Відео

No, not at all! Azure Local is a consolidation and name change for what was once called Azure Stack HCI. It is a not an OS, but a compete solution. That solution is built on-top of technologies like Hyper-V and Windows Server OS. As a matter of fact, Windows Server 2025 shares the same build number as the soon-to-be-released OS update for Azure Local. And Windows 11 24H2! Just to say it one more time for everyone in the back - Hyper-V is not going anywhere! It is the foundation that almost every Windows OS uses - from client (Win 10/11), Server, XBox, and Azure's own hypervisor. Local AD - not sure I follow this question. If you're asking if traditional ADDS is gonna die and be replaced with Azure AD (Entra ID), the answer is also a loud "no". Azure Local was built requiring ADDS since the beginning, but they are introducing AD-less deployments for folks who do not want to manage a "fabric domain". But no, Azure AD is not in that equation as a replacement.

In the demo video the nodes automatically were assigned to their sites because sites/subnets were configured in “Active Directory Sites and Services” (For example, subnet 10.3.7.0/24 = “site X” and Subnet 10.4.7.0/24 = “site Y”). Otherwise, you would do it manually in the WAC wizard. For PowerShell deployments it would be done like the following: #create sites: New-ClusterFaultDomain -CimSession "ClusterS1" -FaultDomainType Site -Name "Site1" New-ClusterFaultDomain -CimSession "ClusterS1" -FaultDomainType Site -Name "Site2" #verify both sites created for the cluster: Get-ClusterFaultDomain -CimSession "ClusterS1" #assign servers to their sites: Set-ClusterFaultDomain -CimSession "ClusterS1" -Name "Server1", "Server2" -Parent "Site1" Set-ClusterFaultDomain -CimSession "ClusterS1" -Name "Server3", "Server4" -Parent "Site2" #verify nodes are in their desired sites: Get-ClusterFaultDomain -CimSession "ClusterS1" learn.microsoft.com/en-us/azure-stack/hci/deploy/create-cluster-powershell

Currently the answer is 'no'. Nutanix AHV backups can only be restored to a select few other hypervisors or cloud locations (documentation.commvault.com/2022e/essential/87279_cross_hypervisor_restores_vm_conversion.html). Please feel free to submit a request for Nutanix to Azure Stack HCI support here: metallic.io/contact

Please try watching again. I just checked the video and didn't experience any issues with the audio.

In Windows Admin Center, you should be able to see the disk space usage under Tools -> Drives and then by clicking the Inventory tab. See: learn.microsoft.com/en-us/azure-stack/hci/get-started#drives

Correct, Storage Bus Layer (SBL) cache is not supported in single server HCI configurations. The only supported storage types are flat-NVMe or SSD (i.e., single drive type).

Hi Suvradeb. The four drives will need to be identical SSDs for a non-cached solution. One recent announcement from Microsoft is lowering the minimum number of capacity drives needed. In your case, you can create an HCI cluster with just 2 SSD (no HDDs) drives as capacity drives. See learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-hardware-requirements#physical-deployments

Microsoft recommends using a server from the Azure Stack HCI catalog (learn.microsoft.com/en-us/azure-stack/hci/guided-quick-deploy-eval). In your case it might be easier to create a VM-based lab (learn.microsoft.com/en-us/azure-stack/hci/deploy/tutorial-private-forest) or by using Azure VMs (learn.microsoft.com/en-us/azure-stack/hci/guided-quick-deploy-eval).

Azure Stack HCI is Hyper-V under the covers. If you want the traditional model of licensing the host and licensing the guests with a license instead of monthly subscription, you can install the Hyper-V role on Windows Server. It's functionally the same. Azure Stack HCI may get some updates faster than Hyper-V on Windows, but it's the same hypervisor, runs the same VHD's, etc.

Yes. Dell has an integrated solution for disconnected Windows server HCI too.

Yep: Azure Stack Hub

Glad you enjoyed it

I believe you need 2 servers minimum per cluster and 2 sites to achieve a stretched cluster, so 4 servers total