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
Portal-based Deployment and Operations Guide for Single-node Cluster
Revision history Single-node clusters
Single-node clusters
Single-node configuration
Operating system deployment
Manual operating system deployment Factory-installed operating system deployment
Configure host networking
Registry settings
Change the hostname
Registering a Partner Admin Link (PAL) for Azure related solutions
Add a PAL through the Azure portal by using Azure PowerShell Add a PAL through the Azure portal using the subscription user ID Dell Technologies Partner IDs for Partner Admin Link
Install Windows Admin Center
Install OpenManage Integration with Microsoft Windows Admin Center
Install roles and features
Configuration to prepare nodes
Verify and update firmware and software compliance
Configuring firewall settings
Cluster deployment prerequisites
Review Requirements Prepare Active Directory Stage SBE package for installation Register Servers with Azure Arc Assign deployment user roles
Deploy Azure Stack HCI version 23H2
Deploy a single-node cluster using Azure portal Deploy Azure Stack HCI using Microsoft ARM template
Best practices and recommendations
Updating the page file settings Update the hardware timeout for the Spaces port Antivirus exclusions
Update Azure Stack HCI clusters using SBE package
Prerequisites SBE package update using PowerShell SBE package update using Azure portal
Dell OpenManage Integration with Windows Admin Center
Overview Managing Microsoft HCI-based clusters Validate and remediate Azure Stack HCI clusters View HCI compliance summary
Onboard Dell policies to Azure Arc from Windows Admin Center

Cluster deployment prerequisites

Home > Integrated Products > Microsoft HCI Solutions from Dell Technologies > Guides 23H2 and later > Portal-based Deployment and Operations Guide for Single-node Cluster > Cluster deployment prerequisites

Cluster deployment prerequisites

  • Register Servers with Azure Arc

    Ensure that you have a unique name for your Azure resource group.

    1. Run the following PowerShell commands on each server. 
      #Install NuGet package provider
      Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
       
      #Register PSGallery as a trusted repo
      Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
       
      #Install Arc registration script from PSGallery 
      Install-Module AzsHCI.ARCinstaller -Force
       
      Install-Module Az.Accounts -RequiredVersion 2.13.2
      Install-Module Az.Resources -RequiredVersion 6.12.0
      Install-Module Az.ConnectedMachine -RequiredVersion 0.5.2
       
      #Define the subscription where you want to register your server as Arc device
      $Subscription = " <subscription ID>
       
      #Define the resource group where you want to register your server as Arc device
      $RG = " <Resource group name>"
       
      #Define the tenant you will use to register your server as Arc device
      $Tenant = "<Tenant ID>
        
      #Connect to your Azure account and Subscription
      Connect-AzAccount -SubscriptionId $Subscription -TenantId $Tenant -DeviceCode
    2. Log in to Microsoft Device Code, and then enter the code that you generated in the previous command.
      In the PowerShell window, you can confirm that the Connect-AzAcount operation is complete.
    3. In the PowerShell window, enter following ARC registration commands: 
      #Get the Access Token for the registration
      $ARMtoken = (Get-AzAccessToken).Token
       
      #Get the Account ID for the registration
      $id = (Get-AzContext).Account.Id
       
      #Invoke the registration script. For this preview release, only eastus region is supported.
      Invoke-AzStackHciArcInitialization -SubscriptionID $Subscription -ResourceGroup $RG -TenantID $Tenant -Region eastus -Cloud "AzureCloud" -ArmAccessToken $ARMtoken -AccountID $id
      The registration process takes about 5 to 15 minutes.
    4. To verify the ARC extension registration, view the resource group in the Azure Portal.
      The server resource must be listed in the resource group.
    5. Verify that all ARC extensions are installed on each node.
      The time required for the system to reflect the installation of ARC extensions through the Azure portal varies depending on the available bandwidth. On average, it usually takes about 10 to 15 minutes.
    6. Go to Resource Group > Node > Extensions.
      Figure 6. View of node extensions
      View of node extensions under Resource Group

    For more information about registering the servers with Azure Arc, see Register servers with Azure Arc.