大网数据广告活动
账户与安全

Guarded host prerequisites

· 52CE 我爱测

Learn more about: Prerequisites for guarded hosts

Review the host prerequisites for the mode of attestation you've chosen, then click the next step to add guarded hosts.

TPM-trusted attestation

Guarded hosts using TPM mode must meet the following prerequisites:

  • Hardware: One host is required for initial deployment. To test Hyper-V live migration for shielded VMs, you must have at least two hosts.

    Hosts must have:

    • IOMMU and Second Level Address Translation (SLAT)
    • TPM 2.0
    • UEFI 2.3.1 or later
    • Configured to boot using UEFI (not BIOS or "legacy" mode)
    • Secure boot enabled
  • Operating system: Windows Server 2016 Datacenter edition or later

    [!IMPORTANT] Make sure you install the latest cumulative update.

  • Role and features: Hyper-V role and the Host Guardian Hyper-V Support feature. The Host Guardian Hyper-V Support feature is only available on Datacenter editions of Windows Server.

Warning: The Host Guardian Hyper-V Support feature enables Virtualization-based protection of code integrity that may be incompatible with some devices. We strongly recommend testing this configuration in your lab before enabling this feature. Failure to do so may result in unexpected failures up to and including data loss or a blue screen error (also called a stop error). For more information, see Compatible hardware with Windows Server Virtualization-based protection of Code Integrity.

Next step:

[!div class="nextstepaction"] Capture TPM info

Host key attestation

Guarded hosts using host key attestation must meet the following prerequisites:

  • Hardware: Any server capable of running Hyper-V beginning with Windows Server 2019
  • Operating system: Windows Server 2019 Datacenter edition
  • Role and features: Hyper-V role and the Host Guardian Hyper-V Support feature

The host can be joined to either a domain or a workgroup.

For host key attestation, HGS must be running Windows Server 2019 and operating with v2 attestation. For more information see HGS prerequisites.

Next step:

[!div class="nextstepaction"] Create a key pair

Admin-trusted attestation

Important: Admin-trusted attestation (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.

Hyper-V hosts must meet the following prerequisites for AD mode:

  • Hardware: Any server capable of running Hyper-V beginning with Windows Server 2016. One host is required for initial deployment. To test Hyper-V live migration for shielded VMs, you need at least two hosts.

  • Operating system: Windows Server 2016 Datacenter edition

    [!IMPORTANT] Install the latest cumulative update.

  • Role and features: Hyper-V role and the Host Guardian Hyper-V Support feature, which is only available in Windows Server 2016 Datacenter edition.

Warning: The Host Guardian Hyper-V Support feature enables Virtualization-based protection of code integrity that may be incompatible with some devices. We strongly recommend testing this configuration in your lab before enabling this feature. Failure to do so may result in unexpected failures up to and including data loss or a blue screen error (also called a stop error). For more information, see Compatible hardware with Windows Server 2016 Virtualization-based protection of Code Integrity.

Next step:

[!div class="nextstepaction"] Place guarded hosts in a security group

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.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Server documentation
适用范围
Windows Server · Source date 08/29/2018
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。