Update HLH hosts from Windows Server 2016 to 2019 on Azurestack Hub

Summary: This article explains the importance of upgrading the HLH server from Windows Server 2016 to Windows Server 2019.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Instructions


Table of Contents

  1. Support strategy
  2. Fixes
  3. Resource 

Migrating your HLH from Windows Server 2016 to Windows Server 2019 is a critical key component and necessary part of optimizing your Windows Azurestack Hub environment. The HLH upgrade is key to ensuring proper monitoring of the various software and hardware components.

1. Support Strategy

1.1 Outline support strategy

1.2 Highlight both Microsoft and Dell EMC support details

N-2 support model policy (Currently N-3 during times of Covid-19)  is governed by Microsoft so they could properly and most effectively push out fixes and features.  HLH is key to that as it is constantly monitoring various points within this ecosystem to predict hardware failure and known issues. Keeping the HLH current is a critical key component.    If the customer’s HLH stays on Windows Server 2016 it will not properly monitor the solution.
Again, as with any solution, the main reason for updates is to keep data, applications, and identities secure.
For the AzureStack Hub, this is no different.  For this on-premises environment to ensure resiliency and a secure environment with limited downtime, our customers need to stay within N-2 code currency of the Windows monthly cadence.  Please note: MS extended that to N-3 while customers work through the current Covid-19 pandemic.  This also includes keeping current with the HLH and hardware components such as CPLD, PSU, and BIOS.  They ensure your environment operates as expected and prevents unexpected downtime.

https://docs.microsoft.com/en-us/azure-stack/operator/azure-stack-updates?view=azs-2002
https://docs.microsoft.com/en-us/azure-stack/operator/azure-stack-servicing-policy?view=azs-2002

 

QNA44773_en_US__1icon Note: According to Microsoft's documents, please keep your Azure Stack Hub environment on a supported Azure Stack Hub software version to continue to receive support.

2. Fixes and Enhancements
 

2.1 Updating HLH to the latest Windows Server – 2019. Aligns with the rest of the stamp.
2.2 Migrating Management VM to 2019.
  • Updates management VM to latest Windows Server – 2019
  • Removes OpenManage Essentials
2.3 Updating management software
  • Removes OpenManage Essentials from HLH
    • End-of-Life management software
    • Removes the need for legacy software – Silverlight
       
  • Updates OpenManage Enterprise to the latest code
  • Updates SAE to the latest code

 

One of the biggest and important fixes addresses issues with dial Home. Dial Home being generated from the older agent did not have the capability to properly route cases and or alert on all critical issues, so it delays any proactive measures and hinders remediation.  There has been a good amount of work to update the code and improve upon the alert functionality.  Without the update, this could get missed, and or the customer remediation could be significantly delayed.  As such, an important step when migrating for support and the field is to ensure we follow the steps and test dial home functionality accordingly.

OMEss is the end of life so we need to ensure our customers update to OMEnt to keep with support coverage.  OpenManager Essentials is a free software with limited function and alerting capability. OpenManager Enterprise has more features and components to allow it to better support and integrate with the IDRAC and Life cycle monitoring needed for AzureStack.  Windows 2016 only supported OMEss and due to limited features, we could not effectively support our customers.  OMEss is not tested and or validated with a newer code.  It works until it breaks and it is the best effort.   It is a hindrance to rely on an end of life product OMEss and Silverlight from MS which has its own instability and reported issues.

Many customers have complained about Silverlight and our reliance on that.  There are known issues and with this update and migration, we no longer rely on this. OMEss functions by leveraging Microsoft’s Silverlight but it works off an older version of Silverlight and breaks when a newer version of Silverlight is installed on top of it.  The only true way to fix that besides the workaround of uninstalling the latest Silverlight and reinstall the Silverlight version that was validated with OMEss is to migrate your HLH to Windows 2019 which no longer leverages Silverlight.

Reported problems from existing Windows 2016 environments that have been addressed with Windows Server 2019.

With all these changes, it helps ensure the customer’s environment will be properly supported with hardware alerts making it to the right Dell backend and cases get opened as expected. 


3.Resources

Video walkthrough:
https://edutube.emc.com/html5/playlistmain.htm?pno=JBNAiW0CILRqoaSCeS+pRA

 

Whitepapers and Documentation:
https://dl.dell.com/content/docu97255_HLH_Migration_from_Windows_Server_2016_to_2019_for_Cloud_for_Microsoft_Azure_Stack_Installation_Guide-Valid_from_Dell_EMC_2001_and_Microsoft_1910_Releases.pdf?language=en_US&source=Coveo
 


Affected Products

Integrated System for Microsoft Azure Stack Hub, Integrated System for Microsoft Azure Stack Hub 13G, Integrated System for Microsoft Azure Stack Hub 14G, Dell Hybrid Cloud System for Microsoft
Article Properties
Article Number: 000060392
Article Type: How To
Last Modified: 15 Sep 2021
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.