Complete the following predeployment configurations before deploying the Azure Stack HCI solution:
Installing Windows Admin Center and OMIMSWAC
Windows Admin Center build 2103 or higher is available from the Microsoft Download Center (download will start if you click this link) and installable on any computer or VM running Windows 10, Windows Server 2016, Windows Server 2019, or Windows Server version 1709. Windows Admin Center may also be installed directly on a managed node to manage itself. It is possible to implement high availability for Windows Admin Center by using failover clustering. When Windows Admin Center is deployed on nodes in a failover cluster, it acts as an active/passive cluster, providing a highly available Windows Admin Center instance.
The Windows Admin Center installer wizard performs the configuration tasks that are required for Windows Admin Center functionality. These tasks include creating a self-signed certificate and configuring trusted hosts for remote node access.
Optionally, you can supply the certificate thumbprint that is already present in the target node local certificate store. By default, Windows Admin Center listens on port 443—you can change this port during the installation process.
For complete guidance on installing Windows Admin Center on an Azure Stack HCI operating system with desktop experience or Server Core, see Install Windows Admin Center .
After the installation is complete, you can access Windows Admin Center at
https://managementstationname:< PortNumber > and install the Dell EMC OpenManage Integration with Microsoft Windows Admin Center (OMIMSWAC) extension. For more information about the installation procedure, see the "Installing Dell EMC OpenManage Integration with Microsoft Windows Admin Center" section in the Dell EMC OpenManage Integration with Microsoft Windows Admin Center Installation Guide .
The Azure Stack HCI solution requires registration with an Azure subscription within 30 days of deployment. Once the Azure Stack HCI cluster is registered, all the hybrid services that are supported as a part of the integration can be used along with the hyper-converged infrastructure services. To complete Azure registration, Azure authentication credentials, subscription ID, and an optional tenant ID are required.
Configuring network switches
Based on the selected network topology from the recommended configurations, configure the top-of-rack (ToR) network switches to enable storage and VM/management traffic. A standard Storage Spaces Direct deployment requires three basic types of networks: out-of-band (OOB) management, host management, and storage.
For sample switch configurations, see Sample Network Switch Configuration Files .
For configuration choices and instructions about different network topologies and host network configurations, see Network Integration and Host Network Configuration Options .
Deploying the Azure Stack HCI operating system
These instructions are for manual deployment of the Azure Stack HCI operating system on AX nodes. Unless specified otherwise, perform the steps on each physical node in the infrastructure that will be a part of Azure Stack HCI.Manual operating system deployment
Dell Lifecycle Controller and integrated Dell Remote Access Controller (iDRAC) provide options for operating system deployment. Options include manual installation or unattended installation by using virtual media and the operating system deployment feature in Dell Lifecycle Controller.
The step-by-step procedure for deploying the operating system is not within the scope of this guide. The remainder of this guide assumes that:
- The Microsoft Azure Stack HCI operating system installation on the physical server is complete.
- You have access to the iDRAC virtual console of the physical server.
Enabling the firewall rule
If the nodes do not have a fully qualified domain name, set the firewall rule for each node to ensure that the firewall port for Windows Remote Management allows you to add inbound traffic on additional nodes. Setting this rule allows Windows Admin Center to reach the nodes and add them to the cluster creation wizard.
Run the following PowerShell command as an administrator on each node:
Set-NetFirewallRule -Name WINRM-HTTP-In-TCP-PUBLIC -RemoteAddress Any
Perform the following steps to enable CredSSP on the management station where Windows Admin Center is installed.
- From a PowerShell window, run gpedit .
- In the Group Policy Editor window, go to .
- Select Allow delegating fresh credentials with NTLM-only server authentication and enable it.
- Under Options , add servers to the list by clicking Show...
- Add a fully qualified domain name entry that begins with wsman/hostname.mydomain.com (single host entry) or wsman/*.mydomain.com (wild card entry for all the hosts in this domain).
- Apply the settings.
- Run gpupdate /force in the PowerShell window.