Youll still get duplicate SID errors. Actually, I think for workstations, they show up as warnings.
Granted, since SPNs on a workstation are few and far between, that isnt as important From: Sam Cayze [mailto:[email protected]] Sent: Wednesday, March 11, 2009 11:53 AM To: NT System Admin Issues Subject: RE: sysprep question 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, Im no expert, however, I would clone the machines *before* connecting them to the domain as its much easier to change the name before joining the domain. Thats just my 2¢ worth. John-AldrichTile-Tools 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, Ive 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? Im just doing 6 computers. Ive read that I do need to sysprep, and Ive read that I dont 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 dont 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 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
<<image001.jpg>>
<<image002.jpg>>
