Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm in a network with thousands of workstations. There is a bunch of GPOs applied to all domain users, and also a couple of Startup scripts in GPOs.

When the workstations are starting up, there is a message saying "Applying Startup scripts" or something like that. And this takes some time. I would like to troubleshoot that issue, and point out which script(s) are taking the most time in the startup process.

How can I achieve that? Thanks!

share|improve this question
sorry for the link bomb but… – tony roth Oct 18 '12 at 18:45

A hanging Startup Script isn't too bad to troubleshoot. Using the Resultant Set of Policy (RSoP) too you should be able to get a list of the Startup Scripts applying to the computer. Since you only have a "couple" of Startup Scripts it's probably easiest if you look over the scripts individually and, if necessary, execute them as an Administrator (or as SYSTEM, if you'd prefer to completely simulate the startup process) to see which one is taking a long time to complete.

There's no good event logging, stock, that will show you which script is taking a long time to execute. I believe that verbose USERENV logging (search for the term "RunDiagnosticLoggingGlobal" to see what I'm talking about) would give you script execution start / stop events, but that's a lot of work to go thru if you only have a couple of scripts.

If I had a lot of scripts and no idea which one was slow I'd likely start w/ a binary search thru the scripts by denying the test computer rights to execute half of the scripts, then half-of-the-half, etc, until I located the problem script.

Fixing a broken script is probably beyond the mission of Server Fault, but this should let you isolate the slow script, at least.

share|improve this answer
Evan, you're an awsome man! Thank you so much! – Jonathan Rioux Oct 18 '12 at 22:48
The consensus is that I'm a tired, cranky, over-worked AI, actually. – Evan Anderson Oct 18 '12 at 22:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.