Sysprep Windows 7 Pro HELP Plz >>

Associate
Joined
21 Jan 2003
Posts
496
Location
Surrey
I want to build up one Windows 7 Pro PC, run a Sysprep tool like we could under Windows XP, then image with Acronis and roll the image out to 10 identical PC's.

Can a knowledgeable person refer me to an easy way of Syspreping a Windows 7 Pro system?

Any help is greatly appreciated.

Thanks

svan
 
Ok perhaps if you let us know where you are upto at the moment. Have you got your reference PC ready and if so have you tried to run sysprep on it yet?

The reference system is yet to be built. I want to make sure what Sysprep type method to use on Windows 7 systems...
 
Just have to run the sysprep utility in windows\system32\sysprep.exe

click the generalize tickbox and choose shutdown. It should work, but for more advanced sysprep features you have make an unattend.xml with WAIK.

So with Windows 7, its really a simple as that?.. Same as Win XP.. So thats all i need do to remove the SIDs?
 
So with Windows 7, its really a simple as that?.. Same as Win XP.. So thats all i need do to remove the SIDs?
That's the way I have done it before opening up the sysprep in Windows folder.

(not sure what SID is though =( )
 
You don't really need to use sysprep or even Acronis if they are identical machines. Just build the reference PC, use the built in Windows backup tool to create an image and then restore this to the other computers. All you need to do then is activate them. If you're still bothered about SIDs then just run sysprep on them individually.
 
Just have to run the sysprep utility in windows\system32\sysprep.exe

click the generalize tickbox and choose shutdown. It should work, but for more advanced sysprep features you have make an unattend.xml with WAIK.

Yep this is all you need to do. The generalize option removes the SID.
 
IIRC, you have to end the 'wmpnetwk.exe' process in order for sysprep to function correctly. I remember it causing me problems, and it's a wide-spread issue anyway.
 
I use w7 sysprep for deploying developer images at work.

I had a few annoying problems at the start - wasted around 20 hours work when it destroyed an image I'd been building :(

I though my problems were based on the wmpnetwk.exe issue, but from my notes taken at the time:

Set password for adminitstrator account
Keep administrator account disabled
Launch C:\Windows\System32\sysprep\sysprep Set to oobe + generalise
Shutdown
Take image with clonezilla

Also don't run sysprep more than 5 times (I was doing versions of builds for different departments from the same base images). You'll run in to the re-activation limit (I can't remember the exact terminology), even though fully licensed you do have to perform some slightly "dodgy" tasks.
 
Back
Top Bottom