Solved

Windows 7 sysprep/generalize and rearm with WDS

Posted on 2010-08-23
4
3,789 Views
Last Modified: 2012-05-10
I am installing windows 7 in a school lab environment with Windows Deployment Services.  I need clarification on how the sysprep rearm flag is used when deploying administrative images.

1.  Does the 3 ream limit apply if the machine is activated when sysprep/generalize is selected?
2.  Does the ream limit follow the clones after they've been deployed or does it get reset on new hardware?  This would only allow us to update and redeploy the image 3 times.
3.  Does the skiprearm setting solve all of my concerns?  I'm worried that this could cause licencing problems and duplicate SIDs.

Windows 7 in our environment is new for this coming school year and would like to start off in the right direction.  I'm looking for a best practices scenario and any surprises I might encounter in regards to cloning with WDS and the Sysprep Rearm limit.

Thanks

BZ
0
Comment
Question by:tnorman
  • 3
4 Comments
 
LVL 22

Expert Comment

by:Adam Leinss
ID: 33505967
1. Yes
2. Yes.  You can only rearm an image or a clone of an image 3 times max.  
3. It doesn't, but it won't reset the CMIDs and your KMS counts won't go up.  See http://support.microsoft.com/kb/929829
I think that Mark Minasi preaches the use of skiprearm: http://www.minasi.com/newsletters/nws0807.htm
However, I did e-mail him to let me know that he should be careful in recommending to everyone without mentioning the CMID issue.  I can't remember what he responded, but he didn't seem too concerned.
0
 
LVL 22

Expert Comment

by:Adam Leinss
ID: 33506005
*e-mailed him to let HIM know.  
0
 

Author Comment

by:tnorman
ID: 33521481
I know this isn't a place to express opinions but this is incredibly annoying.

Thanks aleinss, please look at my workaround solution and see if you think this will work

1.  Sysprep with -norearm
2.  Image Capture and deploy images
3.  run "cscript c:\windows\system32\slmgr.vbs –rearm" on the clones or sysprep /generalize

This way I would have an image that I can manipulate forever and deploy as long as I rearm each machine after the clone.

Will this work?
0
 
LVL 22

Accepted Solution

by:
Adam Leinss earned 500 total points
ID: 33521916
sysprep /generalize on the unrearmed clones would work, I'm not sure about slmgr -rearm.  That might just reset the grace period.  Sysprep will create random SIDs for each one.
0

Featured Post

6 Surprising Benefits of Threat Intelligence

All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

Join & Write a Comment

One of the features I've come to appreciate about Windows 7 and Windows Server 2008 R2 is the ability to pin applications to the task bar. As useful a feature as I've found this, it does have some quirks.  For example, have you ever tried pinning an…
When you start your Windows 10 PC and got an "Operating system not found" error or just saw  "Auto repair for startup". After a while, you have entered a loop for Auto repair which does not fix anything and you will be in a  panic as all your work w…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
This Micro Tutorial will give you basic overview of the control panel section on Windows 7. It will depth in Network and Internet, Hardware and Sound, etc. This will be demonstrated using Windows 7 operating system.

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now