• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 795
  • Last Modified:

Very long shutdown time due to running shutdown scripts

I have a strange problem. We have some standard non-complicated shutdown scripts that we run for our XP SP3 clients. But for some reason when PCs are being shutdown or restarted they can sit at the 'running shutdown scripts' information box for 5-10 minutes, whereas other PCs pass this stage in the normal amount of time.

There is no difference in the scripts that these PCs run so I need to find out why or how this is happening.

Any ideas?
0
sydleg
Asked:
sydleg
1 Solution
 
PanicXCommented:
Usually timeout errors would cause long delays.  Can you give us the script code?
0
 
Iain MacMillanIT Regional Manager - UKCommented:
could be delays in shutting down some services/drivers.  are all the systems running the same software packages.  have you applied the latest UPHClean (User Profile Hive Clean-up) that was released to finally get rid of problems with user profiles not unloading.  Last update Sept. 2010

You can find the latest v1.6g here - we now have this applied to almost all our XP systems now.

http://www.microsoft.com/downloads/en/details.aspx?FamilyId=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en
0
 
gjoaCommented:
are the roamingprofiles large?
try without roaming profiles.
are rights a problem?
network problems? try a different port
what changed in the network/PCsettings/Usersettings?
when did you had a workable situation
0
Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

 
Jared LukerCommented:
I agree that it's probably time out problems.  Are you calling an executable that might not be available at shutdown.  In VBSCript, if you do a wshshell.run to a target that does not exist or can not be accessed, then it'll take a long time to time out and move on.
0
 
sydlegAuthor Commented:
Thanks for the pointer to check the script code. Even though I am not sure why the script times out only some PCs, i disabled it. I did want some clues about how to monitor the code while it is running after log off.
0
 
PanicXCommented:
Thanks for the points.  Usually the best way to monitor the script on these machines would be to modify the script.  Insert diagnostic logging comments with timestamps,  something like,
echo "Disconnecting Drive Q:"  >> logfile.txt
Then examine the logs for answers.
I'd recommend making a new question and posting your script, ask for optimizations and diagnostic troubleshooting tips.
0
 
sydlegAuthor Commented:
Thanks again for further follow up :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now