+1. Making the image while it's part of a workgroup is important. To be clear, not following these steps exactly will still give you a machine that will connect to the network, but the event logs will show some interesting things and GPO���s w�����t work.
Dave -----Original Message----- From: Don Guyer [mailto:[email protected]] Sent: Thursday, March 12, 2009 6:42 AM To: NT System Admin Issues Subject: RE: sysprep question Make an image of the machine while it's in a workgroup. After bringing up the new computer (using that image), roll the SID while disconnected from the network, change the computer name, connect to network and join domain. This is all based on similar (or close enough) hardware, of course. Don Guyer Systems Engineer - Information Services Prudential, Fox & Roach/Trident Group 431 W. Lancaster Avenue Devon, PA 19333 Direct: (610) 993-3299 Fax: (610) 650-5306 [email protected] -----Original Message----- From: Ian Roche [mailto:[email protected]] Sent: Thursday, March 12, 2009 4:25 AM To: NT System Admin Issues Subject: RE: sysprep question Just on sysprep whats the easiest way to not have the mini setup run after you image a machine. I just want the machine to boot straight to windows after deploying the image and then add it to the domain . I have tried using the sysprep.inf using WDS but it doesnt seem to take !! I am probably missing something .. CheersOAm ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
