Slow Start-up Times

Posted on 2010-01-12
Medium Priority
Last Modified: 2012-05-08

   I'm in a Windows 2003 AD environment with a pretty large user base.  One of our business's is experiencing slow start-up times with their machines.  I've looked at the GPO's for this OU/business and it appears there is no heavy WMI filtering and the configuration settings for their machines are correct where as user configuration has been disabled and vice-versa with User accounts it's not looking for machine configuration.  Besides the obvious, such as investigating the log-on scripts for this particular OU, is there anything else you guys can suggest I look at or configure within AD or someplace else that might improve their start-up times?
Question by:itsmevic
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2

Expert Comment

ID: 26295784
Are they using the same Domain Controller than the rest of the offices?
Are they trying to connect to a non-existent printer/network folder?

Author Comment

ID: 26296170
yes using the same DC's as the rest of the office.  Not sure on the printers or network folders.  For arguments sake, let's say they aren't, then what might it be?

Accepted Solution

darkchild173 earned 2000 total points
ID: 26297238
You might want to check if "Always wait for the network at computer startup and logon to the computer" is enabled under GPO at Computer Configuration\Administrative Templates\System\Logon\. For optimised times, it should not be enabled.


Aside from that, this kind of problem in 99% of the times resides in faulty folder redirections, invalid mapped networked drives and missing printers. Also, you might want to check if the DNS servers that service those computers know about your domain and domain controllers.


Expert Comment

ID: 26302024
As stated before by darkchild, most of the times is a bad mapped folder/printer.
The script calls the folder/printer and waits for it to answer the packets. As it doesn't receive confirmation it sends the packet again and again until it timeouts and jumps to the next folder/printer.

The more failed connections the longer it will take to log on.

Featured Post

Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article shows the method of using the Resultant Set of Policy Tool to locate Group Policy that applies a particular setting.
Microsoft Office 365 is a subscriptions based service which includes services like Exchange Online and Skype for business Online. These services integrate with Microsoft's online version of Active Directory called Azure Active Directory.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
Suggested Courses
Course of the Month12 days, 10 hours left to enroll

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question