Windows 10: ADK 10: Windows Imaging and Configuration Designer

Yes - mostly the same screens as on a normal setup I think, including licence agreement

 

because you should be able to install Firefox - create a firefox.ppkg
install windows ADK and create a ADK.ppkg
Install Marcium and create a macrium.ppkg

then when you want that software just included the software ppkg into your build by placing it in your customizations folder

that is my understanding of how this all works, and how you can use the ppkg's in a factory deployment

Buyer wants Firefox - run firefox.ppkg and then included firefox.ppkg in customization folder to be used by Windows Recovery later to reinstall firefox..

 

Yep that's my understanding too, although it would be a time-consuming process to create all those individual ppkgs. I picked up somewhere that you can use .xml files to control what gets migrated which I guess would help to create lots of individual ppkgs, but I want to play with the more basic scenarios before I get to that one!

I guess that would also mean you can have more than one ppkg in the C:\Recovery\Customizations folder?

Thanks for your help and the info. *Smile It's bedtime in this timezone so I'm leaving it for tonight.

 

Time consuming to install then create the ppkg - yes the first time, - but to reset your PC 10 times.. that is a saving of 10 software re-installations..

And yes you can have more then one ppkg in the folder, but there is a clause I do not understand in the documentation

This is designed for large scale deployment and customization

Macrium is all that a PC owner needs..

Just nice to understand the process the FACTORY OEM will use

And yes by using the config.xml you can tell windows what you want installed from the ppkg

 

What/where is that clause?

Yeah I know what you mean, and Macrium will be my primary backup most of the time.

But there are scenarios when I might use this on a real PC:

