Windows 10: USB + PPKG Provisioning Package stuck at login Office 365

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.ObjectAl

:)

 

Windows 10 Mobile - provide provisioning package

We want to provide a provisioning package to our Windows 10 mobile phones and are testing this.

Regarding TechNet.

Provisioning packages overview on Windows 10/11 - Configure Windows | Microsoft Docs

We can provide that .ppkg to others through any of the following methods:

• 
  Shared network folder
  
• 
  SharePoint site
  
• 
  Removable media (USB/SD)
  
• 
  Email
  
• 
  USB tether (mobile only)
  
• 
  NFC (mobile only)
  

But our mobile phones only provide Removable media (USB/SD)

Anyone using this Feature and can help us.

 

Provisioning package fails to install

Hi Mikeyn,

If it's a provisioning package created by capturing installed apps with Scanstate, my understanding is that you can't apply it at runtime.

From: Configure customizations using Windows ICD - Windows 10 hardware dev

In this context, the ppkg from Scanstate is "reference device data".

It seems from that note that this sort of ppkg won't work at OOBE time either. So I think you're looking at some sort of Windows installation process.

Ways you might try are:

1. use ICD to include the provisioning package into an installer, which can then put onto a bootable USB and installed afresh
2. from a clean install, install the apps, use scanstate to capture the software to C:\recovery\customizations and then use Sysprep to get an image which you deploy with the more traditional route
3. try copying the ppkg to C:\recovery\customizations and running a Reset

For a running PC, I *think* number 3 should work, but I'm not 100% sure, so I'd strongly advise having a good backup before trying it - a Reset will clean a lot of stuff off the PC in any case.

 

Provisioning package fails to install

Hi DavidY,

After it create the .ppkg package. I copied on the usb and run (double click the .ppkg) it on another computer with win10 Pro OS. that's where I got the error.. or I create a new simple provisioning package then import the scanstate package run it on the new machine (OOBE) the error is different (Invalid Product key).

What I'm doing wrong here? How do you run the scanstate provisioning package to install on the another machine?


Thank you in advance !

Mike