Windows 10: ADK 10: Windows Imaging and Configuration Designer

OK I think there's a new ADK out there... On this Technet forum thread someone has posted this:

The shortened link decodes to a microsoft.com URL:
http://download.microsoft.com/downlo...k/adksetup.exe

@Kyhi and @Kari, you might be interested if you weren't aware already...

 

Thank You David..

Want to test the provisioning packages

 

Yeah I've been itching to explore provisioning packages, although annoyingly I'm pretty busy for the next few days so don't know when I'll get the chance to do much.

 

what ever you do - do not follow this guide - as it is totally BOGAS
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx

Code: scanstate.exe /apps /ppkg C:\Recovery\Customizations\Name.ppkg /o /c /v:13 /l:c:\ScanState.log[/quote] Code: scanstate.exe /i:migapp.xml /i:migdocs.xml /genconfig:\config.xml /o /v:13 /l:\ScanState.log scanstate.exe /apps /ppkg D:\ProvPackages\Name.ppkg /o /c /v:13 /l:\ScanState.log[/quote]

 

[/quote] Is it all wrong or is it just the command they give (even I'd spotted that it says "/app" when it should be "/apps" !)

 

My customization package was 3.9GB

I install Win10 ADK

 

Great - thanks for the info. *Smile

 

somehow they think this
Code: D:\ScanState_x64\scanstate.exe /app /ppkg D:\Provisioning\ /o /c /v:13 /l:\ScanState.log[/quote] Code: D:\ScanState_x64\scanstate.exe /app /ppkg C:\Recovery\Customizations\ /o /c /v:13 /l:C:\ScanState.log[/quote] gives you that > C:\Recovery\Customizations\usmt\usmt.ppkg < then they say you have to move the usmt.ppkg

But to get that all you need to do is this
Code: D:\ScanState_x64\scanstate.exe /apps /ppkg C:\Recovery\Customizations\usmt.ppkg /o /c /v:13 /l:C:\ScanState.log[/quote]

 

So... when the documentation says the command is
Code: scanstate.exe /app /ppkg {Foldername}[/quote] what it really should say is:
Code: scanstate.exe /apps /ppkg {Foldername}\Something.ppkg[/quote] That is, it's /apps not /app, and (when used with the ppkg parameter at least) it needs a full file name, not just a folder.

I'd never have figured that out on my own - thanks for that!

 

My testing was all done on the same 10240 x64 PC

Created a Recovery Drive via Control Panel
Attachment 25044

Created a provisioning package c\recovery\customizations\
Attachment 25045

Recreated the Recovery drive via control panel - with c\recovery\customizations\xpscustom.ppkg
Attachment 25047
Attachment 25048

Create Recovery Drive added the customizations to the recovery media..

Also just a little side note: you can also right click the *.ppkg and run as admin and it will install your customizations..

Using the create recovery option is said the keep windows apps and windows updates ( because they are all ready in the windows data store folder)

You can also see the partition layout changes in the diskpart.txt ( you can edit the partitions and layout that recovery creates)
And you can see how the recovery is placing the images in resetcfg.xml (which can also be edited to suit your needs)

 

I think that is similar to what I was finding (in a 32-bit VM).

So by creating the provisioning package in c:\Recovery\Customizations (with scanstate), it means that those customisations are saved by the Recovery Drive process. (And presumably they also come back when you do a Reset without the Recovery Drive - I haven't tested that yet.)

 

that is my understanding too - but have not tested... Although I had the USB plugged in and the system must of rebooted due to windows update - woke up to recovery > select your language

 

I have created a script to run the scanstate commands - it also contains USMT
Run the cmd from the same Dir as usmt

https://www.dropbox.com/s/0aqg2c0z0a...0TEST.zip?dl=0

 

I know this is a dumb question, but what is the purpose of ScanState? What exactly does it do, and what do you gain from using it? I've read about it, but I still don't quite "get it."

 

First off you have to understand that windows recovery has changed.. Recovery no longer uses an install.wim or a factory install.wim which was kept on a separate partition.. Windows 10 Recovery now rebuild itself from its data store.. Basicly windows keeps updates, drivers and apps in the winsxs folder - theses are used as a reference for such tools as SFC and DISM - to repair the online image.. Every file on the running OS has a compressed version in backup..

When you recover windows 10 it rebuilds itself from those backup files.. It does not back up 3rd party programs, non default system setting, 3rd party drivers - basically anything non MS Windows related is not backed up and thus will not be restored..

Scanstate allows you to create a provisioning package that will backup the non-windows settings, apps, programs and drivers..
These settings are captured into a ppkg file and stored the Recovery\customizations Folder.. when you reset or refresh these ppkg files are added into the recovery process.. thus reinstalling all your programs and setting..

You can even save the ppkg to an external source, clean install the OS, and then run the ppkg file as admin and install the settings...

Here is the Plus to all this, say you have 10 different PC, all running different hardware, rather then setting each one by itself, you run the same ppkg file on each one and all your settings are done.. Lets say you have 20 pc and 10 have office and are video edit.
install the office ppkg on 10 and the video edit on the other, all your setting are done.. no need to reinstall 20 pc's one at a time with different software and settings..

windows reset windows, and the rest is in the custom provisioning packages .ppkg files for the average 2 pc family not a big deal one way or the other as there is a lot of good backup programs out there...