Hello
I have setup a test machine with all the settings and apps I need, I have then created a provisioning package Called 'capturedSettings' using the ICD but when I try to install it I get the following error
I use the following tutorial on this website to use the scanstate command to created the PPKG
Provisioning Package - Create in Windows 10 - Windows 10 Forums
Last edited by mattsaundersmcp; 09 Oct 2016 at 18:23.
Hi mikeyn,
If your provisioning package was captured with ScanState and includes desktop apps, I think the only way to install it is during an installation - I don't think you can use Settings as per the screenshot above for this type of provisioning package.
How are you trying to install it?
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
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".Deployment assets are configurable customizations that are not settings. These, and more information on how to configure them, are as follows:
- Applications - To add an app
- Driver set - To add a driver set
- Drivers - To add a driver
- Features on demand - To add an individual feature package
- Language Packages - To add a language pack
- Reference device data - To import reference device data
- Windows Updates - To add OS updates
Important For Windows 10, if you build a provisioning package that contains any asset and then install the package during the first runtime experience or later, the asset will not be installed on the device. Assets can only be applied during the deployment process and not at runtime.
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:
- use ICD to include the provisioning package into an installer, which can then put onto a bootable USB and installed afresh
- 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
- 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.
Hi DavidY,
Thank for your awesome directions.. #3 works for me.. the only thing I noticed that Window Pro machine didn't upgrade to Window10 ENT when I installed the scanstate provisioning.. any idea? Thank you in advance..
Thanks,
Mike
Hi DavidY,
I have the MAK win10 ent licensed and that didn't work when I plug that in to a new provisioning package (runtime) it error "Invalid Product key".. What I read from other blogs it only work if you do have a KMS license (which need a KMS server) but of course if you input the Win10 ENT Mak license to Win10Pro that work..
Thank you for all your help!
Mike
I don't know any more than I read in articles like this I'm afraid:
How to upgrade Windows 10 edition using provisioning package? – beanexpert
I imagine you've already found this one though.
Hi DavidY,
Yeah, I found that already and tried without success.. I found this blog that talk about it too and stated to use KMS Licensed
How to convert Windows 10 Pro to Windows 10 Enterprise using ICD | Ask the Core Team
Thank you DavidY
Mike
Quote