ADK 10: Windows Imaging and Configuration Designer

Kyhi said:

so did ADK get reset too ??

Ooh I'm not sure. I thought I'd play with the Recovery Drive so I blasted the setup (sorry). I'll see if it comes back from the Recovery Drive version. (I only installed USMT on the machine to save time, not full ADK.)

because our file package is the same, your temp\scanstate and my usmt

except you copied all the setup source files and overwrote usmt files

I'll test some more Name and location..

Guide said sub-folders not needed, source or usmt

Although scanstate when running the command can not find replacement manifeists and is using system manifists..

so you, like me, included the replacements manifists in the file package

Maybe it's because I have a very basic machine setup - one local account, and only a few apps installed (Firefox, Adobe Reader, VLC, 7Zip, and USMT).

USMT in Program Files came back after a Recovery Drive reinstall incidentally.

Also, I'm not running scanstate from Audit Mode. I realise I probably should be, although the documentation is of course vague on this, but on the other hand it does seem to work.

I saw the error on Replacement Manifests too, which is why I copied the sub-folders.

Figured ADK came back..

not temp\scanstate

I am in user mode too

I logged to the customizations folder and deleted the log - but left behind the mig.xml..

So that leaves me to think, leaving mig.xml in the customization folder was the issue with my script
Or the ppkg name - although when using ICD you create a name..

so think for sure mig.xml in customization folder was the issue...

And for those looks to follow David's script here are the needed ADK folders (rather then a full installation of ADK)

https://www.dropbox.com/s/4c24ojkmgc...ckage.zip?dl=0

Kyhi said:

so did ADK get reset too ??

I expect c\temp\scanstate did not get reset ??

After a recovery drive install, yes to the ADK in the C:\Program Files, but you are correct that c:\temp\scanstate did not get reset.

Curiously it did create c:\temp but it's empty!

Edit: Here's what File Explorer looks like after the Recovery Drive install.

did not copy USER files or windows related USER settings

which is good.. Reset windows with windows default settings and re-installed the program..

After reset you have to run through License agreement (OOBE) ??

Kyhi said:

did not copy USER files

Yes you are correct, as far as I can tell. I had to create a new account when going through the initial setup screens after recovery install.

so audit mode not required...


Windows Reset Windows and your ppkg reinstalled your 3rd party programs

See once again I do not think it was ppkg name, but rather mig.xml causing the issue..

Kyhi said:

did not copy USER files or windows related USER settings

which is good.. Reset windows with windows default settings and re-installed the program..

After reset you have to run through License agreement (OOBE) ??

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..