To install the HLH from a Privileged Access Workstation (PAW) or Jumpbox:
- Connect to the iDRAC Virtual Console of the HLH server from a PAW. At the security certificate window, select Continue to this website.
Figure 50. Security certificate warning
- Enter the credentials used for the HLH iDRAC.
Figure 51. HLH iDRAC credentials
- From the Virtual Console Preview pane, click Launch.
Note: The following figures show a 13G server and a 14G server respectively.
Figure 52. 13G server system summary
Figure 53. 14G server system summary
- When the Virtual KVM Remote Client message displays, click Allow.
Figure 54. Prompt message
- When the Untrusted security warning displays, click Run.
Figure 55. Security warning prompt
- From the splash screen window menu, select Virtual Media > Connect Virtual Media.
Figure 56. Virtual Media menu option
- From the list, select Map CD/DVD.
Figure 57. Map CD/DVD list option
- To locate Windows Server 2016 ISO, click Browse.
This is located in the data partition of the HLH in the Tools directory (D:\Tools\HLHISO).
Note: If you map to the ISO located in the data partition of the HLH, first ensure that both the C: and D: partitions are decrypted (see Before proceeding).
Figure 58. Ensure partitions have been decrypted
- Select the ISO, and then click Open.
Figure 59. Selecting the ISO CD image file
- From Map CD/DVD box, click Map Device.
- Select Next Boot from the menu, and then select the Virtual CD/DVD/ISO option from the list.
Figure 60. Selecting Virtual CD/DVD/ISO
- From the Device Selected window, to confirm, click OK.
Figure 61. Selecting a boot device
- To run a Power Cycle System (cold boot), click Yes.
Figure 62. Running a cold boot
During this process, the HLH reboots and BIOS displays the following message: IPMI: Boot to Virtual CD Requested.
Figure 63. Reboot progress
- Press Enter each time you are prompted to boot from CD/DVD.
Figure 64. Windows installation media prompt
Windows Server 2016 media starts loading for installation.
Figure 65. Loading for media installation
Completing Installation of OS
To install and configure Windows Server 2016:
- From Windows Setup, set the language, time, and keyboard to your region, and then click Next.
Figure 66. Setting Windows Server 2016 preferences
- Click Install Now.
Figure 67. Installing Windows Server 2016
- Under Activate Windows, click I don’t have a product key.
Figure 68. Product key
- From the operating system list, choose Windows Server 2016 Datacenter (Desktop Experience), and then press Next.
Figure 69. Selecting the OS
- After you read the license terms, select I accept the license terms, and then click Next.
Figure 70. License terms
- At the installation prompt, to select the install location:
- Delete all existing partitions except the 299 GB partition (14G) or 99 GB partition (13G).
- Install the OS in the newly created free space.
- To restart the server, click Next.
Figure 71. Installing Windows
- After restarting the server, verify that the data partition still exists and is listed as the D: drive. Change the drive letter if required.
- Install the Windows Server Hyper-V role and required tools.
- Open an Administrative PowerShell window.
- Enter Install-WindowsFeature -Name Hyper-V, RSAT-Hyper-V-Tools, and then press Enter.
- To continue the HLH deployment, follow the instructions in the Dell EMC Cloud for Microsoft Azure Stack Deployment Guide for 13G or 14G, as required.
Note: The deployment guide is not available to customers. To obtain instructions for completing a new HLH deployment, create a Support Request with Dell EMC Support.
- To prepare your system to use the Dell EMC Patch and Update Automation Tool for updates later than the 1906 release, follow the instructions in the latest Dell EMC Cloud for Microsoft Azure Stack Hub Patch and Update Installation Guide.
For 13G, to avoid taking down the scale unit nodes, do not use the remediate parameter when running the Invoke-CheckFirmwareBaseline command.
For 14G, to skip the compliance portion and avoid decommissioning the scale unit nodes, before running the HLH Deployment script, modify the AutomationWorkFlow.JSON file.
The following figures show the AutomationWorkFlow.JSON file before and after editing the statuses of the compliance commands:
Figure 72. JSON file
Figure 73. Before modifying the file
Figure 74. After modifying the file