Windows 10: Create Provisioning Package in Windows 10

Good news! Thanks for posting back with the details of what you did.

I'm sure you know this, but to reiterate for anyone else reading this- the Provisioning Package doesn't include user settings or files from C:\Users.

So you'd need to back those up separately. I believe if you reinstalled from a recovery drive, it would reset any preferences back to defaults too.

 

In Part 3,

Provisioning Package - Create in Windows 10


To run the commands using a batch file
there is a link to a bat file for 64bit machines.

for the last couple of days, the link ends up with "Problem loading page" I have tried in several browsers just to be sure.

Would appreciate assistance, thanks.

Bob

 

Hmm you're right. I can't access them either. *Sad
They definitely were there because I know I tested them.

I'll have a look tonight (I'm not at the computer that holds the files at the moment), but they aren't anything more than you'd get by manually typing in the commands at steps16-18

 

Hello Bob,

I didn't do anything, but those .bat files seemed to work for me when I tried them just now. Do they work for you too?

Regards
David

 

Thanks David,

I copied the instructions to a text file and manually typed them in yesterday [as you suggested 3 days ago and everything ran fine inc making the new recovery USB drive. At 73, I probably didn't read the instructions down further [so I could manually type them in] and thought it wiser to download the bat file and reduce my mistakes.


thanks again

Bob

 

Ah I'm glad it worked for you *Smile

 

I get an error xcopy not recognized

 

Was that using the batch files, or typing in the commands yourself?

 

Figured it out. When I copied the code some reason it was including the dot before the code started.

 

A bit late to the party...but thanks for taking the time to post this up. A great tutorial

*Thumbs

 

would you be able to use this process to transfer from an old win 10 pc to a new win 10 pc to transfer all your apps to the new one, then use scanstate and loadstate to update your settings?
Regards Chris

 

Funnily enough I've been wondering the same thing.

I've not given it a try yet though - other things getting in the way at the moment so not had time to 'play' recently.

One issue is that any problems on the old PC will be brought forward to the new one and possibly give undesirable effects.

I've not used the scanstate->loadstate combination myself so not sure how well it works to copy user settings, but in theory that part should work.

 

Hello, last year (Summer 2015) I used these provisioning pack instructions to create custom recovery drives on three now three-year old Acer Haswell Laptops. I notice though that I still have the usmt.ppkg files on the c-drives. The files are as large as 20GB. Can I simply delete them at this point?

With Windows 10 Anniversary out now, and since I make system images of the machines regularly, I am thinking of simply keeping one bootable USB drive with Windows 10 on it, just in case I ever need to boot from a USB. Turns out, I am not fussed about reinstalling software (Office etc.) in case of calamity. Also, I used Brink’s Reset Recovery Image instructions to point the PCs to recovery copies of the install.wim on other partitions of secondary drives anyway. Note: the three machines are no longer identical, since I installed m-SATA SSDs in two of them this Summer, for example, using Kari’s instructions on moving the user folders back to the old hard disks. The provisioning pack files seem to have migrated via Macrium cloning to the new SSD c-drives, hence the desire to cut down on large files on the SSDs… Any supplemental advice appreciated. I can post this as well to the thread on bootable USB drives if advisable. Thanks!

 

Yes, you can just delete the usmt.ppkg.

 

Yes I agree.
The provisioning packages are mainly intended as a way of deploying software, and have the advantage that a less-technical user could run a Reset and have their software be reinstalled. But if you're happy to reinstall software yourself, I'd delete them as suggested.