USB + PPKG (Provisioning Package) stuck at login Office 365

Jos 106 Reputation points
2021-11-03T13:16:52.507+00:00

We are using Windows Configuration Designer to create a PPKG file. We have created a USB device combined with the PPKG file on the root of this device. We have tested several versions on two devices and 10/12 USB's worked as expected. But suddenly it stopped working with the other USB's. When we tried to use the previous USB's (which we did test before and which worked) again they suddenly also stopped working.

When looking in Azure we do see "Failed" for "Add device", "Add registered owner to device" and "Add registered users to device". The reason in here "Microsoft.Online.Workflows.ObjectAlreadyExistsException".

We have also tried:

  • Installing a different device with the same USB: It works
  • Logon when the question was shown: It works
  • Applying the PPKG manually after login: It works as well

So for us it looks like the USBs are working but somehow there is a limit on how many times you can reinstall a device and let it join to Azure.

Anyone an idea what to look for and where to find it?

Microsoft Intune Enrollment
Microsoft Intune Enrollment
Microsoft Intune: A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.Enrollment: The process of requesting, receiving, and installing a certificate.
1,417 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
23,177 questions
0 comments No comments
{count} votes

Accepted answer
  1. Jos 106 Reputation points
    2021-11-04T08:39:17.617+00:00

    We have found the root cause, we also had a profile inside Azure for AutoPilit, inside this profile we enabled the option which automatically adds all devices inside this tenant to AutoPilot.
    The first day everything worked as expected but the day after this device was available inside AutoPilot.
    When I removed the PPKG file it still was connecting automatically to the tenant of this customer, so this way we found out this was the root cause.
    So its solved for us.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.