1 of 1 people found this helpful
You don't necessarilly need to sysprep before capture. It all depends on what you are trying to achieve. You can simply capture an image and then run newsid afterwards if you wanted to. Sysprep obviously cuts out this step. I would recommend syspreping the machine and letting it shutdown. Once it shuts down then capture the image and deploy. Of course you have to make sure your sysprep file has most settings in it, or you will still have to touch each machine. Btw, are these XP or 7
These are XP SP3 machines.
They are not running NewSID against them after imaging.
In the past I have read up on this issue about the SID's and basically it said that domain SID's diminish the need for local unique SID's but unique local system SID's are still best practice. But this was for XP SP2. And my memory may not be that accurate.
So if this no unique local SID issue is creating concrete problems I would love to know what the problems are.
The systems are all either Dell E4200, E6400 or E6410's. They are pretty much alike chipset-wise and although I haven't yet played with it I'm guessing that a "golden image" could be prepared, sysprepped then instead of three images only have one master image.
You may want to read this article.
It is pretty good. I had to search for it for a while to track it down for you, since I read it when it first came out.
Once you are done with the article, read the comments.
The article basically states that SID doesn't matter.
Then in the comments users tell Microsoft why their SID does matter...because 3rd party software uses it and doesn't except multiple SIDs, because....etc...
It all the registry's fault.
I have alway felt that the registry was a lame idea. An opportunity of every application to completely trash the system.
No registry no need for SID's
Anyway, I am going to pursue getting my new employers to start using sysprep. I just found out that since SP3 customizations to the default profile are not copied unless you add a UpdateServerProfileDirectory=1 to the unattended section of sysprep.inf.
That and the possiblity of consolidated to one "golden image" instead of one for every model are enough good reasons to pull toward sysprep.
Also, keep in mind that LANDesk won't support the use of OSD without sysprepping. ;-) It's in the manual.
I found the following:
Best practice for XP clearly states SYSPREP YOUR IMAGES.
Now I just have to walk that line between being the new guy that solves problems and new guy that is a problem.