+ 0 Votes Did you create a New Sid? markp24 3 years ago Hi, Did you use Sysprep when creating the new image?or did you just load a PC and then image it and use that image for the other PC's? + 0 Votes No sysprep rouschkateer 3 years ago Just took one of the machines "as it was" out of the classroom, cleaned it up, and imaged that machine. + 0 Votes You do need to run sysprep markp24 3 years ago Hi, The issue may be caused by not using sysprep, , if you do not use sysprep, then the systems (even though you may change the host name) still have identifiers that are the same as the other systems that were created by this image, there for kick eachother off the network. Try recreating the image on a machine after running the systprep utility on it.I believe this will fix your issue.please let me know how it works out. + 0 Votes Hmm...but... rouschkateer 3 years ago If I hand-configure each NIC to have its own IP address, subnet mask, and gateway, as well as DNS, then will it still cause an issue? + 0 Votes Yes it will markp24 3 years ago Hi, there are still other OS items that ID a system.here are some artivcles and How to's for imaging a windows 7 systemhttp://www.symantec.com/connect/blogs/how-create-and-deploy-windows-7-imageshttp://blog.brianleejackson.com/sysprep-a-windows-7-machine-%E2%80%93-start-to-finish-v2i hope those helpthank you,Mark + 0 Votes Are you using Active Directory? IC-IT 3 years ago If so see if you can right click (Admin tools - AD Users and Computers) on one of the "bad " systems and check the event logs.You did un-join the build machine from the Domain and if using SMS uninstalled it and McAfee Framework?Edited to add; We have used Ghost to push out about 200 systems (25 -35 each time). We have not been using Sysprep. We did have to change the Default Ghost template to PCDOS from WINPE.