Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Clients take 10-15 to startup on my 2003 domain

Status
Not open for further replies.

guinnessman

Technical User
Mar 15, 2002
64
IE
I have a domain with two DCs running Server 2003. There are around 50 clients all running XP Pro. When any of the clients are started up, it can take 10 - 20 minutes before the logon (Ctrl-Alt-del) screen appears. The dialogue box "Running startup scripts" is displayed for most of that time.
The only scripts I have are two separate batch files in two separate OUs that map a couple of drives. Actually, the last drive in each batch file, often doesn't get mapped.

I had enabled "don't allow logon until scripts have run" or whatever the actual wording of that GPO setting is, however, even removing this does not increase the logon speed.
The managers are telling their users to just “log off” instead of shutting down because it simply delays things too long in the mornings.
This is not just happening in the morning though. Performing a reboot at any time causes the same long delay.


Remember, it's all just ones and zeros!
 
I would take a copy of the scripts and run them manually on a workstation. Put a pause statement between each command and troubleshoot success/failure and time of execution. If all is well with the scripts, check the size of your SYSVOL on the domain controller, if it is abnormally large start looking there.
SYSVOL contains GPOs, Scripts, and FRS. A large SYSVOL could slow logon times.
If you have multiple DCs in same domain check that the sizes are the same.
Read hear for more info:
 
The scripts run fine when run manually.
SYSVOL has now space issues and is not particularly large when compared with other SYSVOL folders in other domains that do not exhibit this slow startup behaviour.
FRS displays no errors.
The sysvol on each DC is the same size.

Remember, it's all just ones and zeros!
 
Space issue= lack of access permissions.

Check your SMB signing settings, I had an MS patch in July modify them causing real headaches

........................................
Chernobyl disaster..a must see pictorial
 
Sorry - mistyped.
SYSVOL has no space issues.

Remember, it's all just ones and zeros!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top