New
#31
That's a good suggestion - I'll have a look at the first post in the next couple of days. (Might not get a chance tonight)
@Kyhi would it be OK with you if I put some of your stuff and links in the first post too?
No Problem
another good link > https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx
Really good information.
So let me see if I understand with a simple example.
Let's say that I install Firefox and set a bunch of settings in Firefox, like the homepage, disabling updates, etc.
Are you saying that ScanState will create a "package" that will have the installed program in it along with the Firefox settings changes in it?
yes....
Scan state is designed for use in audit mode (no user has been setup) so the setting exported are imported into the default user setting)
In a user state, scanstate also seems to pull some user settings (or so it seems by reading the MIG.xml) after creating the ppkg file..
Or maybe it is excluding it - not sure - long hard to figure out file.. Yes included, No do not would be eaiser to follow along.. seems like every section of the xml say the same thing to me..
I tested the windows 10 OS reset feature but that feature failed.. And had to restore partition with macrium image (created minutes before, testing windows reset..
Going back to the Firefox example, how does ScanState grab that program? Does it get the Firefox installer and then install Firefox automatically when the package is deployed? Or, does ScanState actually look at the files and registry keys that the Firefox installer created and changed and record those changes?
ScanState actually look at the files and registry keys that the Firefox installer created and changed and record those changes?
Problem is half the page is missing > https://msdn.microsoft.com/en-us/lib...(v=VS.85).aspx
When using wimboot in win81 - you could capture the install.wim with the /wimboot option
or
capture the install.wim and export it to a wimboot image by using the /wimboot option
the wimboot image was stored on the R partition and then applied to the W windows partition..
*******************
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx
My understanding now is you just apply the install.wim using the /compact option to get wimboot..
which places a compacted install.wim in C\Images\Code:dism /Apply-Image /ImageFile:X:\install.wim /ApplyDir:W:\ /Index:1 /Compact
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)
Now you have the full instance software (which you just captured into a ppkg) and a compressed instance of that same softwareCode:scanstate /tel:off /apps /drivers /ppkg C:\Recovery\Customizations\Apps_Drivers.ppkg /o /c /v:13 /l:C:\
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..
Inportant ... You MUST keep the C\images and C\Recovery Directories - Removing them Removes WindowsCode:DISM /Apply-CustomDataImage /CustomDataImage:C:\Recovery\Customizations\USMT.ppkg /ImagePath:C:\ /SingleInstance
Last edited by Kyhi; 23 Jul 2015 at 10:14.
I have tried the script that was in drop box for this but when I do the reset it always fails. What am I missing here?
Have you tried Reset without the provisioning package ??
When I tried Reset with the provisioning package it failed too.. Thought it was just the windows 10 reset failure others have complained about..
But I will now test without provisioning package.. thanks for the idea and info..