<div>
First when you image machines you need to make sure you change the SID before rejoining to the domain.<br />
NEWSID works fine <a href="http://technet.microsoft.com/en-us/sysinternals/bb897418.aspx" rel="ugc">http://technet.microsoft.com/en-us/sysinternals/bb897418.aspx</a><br />
Now once you change the SID you should be OK but what i would aoso look at next is DNS settings.<br />
On that workstations is everything set to DHCP on the tcpip properties of the lan connection?<br />
Make sure under the advanced tab there is no dns server listed.<br />
Everything should be automatic.
</div>


<div>
The SID should have been changed by Sysprep when they were imaged. I am limited to MS approved software to reset the SID. Running ipconfig /flushdns makes it work when a computer is rebooted. If the computer is rebooted more than once the problem starts again.
</div>


<div>
Can you check all DNS settings from my previous post?<br />
Also just the cloned machines are having the issue or all lan clients?
</div>


<div>
RE:<br />
&quot;On that workstations is everything set to DHCP on the tcpip properties of the lan connection?<br />
Make sure under the advanced tab there is no dns server listed.<br />
Everything should be automatic.&quot;<br />
<br />
I checked and it was all set to automatic.
</div>


<div>
OK is it just the imaged machines or all lan machines having the issue
</div>


<div>
RE<br />
&quot;Also just the cloned machines are having the issue or all lan clients?&quot;<br />
<br />
It is just the recently cloned machines. 
</div>


<div>
I may try that tomorrow on a test machine tomorrow. <br />
<br />
Why would ipconfig /flushdns make it work when it reboots, then stop working after that? What does /flushdns delete that gets added back when it is added to the network?
</div>


<div>
flush dns remove the dns queries cached on the local machine.<br />
Flushing it removes that local cache.<br />

</div>


<div>
Would nbtstat -R help if I ran it after ipconfig /flushdns?
</div>


<div>
I dont think that will help much.
</div>


<div>
Tomorrow I'll try your suggestion of using newsid on a test machine. <br />
<br />
If that does not work, I'll try the &quot;repair option&quot;. <a href="http://support.microsoft.com/kb/289256" rel="ugc nofollow">http://support.microsoft.com/kb/289256</a>&nbsp; &nbsp;<br />
That runs these commands: <br />
ipconfig /renew<br />
arp -d *<br />
nbtstat -R<br />
nbtstat -RR<br />
ipconfig /flushdns<br />
ipconfig /registerdns<br />
<br />
If that does not work, I'll re Ghost them with a fresh image.<br />
<br />
My trial subscription runs out at midnight, so I'll deliver the points now. Thanks for your help.
</div>


<div>
Ah dont forget to renew this is such a fantastic place!<br />
Thank you for the pts
</div>


<div>
<div class="content wysiwyg-content">
Have about 25 PCs running XP SP2. About 12 of them are sometimes crashing. After a reboot, it takes a long time to log on, sometimes 20 to 40 minutes. It seems to be getting hung on loading personal settings. This is true with both preexisting profiles and first time logons. If I unplug the network cable, it does not get hung on loading personal settings. Removing all group policy had no effect. <br />
<br />
Yesterday I removed the group policies, I then ran Sysprep on them, I reset them and added them back to the domain. Then I added back the group policies. They all ran great for a day even with multiple reboots and heavy use. The next day the same problem is back.<br />
<br />
Ideas?
</div>
</div>


Have about 25 PCs running XP SP2. About 12 of them are sometimes crashing. After a reboot, it takes a long time to log on, sometimes 20 to 40 minutes. It seems to be getting hung on loading personal settings. This is true with both preexisting profiles and first time logons. If I unplug the network cable, it does not get hung on loading personal settings. Removing all group policy had no effect. 

Yesterday I removed the group policies, I then ran Sysprep on them, I reset them and added them back to the domain. Then I added back the group policies. They all ran great for a day even with multiple reboots and heavy use. The next day the same problem is back.

Ideas?

PCs getting stuck on loading personal settings. When unpluged they do not get stuck with a pre-existing user.

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).