Windows 10: Intune Autopilot is failing to encrypt Windows 10 HAAD Joined devices during OOBE

Nitin Singh4 · Dec 5, 2024

Intune Autopilot is failing to encrypt Windows 10 HAAD Joined devices during OOBE

:)

Jeremy USW · Dec 5, 2024

Windows Autopilot not installing apps

We have Windows Autopilot setup on several devices through Intune. Recently, the devices will no longer run through the process properly during OOBE. When we reset a machine, the apps do not install.

The devices are configured for autopilot. They show profile status of assigned in Intune. After logging in as a user during OOBE, though, they never display the app install window like they used to. When looking at the Autopilot deployments page in Intune, it shows the device enrollment status as success, but it also shows it completed in 10-15 seconds. In the past, when this was successful, it was always 5-10 minutes before it was successful.

Can anyone tell us where to start troubleshooting this problem? Autopilot has been working flawlessly when resetting a Windows 10 or 11 device. Now none of them are going through the process. All machines are Azure AD joined. They are not hybrid and we have nothing on prem anymore.

Sean Todd (Sean.Todd) · Dec 5, 2024

Windows 10 - Hybrid Joined Machines - Intune Bitlocker

Goal: To deploy Bitlocker via Intune to both Hybrid Joined / AzureAD joined windows 10 devices.

Issue - Currently seeing errors for machines relating to password rotation in the configuration of most workstations.

Error:

-2016281112 (Remediation failed)

ERROR CODE

0x87d1fde8

ERROR DETAILS

Remediation failed

The encryption appears to be taking place, but the password rotation is failing. Any suggestions would be appreciated. I've googled for several days at this point.

Brink · Dec 5, 2024

Windows Autopilot for existing devices supports Hybrid Azure AD Join

First, a quick refresher on Windows Autopilot for existing devices: For customers looking for a path to migrate from Windows 7 (or 8.1) to Windows 10 using Windows Autopilot, the challenge was always that you had to register the existing machines with Windows Autopilot in advance, but doing so was impossible because you couldn't grab the hardware hash from a device running Windows 7.

So, we added the ability in Windows 10, version 1809 to use a JSON file containing the equivalent of the Windows Autopilot profile so that you didn't have to register the device in advance; you could then tell Microsoft Intune to harvest the hash from the device later and register the device after the fact.

This solution worked great and has been leveraged by a number of organizations to move from Windows 7 and Active Directory to Windows 10 and Azure Active Directory, using Microsoft Intune (often with Configuration Manager for co-management) to deploy and manage the device.

But some organizations weren't yet ready for Azure AD Join (even with the Administrative Templates support in Microsoft Intune, and full support for Kerberos authentication from an Azure AD-joined device to Active Directory-secured resources) and asked us to support this same process, but with Hybrid Azure AD Join.

With this month's Microsoft Intune updates, we can now support this. And no client changes are needed: this works with Windows 10, version 1809 and above. All you need to do is specify a JSON file that specifies to join Active Directory (via Hybrid Azure AD Join) instead of Azure Active Directory - the rest of the process (e.g. the Configuration Manager task sequence that deploys Windows 10 to the device) is unchanged.

Note that you will need to target a Domain Join profile (and any other device-targeted policies) to "All devices" since the device won't be known to Microsoft Intune in advance. (Don't worry, this Domain Join profile has no impact on already-deployed devices, as it's only used by Microsoft Intune to determine what domain and OU should be used when joining a device to Active Directory.) See the updated documentation for more details.
Click to expand...

Source: https://techcommunity.microsoft.com/...re/ba-p/730408

Tweet

— Twitter API (@user) View on Twiiter
Click to expand...

Windows 10: Intune Autopilot is failing to encrypt Windows 10 HAAD Joined devices during OOBE

Intune Autopilot is failing to encrypt Windows 10 HAAD Joined devices during OOBE

Intune Autopilot is failing to encrypt Windows 10 HAAD Joined devices during OOBE

Intune Autopilot is failing to encrypt Windows 10 HAAD Joined devices during OOBE

Intune Autopilot is failing to encrypt Windows 10 HAAD Joined devices during OOBE - Similar Threads - Intune Autopilot failing

Intune and AutoPilot

Intune and AutoPilot

Autopilot device with Entra and Intune mismatch

Autopilot device with Entra and Intune mismatch

Intune Autopilot is failing to encrypt Windows 10 HAAD Joined devices during OOBE

Intune Autopilot is failing to encrypt Windows 10 HAAD Joined devices during OOBE

Onboarding OOBE laptops to Intune Autopilot - Defender Install

Win11 OOBE "Let's name your PC" breaks Pre-Provisioning Mode HAAD Join Autopilot

Win11 OOBE "Let's name your PC" breaks Pre-Provisioning Mode HAAD Join Autopilot