Link to home
Start Free TrialLog in
Avatar of quicksilver9365
quicksilver9365

asked on

Windows XP stuck on "Running Startup Scripts" for 10 minutes

XP Pro fully patched laptop that when I take it home and try to log in it hangs at "Running Startup Scripts" for almost 10 minutes.

I am the Network Admin. We have a new SBS 2008 domain and this laptop has been connected to the domain locally before. I have added the GP timeout reg fix mentioned by MS but it did not fix it.
We are not using scripts on our domain other than the default that comes with SBS 2008 which is more like a policy than scripts.

Any thoughts? I cannot even find the local cached policy on the laptop through computer configuration.

I get Event ID 1054 which is normal since it can't find the DC but I want it to use cached credentials and bypass the script I believe. Very Frustrating.
Avatar of ThinkPaper
ThinkPaper
Flag of United States of America image

have you checked Group Policy and made SURE that you have no policies for startup scripts for whatever OU the machine is located in?

.. you may want to have 2 OU's - one for machines with cached logon and other machines that are always connected on the network.
Avatar of Will Szymkowski
Do you get the same result if you are logging on locally to that machine when it is off the domain? When you are logged in have you tried doing an rsop.msc on your computer to see what policies have been pushed or trying to be pushed?
Avatar of quicksilver9365
quicksilver9365

ASKER

After running RSOP.msc I foudn there are 2 startup scripts and both point to the serv

\\server.local\ClientAgent\machine\sbslogon.exe .....

I don't see a way to delete them since they point to a server share and I am at home on vacation.
ASKER CERTIFIED SOLUTION
Avatar of ThinkPaper
ThinkPaper
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
If you create an account locally on the machine and login to the machine locally the GPO's should not affect the logon times at all. I would try this and see if you have any issues. If this works better you could always copy your favorites, and documents to the local profile as well.