แก้ไข

แชร์ผ่าน


Using Windows 10/11 virtual machines with Intune

Intune supports managing virtual machines running Windows 10 Enterprise with certain limitations. Intune management doesn't depend on, or interfere with Azure Virtual Desktop management of the same virtual machine.

Enrollment

  • We recommend that you don't use Intune to manage on-demand, session-host virtual machines, also known as non-persistent virtual desktop infrastructure (VDI). Each VM must be enrolled when it's created. Also, regularly deleting VMs creates orphaned device records in Intune until they're cleaned up.

  • Windows Autopilot Self-deploying and pre-provisioning deployment types aren't supported because they require a physical Trusted Platform Module (TPM).

  • Out of Box Experience (OOBE) enrollment isn't supported on non-persistent VMs that can only be accessed by using RDP (such as VMs that are hosted on Azure). This restriction means:

  • Windows Autopilot and Commercial OOBE aren't supported.

    • Enrollment Status Page isn't supported.

Configuration

Intune doesn't support any configuration that utilizes a Trusted Platform Module or hardware management, including:

Reporting

Intune automatically detects virtual machines and reports them as "Virtual Machine" in Devices > All devices > choose a device > Overview > Model field.

Deallocated virtual machines may contribute to noncompliant device reports because they're unable to check in with the Intune service.

Retirement

If you only have RDP access, don't use the Wipe action. The Wipe action deletes the virtual machine's RDP settings and prevents you from ever connecting again.

Limitations

Intune does not support using a cloned image of a computer that is already enrolled. This includes both physical and virtual devices such as Azure Virtual Desktop (AVD). When device enrollment or identity tokens are replicated between devices, Intune device enrollment or synchronization failures will occur.

Next steps

Learn about using Azure Virtual Desktop with Intune