• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 783
  • Last Modified:

Sysprep and Windows 7

Have a couple questions regarding Sysprep with Windows 7:  

Is it possible to Sysprep over a previously Syspreped image in Windows 7?  Is this going to create any conflict in the unique SIDs on a network?  (Background details: We recently sysprepped an image using OOBE and generalize, captured the image using ImageX, found out the captured image file (.WIM) was corrupt and wouldn't load into WDS.  So rebooted up the image that was sysprepped and captured and re-sysprepped w/ OOBE and generalize mode, re-captured that image w/ ImageX to create a second .WIM image file, then successfully uploaded that file to WDS for deployment. Loaded that image and it works just fine.)  

Could someone provide a logical answer?

Thanks,
Drew  
0
navitaire
Asked:
navitaire
2 Solutions
 
EshuunDaraCommented:
Yes you can, and it will work without problems, however there is a limit to how many times you can reset the licensing information, so this will only work a few times (I believe the limit is 3 off the top of my head).
0
 
cantorisCommented:
I've never had any issues with sysprepping and capturing images repeatedly although have yet to do this with Windows 7.  The current (Windows 7 era) AIK reference materials do though include the sentence "Typically while creating a deployment image, you will run the Sysprep command multiple times."  So in there you can see multiple sysprepping is expected and therefore fine.
As EshuunDara rightly says, licensing can be an issue though as you can only "rearm" it three times (which normally occurs during generalisation).  You can set a value in the answer file to stop it rearming under Microsoft-Windows-Security-SPP called SkipRearm (set it to 1) if you are going to be sysprepping an image repeatedly before it's finally ready to go into production use as a WDS image.  Once this value is set to 0 again and the system sysprepped, the licensing will rearm and set the activation timer set back to 0 again.
0
 
AltaSensCommented:
In regards to Rearm, this would be not applicable when using OEM SLP (system-locked preinstallation) Windows (7), right?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now