You should run sysprep immediately prior to capturing the image. When you apply the image onto the target hardware, the first thing it will do after booting is run minisetup. You can have minisetup join it back to the domain with an arbitrary name, or you can have it prompt you for the name.
In larger deployments I've typically had a script that goes back to some sort of database and gets the correct name and renames/joins the box post-sysprep. Thanks, Brian Desmond [email protected] c - 312.731.3132 Active Directory, 4th Ed - http://www.briandesmond.com/ad4/ Microsoft MVP - https://mvp.support.microsoft.com/profile/Brian From: John Aldrich [mailto:[email protected]] Sent: Wednesday, March 11, 2009 2:27 PM To: NT System Admin Issues Subject: RE: sysprep question Ahh... I did not know that. Good to know. I've just always sysprepped a machine prior to joining it to the domain. :) [John-Aldrich][Tile-Tools] From: Brian Desmond [mailto:[email protected]] Sent: Wednesday, March 11, 2009 2:59 PM To: NT System Admin Issues Subject: RE: sysprep question Yes. Sysprep will unjoin the machine as part of the process. Thanks, Brian Desmond [email protected] c - 312.731.3132 Active Directory, 4th Ed - http://www.briandesmond.com/ad4/ Microsoft MVP - https://mvp.support.microsoft.com/profile/Brian From: [email protected] [mailto:[email protected]] Sent: Wednesday, March 11, 2009 10:57 AM To: NT System Admin Issues Subject: RE: sysprep question Would it work just as well to take said staion out of the domain, then clone? It seems like it would, but I learn all kinds of things in this forum... -- Richard D. McClary Systems Administrator, Information Technology Group ASPCA® 1717 S. Philo Rd, Ste 36 Urbana, IL 61802 [email protected] P: 217-337-9761 C: 217-417-1182 F: 217-337-9761 www.aspca.org<http://www.aspca.org/> The information contained in this e-mail, and any attachments hereto, is from The American Society for the Prevention of Cruelty to Animals® (ASPCA®) and is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying or use of the contents of this e-mail, and any attachments hereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify me by reply email and permanently delete the original and any copy of this e-mail and any printout thereof. "Sam Cayze" <[email protected]> wrote on 03/11/2009 10:53:22 AM: > That would work too. > > > > From: John Aldrich [mailto:[email protected]] > Sent: Wednesday, March 11, 2009 10:50 AM > To: NT System Admin Issues > Subject: RE: sysprep question > Well, I'm no expert, however, I would clone the machines *before* > connecting them to the domain as it's much easier to change the name > before joining the domain. That's just my 2¢ worth. > > [image removed] [image removed] > > From: Reimer, Mark [mailto:[email protected]] > Sent: Wednesday, March 11, 2009 11:30 AM > To: NT System Admin Issues > Subject: sysprep question > > Hi folks, > > In my research on sysprep, I've come across conflicting information. > > I will be cloning xp machines (identical hardware). These machines > are all on a domain. Do I need to sysprep before cloning? I'm just > doing 6 computers. > > I've read that I do need to sysprep, and I've read that I don't need > to sysprep because the machines are on a domain (Windows 2003 native > in my case). > > Obviously after cloning, I need to go in and change the computer > name, so I don't get conflicts (unless, of course, I use sysprep to > change the names for me). > > Thanks for your wisdom in this. > > Mark > > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.0.237 / Virus Database: 270.11.10/1995 - Release Date: > 03/11/09 08:28:00 > > > > > > No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.237 / Virus Database: 270.11.10/1995 - Release Date: 03/11/09 08:28:00 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
<<inline: image001.jpg>>
<<inline: image002.jpg>>
