IsHostGuarded shows False on an HGS node that was in-place upgraded to Windows Server

Applies to: Windows Server, version 2004, all editionsWindows Server, version 1903, all editionsWindows Server 2019, all editions

Symptoms


Consider the following scenario:

  • In an environment, you have a Host Guardian Service (HGS) node, a guarded host, and a domain controller (DC) installed.

  • You verify that the guarded host is working by running Get-HGSClientConfiguration. This cmdlet should return IsHostGuarded as True.

  • You in-place upgrade the HGS node and the guarded host to Windows Server, version 1903, Windows Server, version 1909 or Windows Server 2019. To do this, you run Setup.exe from a mounted ISO of Windows Server.

  • You run Get-HGSClientConfiguration again.

In this scenario, the output of the IsHostGuarded is False.

Workaround


To resolve this issue, run the Initialize-HgsServer cmdlet to rejoin the node to the cluster. For more information, see Upgrade HGS to Windows Server 2019.