Important: AD mode is deprecated beginning with Windows Server 2019. For environments where TPM attestation is not possible, configure host key attestation. Host key attestation provides similar assurance to AD mode and is simpler to set up.
This topic describes the intermediate steps to prepare Hyper-V hosts to become guarded hosts using Admin-trusted attestation (AD mode). Before taking these steps, complete the steps in Configuring the fabric DNS for hosts that will become guarded hosts.
Create a security group and add hosts
-
Create a new GLOBAL security group in the fabric domain and add Hyper-V hosts that will run shielded VMs. Restart the hosts to update their group membership.
-
Use Get-ADGroup to obtain the security identifier (SID) of the security group and provide it to the HGS administrator.
Get-ADGroup "Guarded Hosts"Get-AdGroup command with output
Register the SID of the security group with HGS
-
On an HGS server, run the following command to register the security group with HGS. Re-run the command if necessary for additional groups. Provide a friendly name for the group. It does not need to match the Active Directory security group name.
Add-HgsAttestationHostGroup -Name "<GuardedHostGroup>" -Identifier "<SID>" -
To verify the group was added, run Get-HgsAttestationHostGroup.
Next step
[!div class="nextstepaction"] Confirm attestation
Additional References
Source: Microsoft Learn / Windows Server documentation by Microsoft and contributors (upstream author metadata: robinharwood). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