• If I upgrade from Windows 7 or 8 to Windows 10, then want to clean install, if I can figure out config.xml, I think it should give a way to keep the OEM drivers and perhaps some of the software already installed and OEM utilities (basically anything where I don't have an install disk), but taking out the bloatware
• It gives a way to setup and customise a PC for a friend or relative with those customisations included in Reset and in a Recovery Drive
• I may have more than one computer... *Redface

 

So at this point what do I need to do to get this working? Do I need to specify a name for the packages?

 

hummm.

I have mounted the ppkg using dism and there is an xml file inside the ppkg.... actually just a fews lines

Oh rename .ppkg to .wim to mount...

 

I believe the reference device data asset is the file which scanstate /ppkg creates - yes?

So my understanding from that quote is that you can create loads of ppkg files using the Windows ICD, and they would all work together, but you can only have one ppkg from scanstate. And sadly scanstate is the only way (I think) to create a ppkg containing win32 software and drivers, although I think the ICD will let you create a ppkg with Universal Apps.

I guess this means you couldn't make your own firefox.ppkg and AdobeReader.ppkg as separate files (assuming you want to install them at the same time) but instead would have to use scanstate to make a combined ppkg.

Question on my list for testing at some point... if you load a ppkg manually from within Windows, does it automatically copy it into c:\recovery\customizations for later recovery?

 

reference device data asset - what does that mean??

mount your ppkg by renaming to a wim file and take a look at the enclosed xml..

the top part refers to the machine, I think and then a little down it says it found x number of apps..

https://msdn.microsoft.com/en-us/lib...ce_device_data

 

Do you already have the ADK downloaded (or at least the USMT part)?

If so, I think that I would delete any files from the c:\recovery\customizations folder (but also check that it exists) and try the following commands from an Elevated Command Prompt (that is, an Admin level command prompt)
Code: md c:\temp\Scanstate cd c:\temp\scanstate xcopy "C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\windows setup\x86\sources" xcopy /s /y "C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\User State Migration Tool\x86\*.*" scanstate /apps /drivers /ppkg c:\recovery\customizations\usmt.ppkg /o /c /v:13 /l:c:\temp\scanstate.log[/quote] The above is for 32-bit; for 64-bit it would be:
Code: md c:\recovery\customizations md c:\temp\Scanstate cd c:\temp\scanstate xcopy "C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\windows setup\amd64\sources" xcopy /s /y "C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\User State Migration Tool\amd64\*.*" scanstate /apps /drivers /ppkg c:\recovery\customizations\usmt.ppkg /o /c /v:13 /l:c:\temp\scanstate.log[/quote] This should create a package called usmt.ppkg in your c:\recovery\customizations folder, which is a special folder used by the Reset function and to create Recovery Drivers. It worked for me, anyway - good luck!

If you don' t have the ADK downloaded already, kyhi put the files post 54. You'll need to combine them into one folder though.

 

The above is for 32-bit; for 64-bit it would be:
Code: md c:\recovery\customizations md c:\temp\Scanstate cd c:\temp\scanstate xcopy "C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\windows setup\amd64\sources" xcopy /s /y "C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\User State Migration Tool\amd64\*.*" scanstate /apps /drivers /ppkg c:\recovery\customizations\usmt.ppkg /o /c /v:13 /l:c:\temp\scanstate.log[/quote] This should create a package called usmt.ppkg in your c:\recovery\customizations folder, which is a special folder used by the Reset function and to create Recovery Drivers. It worked for me, anyway - good luck!

If you don' t have the ADK downloaded already, kyhi put the files post 54. You'll need to combine them into one folder though.[/quote] Cool, so it looks like that missing piece of this puzzle is that the file has to be called usmt.ppkg otherwise it kills the reset function. I am ok with that. Also I didn't know the apps and drivers slash commands could be used at the same time.

Small Edit:
I just tried it and it appears to be resetting correctly now. I will know in a few more minutes if it restored the apps I installed. Now I just need to figure out a way to turn this into a compact OS install when resetting. *Cool

 

I'm not sure, but that name was the one in the documentation (not that the documentation is always correct) so I used it. Glad it's working for you.

I haven't got round to trying this in the current ADK, but I think the official route is:

• Save your ppkg file as above and copy it onto another folder/computer
• Get hold of the install.wim from the ISO of the edition you're trying to install
• Use the Windows ICD (within the ADK) and create a new project with that install.wim
• Import the ppkg from step 1 into your project as the Reference Device Data Asset (I think that's the name)
• Set the Compact option in the ICD and create an installation set that way

... but I've not tried this yet! And when I used the ICD in earlier versions of the ADK, the installation sets created at step 5 didn't work.

But I'd be tempted to try it anyway, because it would be useful to see how it works.

Another option is to create a Recovery Disk (with the ppkg in c:\recovery\customizations) and perhaps tweak something there to make it compact? Not sure how though.

 

I've just tried this and was rather surprised to find it created an install disk for me which actually installed Windows.

I had to use the 'Production Media' option in the ICD to make the 'Compact OS' option appear, but when I copied the resultant files onto a VHD and pointed it at a VM with a completely blanked disk, it installed automatically up to the normal Setup screen where you choose your language/region.

When I'd installed it, I could see that the apps I'd saved before (Firefox etc.) were there, and also some customisations I put into the ICD - for instance see the System screen below.





The only thing I'm not sure about is how to check whether the Compact function worked.... Hmmm.

 

Check the size of the install by looking at your c: drive. If its only a few gigs then you have it. If not then you might need to try again.

 

Yeah I'm going to compare by trying out the non-Compact version and see if it uses more space!

I forgot to say earlier - this posted by kyhi further up the thread is (if the documentation is correct *Rolleyes) another way to get the Compact installation. You'd need to boot from a WinPE disk (onto which you'd already added Scanstate) to run the steps , I think.

It may give a tidier result without leaving behind some of the working folders (windows.old etc.) which I noticed the ICD does.

which places a compacted install.wim in C\Images\

then you create a provisioning ppkg of your customizations to be stored in C\recovery\custiomizations
(Note: Capture custom image no longer used in win10)(it is a win8.1 option)

Code: scanstate /telff /apps /drivers /ppkg C:\Recovery\Customizations\Apps_Drivers.ppkg /o /c /v:13 /l:C:\[/quote] Now you have the full instance software (which you just captured into a ppkg) and a compressed instance of that same software

then you can singleinstance the ppkg into the compacted install.wim _ so the full software instance is removed and the OS and customizations are running from a compressed state..

Code: DISM /Apply-CustomDataImage /CustomDataImage:C:\Recovery\Customizations\USMT.ppkg /ImagePath:C:\ /SingleInstance[/quote] Important ... You MUST keep the C\images and C\Recovery Directories - Removing them Removes Windows[/quote]