Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
End-to-End Single-Node Deployment: Microsoft HCI Solutions from Dell Technologies
Single-node deployment
Single-node deployment
Operating system deployment
Install roles and features
Change the hostname
Registry settings
PAL and DPOR registration for Azure Stack
Joining cluster nodes to an Active Directory domain
Single-node configuration
Updating a standalone node before adding it to the cluster
Network connectivity for single node clusters
Creating the host cluster
Enabling Storage Spaces Direct
Updating the page file settings
Azure onboarding for Azure Stack HCI operating system
Best practices and recommendations

Install roles and features

Install roles and features

  • Deployment and configuration of a Windows Server 2016, Windows Server 2019, Windows Server 2022, or Azure Stack HCI operating system version 22H2 cluster requires enabling specific operating system roles and features.

    Enable the following roles and features:
    • Hyper-V service (not required if the operating system is factory-installed)
    • Failover clustering
    • Data center bridging (DCB) (required only when implementing fully converged network topology with RoCE and when implementing DCB for the fully converged topology with iWARP)
    • BitLocker (optional)
    • File Server (optional)
    • FS-Data-Deduplication module (optional)
    • RSAT-AD-PowerShell module (optional)

    Enable these features by running the Install-WindowsFeature PowerShell cmdlet:

    Install-WindowsFeature -Name Hyper-V, Failover-Clustering, Data-Center-Bridging, BitLocker, FS-FileServer, RSAT-Clustering-PowerShell, FS-Data-Deduplication -IncludeAllSubFeature -IncludeManagementTools -verbose

    Note: Install the storage-replica feature if Azure Stack HCI operating system is being deployed for a stretched cluster.

    Note: Hyper-V and the optional roles installation require a system restart. Because subsequent procedures also require a restart, the required restarts are combined into one (see the Note in the "Changing the hostname" section).