Turn off windows restore - that frees up a load
From the MS site:
What is Sysprep?Sysprep must be used only to configure new installations of Windows. You can run Sysprep as many times as required to build and to configure your installation of Windows. However, you can reset Windows activation only up to three times. You must not use Sysprep to reconfigure an existing installation of Windows that has already been deployed. Use Sysprep only to configure new installations of Windows.
fair enough i stand corrected but i still think its worth having a pre sysprepped image around
I'm not convinced that with XP infinite syspreping is a good idea. I use a default image with the basics that every machine receives windows, drivers, couple of system software bits, current windows updates as of when the image was created and CS3 because deploying it by GPO took 3 times longer than including the same data in the image.
I update the image roughly twice a year but in the 3 years I've been working here I've had to start from scratch a couple of times with most of the images because they became "broken" with multiple syspreps. Not the same exact problem each time but one image developed an issue that made it impossible to connect to WMI on any machine based on it. Another one developed a logon issue for users which repeatedly prevented roaming profiles applying. I did allot of hunting to find exactly what was wrong with them but in the end I remade the image from a clean XP SP3 disc and everything was great.
.Sysprep is not the same as activation... You can sysprep as many times as you want. You can only activate 3 times
If you used a VLK copy rather thank trying to activate every build (based on an OEM copy of XP)it would cease to be a problem?
Volume Licence versions of Xp don't need activation, and can be syspreped as often as you like.
HOWEVER, as sysprep occasionally stuffs up your build when running, it would suggest it WAS a good idea to keep a pre-sysprep inage unless you wish to risk a weeks work making your master image?
You can always delete it afterwards?
Imaging systems since NT4!
I have got into the habit of always using a pre-sysprep image anyway.
Basically I have a pre-sysprep image and a post-sysprep image. If I need to update my image, I load up the pre, make the change, update the pre, sysprep and update the post. If that makes sense?!
I know that you can sysprep as many times as you want but I feel more comfortable starting fresh each time.
thats what I do and keep images (ghost or Acronis trueimage) of each mainboardVolume Licence versions of Xp don't need activation, and can be syspreped as often as you like.
Might be better ways, but never had time to look at finding the best
Temporary Internet Files
User's temp folder
Windows Updates from C:\Windows ***NOTE: Do NOT delete the folder C:\windows\$hf_mig$ but you CAN delete any folder starting C:\windows\$NtUninstall***
(If you do the above, you cannot uninstall any applied updates!)
net stop wuauserv
Delete the contents of C:\windows\SoftwareDistribution
The above should save you anywhere between 2 and 6GB if that helps.
Just re-read and didn't realise the OP was from 2009! Also had a chuckle at those of you thinking that 12-28GB is big for an image!
Current image size with compression: 45GB
Last edited by JPShields; 4th March 2013 at 11:39 AM.
zag (4th March 2013)
There are currently 1 users browsing this thread. (0 members and 1 guests)