Forum Discussion
Solved
Is TPM compatibility on client/VM required for using AutoPilot in Endpoint Manage?
I wonder if its really required the support of TPM on target device if i want to use autopilot over Endpoint Manager?
I know, some of the apps like BitLocker is using TPM, but in my case it would be a basic windows 10 installation, without any special policy/feature.
I know, some of the apps like BitLocker is using TPM, but in my case it would be a basic windows 10 installation, without any special policy/feature.
Hey Busto445,
for user-driven Autopilot deployments there is no need for a TPM (but you may have other features like you said, BitLocker etc. which require one). For the Autopilot self-deploying scenario there is a dependency to a TPM 2.0 with device attestation, as the device needs to authenticate during the early phase, see here:
Windows Autopilot Self-Deploying mode | Microsoft Docs
Requirements
Self-deploying mode uses a device’s TPM 2.0 hardware to authenticate the device into an organization’s Azure AD tenant. Therefore, devices without TPM 2.0 can't be used with this mode. Devices must also support TPM device attestation. All new Windows devices should meet these requirements. The TPM attestation process also requires access to a set of HTTPS URLs that are unique for each TPM provider. For more information, see the entry for Autopilot self-Deploying mode and Autopilot pre-provisioning in Networking requirements.
Important
If you attempt a self-deploying mode deployment on a device that does not have support TPM 2.0 or on a virtual machine, the process will fail when verifying the device with an 0x800705B4 timeout error (Hyper-V virtual TPMs are not supported). Also note that Window 10, version 1903 or later is required to use self-deploying mode due to issues with TPM device attestation in Windows 10, version 1809. Since Windows 10 Enterprise 2019 LTSC is based on Windows 10 version 1809, self-deploying mode is also not supported on Windows 10 Enterprise 2019 LTSC. See Windows Autopilot known issues to review other known errors and solutions.
best,
Oliver
2 Replies
Hey Busto445,
for user-driven Autopilot deployments there is no need for a TPM (but you may have other features like you said, BitLocker etc. which require one). For the Autopilot self-deploying scenario there is a dependency to a TPM 2.0 with device attestation, as the device needs to authenticate during the early phase, see here:
Windows Autopilot Self-Deploying mode | Microsoft Docs
Requirements
Self-deploying mode uses a device’s TPM 2.0 hardware to authenticate the device into an organization’s Azure AD tenant. Therefore, devices without TPM 2.0 can't be used with this mode. Devices must also support TPM device attestation. All new Windows devices should meet these requirements. The TPM attestation process also requires access to a set of HTTPS URLs that are unique for each TPM provider. For more information, see the entry for Autopilot self-Deploying mode and Autopilot pre-provisioning in Networking requirements.
Important
If you attempt a self-deploying mode deployment on a device that does not have support TPM 2.0 or on a virtual machine, the process will fail when verifying the device with an 0x800705B4 timeout error (Hyper-V virtual TPMs are not supported). Also note that Window 10, version 1903 or later is required to use self-deploying mode due to issues with TPM device attestation in Windows 10, version 1809. Since Windows 10 Enterprise 2019 LTSC is based on Windows 10 version 1809, self-deploying mode is also not supported on Windows 10 Enterprise 2019 LTSC. See Windows Autopilot known issues to review other known errors and solutions.
best,
Oliver
- Oliver, thanks a lot for your detailed reply. Now its clear.
