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
Dell EMC Integrated System for Microsoft Azure Stack Hub Manual Firmware & Update Process - Builds 1710 - 1906
Patch and Update Overview Installing Microsoft Azure Stack Hub Software Updates Applying Dell EMC OEM extension package Manually Updating Scale Unit Node Firmware Supporting Documentation Manually Updating HLH on Windows Server 2016 through Redeployment
Before proceeding
Installing HLH OS from USB flash drive
Installing HLH from PAW or Jumpbox

Installing HLH from PAW or Jumpbox

Installing HLH from PAW or Jumpbox

  • Procedure

    To install the HLH from a Privileged Access Workstation (PAW) or Jumpbox:

    1. Connect to the iDRAC Virtual Console of the HLH server from a PAW. At the security certificate window, select Continue to this website.

    1. Enter the credentials used for the HLH iDRAC.

    1. From the Virtual Console Preview pane, click Launch.

    Note: The following figures show a 13G server and a 14G server respectively.

    1. When the Virtual KVM Remote Client message displays, click Allow.

    1. When the Untrusted security warning displays, click Run.

    1. From the splash window menu, select Virtual Media > Connect Virtual Media.

    1. From the list, select Map CD/DVD.

    1. 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).

    1. Select the ISO, and then click Open.

    1. From Map CD/DVD box, click Map Device.
    2. Select Next Boot from the menu, and then select the Virtual CD/DVD/ISO option from the list.

    1. From the Device Selected window, to confirm, click OK.

    1. To run a Power Cycle System (cold boot), click Yes.

    During this process, the HLH reboots and BIOS displays the following message: IPMI: Boot to Virtual CD Requested.

    1. Press Enter each time you are prompted to boot from CD/DVD.

    Windows Server 2016 media starts loading for installation.

    Completing Installation of OS

    Procedure

    To install and configure Windows Server 2016:

    1. From Windows Setup, set the language, time, and keyboard to your region, and then click Next.

    1. Click Install Now.

    1. Under Activate Windows, click I don’t have a product key.

    1. From the operating system list, choose Windows Server 2016 Datacenter (Desktop Experience), and then press Next.

    1. After you read the license terms, select I accept the license terms, and then click Next.

    1. At the installation prompt, to select the install location:
      1. Delete all existing partitions except the 299 GB partition (14G) or 99 GB partition (13G).
      2. Install the OS in the newly created free space.
      3. To restart the server, click Next.

    1. After restarting the server, verify that the data partition still exists and is listed as the D: drive. Change the drive letter if required.
    2. Install the Windows Server Hyper-V role and required tools.
      1. Open an Administrative PowerShell window.
      2. Enter Install-WindowsFeature -Name Hyper-V, RSAT-Hyper-V-Tools, and then press Enter.
    3. To continue the HLH deployment, follow the instructions in the Dell EMC Integrated System for Microsoft Azure Stack Hub Deployment Guide.

    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.

    1. 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 Integrated System for Microsoft Azure Stack Hub Patch and Update Installation Guide.

    Important notes

    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 7.                  JSON file

    Figure 8.                  Before modifying the file

    Figure 9.                  After modifying the file