Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

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.

↑ Back to the top


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.

↑ Back to the top


Keywords: HGS node stops working

↑ Back to the top

Article Info
Article ID : 4477066
Revision : 32
Created on : 4/15/2020
Published on : 5/28/2020
Exists online : False
Views : 539