Windows 10: Offline provisioning packages do not start during OOBE

Hello,


In previous versions of Windows 10 I could use dism to add a provisioning package offline that would automate OOBE for me. I do this by applying the image in WinPE then running dism /image:c:\ /add-provisioningpackage /packagepath:test.ppkg.


Starting with 1903 the package is not executed when I get to the first OOBE string. If delete the ppkg from recovery\customizations and run from a flash drive it works as expected. Is this a known issue with 1903? I don't want to put a flash drive into the 450 devices to complete this action and need it to be baked into the image.


Thanks,

Shawn

:)

 

Provision Package to control Start Menu tiles

Hello Stephen,



Thank you for writing to Microsoft Community Forums.



I suggest you to refer the article on
Building Windows 10 Provisioning packages.



However, the issue you posted is related to Provisioning packages with Windows 10 and would be better suited in the TechNet community. Please post your question in the
TechNet forum.



Hope it helps.

Let us know if you got the help you needed by clicking ‘Yes’ or ‘No’.



Regards,

Prakhar Khare

Microsoft Community – Moderator

 

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 Packages and Scanstate


I've been experimenting with the new Provisioning Packages in Windows 10. They seem to be the new way to deploy and save customisations.

For instance you can now use the scanstate command (in the Assessment and Deployment Kit or ADK) to save customised software into a provisioning package for use when you create a Recovery Drive, and also for use when you Reset the computer.

Video is here:
WV9FR-cxFBg

A tutorial similar to the video, showing the detailed steps to create your own provisioning package, is here:
Create Custom Provisioning Package used to Reset Windows 10 or Create Recovery Drive

There is further discussion of scanstate here:
https://www.tenforums.com/installatio...-designer.html