Windows 10: Provisioning package creates account but OOBE still forces creation.

Hello, I created a provisioning package to add a local admin account and connect to our domain. It runs during the OOBE and everything works, it just still forces me to create an account at startup. Is there a way to bypass this or would an answer file be a better solution?

Thanks!

:)

 

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

 

Create Provisioning Package in Windows 10  

Hi there brylok1981, sorry for delayed response.

I believe the provisioning packages mentioned in this Tutorial, which contain Win32 apps from an installation, can only be applied during the Setup process; I think it won't work during the Out of Box experience (OOBE). I haven't tried it with the latest version of Windows and the latest ADK but I'd be surprised if that has changed.

If you do want to create provisioning packages containing other settings, then I believe Microsoft's recommended approach is to use the Windows Configuration Designer. (This was formerly the Windows Imaging and Configuration Designer, but in version 1703 the Imaging capabilities have been removed.) This tool is found within the Windows ADK.

To apply the package from a USB drive, it should be possible to Insert the USB at the first OOBE screen and it should be detected. The provisioning package needs to be in the root folder of the USB drive. I haven't tried it myself with a recent version though.
https://docs.microsoft.com/en-us/win...-apply-package

 

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:


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