We have been deploying a new Windows (Only) environment over the past few weeks. We now have 4 2008 servers across 4 different sites that have the WDS role. The servers are all setup to respond to any client, deliver an image, join the computer to the domain and place the machine account in a specific OU. So far we have deployed windows to approx 1000 client computers.
The problem that we faced is a large number of computers coming up with naming conflicts. We were using a simple naming scheme based on the location and a incremented 4 digit number. The conflict arose because so many computers were coming up at once. We have since resolved the majority of this by using MAC address as the initial computer name.
1. We are still experiencing problems when a WDS managed computer is logged into the first time, renamed, and then rebooted. Sometimes we get the error that the computer name already exists. We can usually overcome this by deleting the duplicate computer name but since we are reimaging so many computers ofter times our techs unjoin the domain, rename the computer and then rejoin. This has the unwanted side effect of removing the computer account from WDS management.
2. We also have several instances when a computer will get the name of a computer from another site all together that was previously imaged via WDS. This causes some trust relationship errors and we begin "chasing our tails".
Any help with the issues described above would be greatly appreciated!!
Are you on Windows XP? If so, there is an update that fixed my domain joining headache. Let me know and I'll root it out for you.
The base image should not be attached to the domain. You are running sysprep -mini -reseal -reboot before taking the base image snapshot.
Yes, were deploying XP and the syspreped machine is not already on the domain prior to capturing the image.
Let me know if you find that patch you spoke of!!