Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: Acceptable Domain Logon Times

25 Oct 2011   #1

Windows 7 32 Bit
Acceptable Domain Logon Times

Hi All,

First time poster, long time reader.

I was wondering if anyone could help me out here.

I am an IT manager at a school (800 users in total). I have only recently taken over, and we have migrated to Windows 7 (also upgraded the domain to Windows 2008 R2). The school employs a rather expensive IT consultant (friend of the Bursar), who is constantly on my case, as i literally ripped his solution apart (RM if anyone knows that name?) as I convinced the school to move to a more standard / corporate solution for the IT.

This consultant is stating that the performance (logon times) are slow, and i wanted some feedback on the people on here.

In a nutshell,

- Windows 7 desktops (32 bit, Professional)
- Windows 2008 R2 domain.
- GPO used obviously for locking down the OS - though a low number of GPO's
- GPP used for mapping of drives (students get 2 drives, staff up to 6 depending on role)
- GPP used for mapping printers (30 printers onsite, but never more than 3 printers mapped per user session)

On average it takes approx 25 seconds from log on to the desktop.

I've always though that if the log on time was below 30 seconds in the above environment then that was acceptable? Not blistering, but certainly not "slow"?

Any feedback would be appreciated.



My System SpecsSystem Spec
26 Oct 2011   #2

Windows 10 Pro x64

Assuming the rest of the logon time is similar, 30 seconds is pretty good. I generally don't focus specifically on one section unless it stands out as significantly slower than the rest of the boot process, either. As a quick aside, I would say that on reasonably middle-of-the-road hardware in today's sense, anything quicker than 2 and a half minutes from POST to logged in is quick, and anything in addition to that needs to be considered in the context of the environment (are you doing a lot of GPP, whcih slows down logon? Running logon scripts? Lots of services to start, especially antivirus, app virtualization, etc? Do you have a baseline to compare this to?).

As someone who deals with a lot of what you're questioning now as a day-to-day job, I would say one of the most important things to do when you're considering boot performance on client machines is to have a reasonable representation of the hardware in the environment (as many of the models you would expect a user to have at their desk as possible), and the image you expect to push out to those machines, as your launching point for starting to clear the fog on your own environment's performance numbers. Using xbootmgr to take boot traces, you start by seeing what you have pushed to the client machines and how it is performing on the hardware you have in it's current form (taking 5 - 10 traces to normalize times is a good idea). Then, you look at ways to shore up those times, looking at things like what can you delay, or what can you remove; are you defragmenting the disk well, and is superfetch / readyboot working properly, as examples.

Once you've gone ahead and tackled the kinds of things that you can change or clean up, you re-push the new image with changes down to the client machines, and you re-test with the same methodology, noting the (hopefully) faster boot times. Thiose are your baselines, and you keep those handy for comparison. Any time you change your hardware models in your organization's baseline, you need to re-test and make sure your baselines are up to date with the new hardware. The same thing holds true for your image - if you change that, you want to re-take the numbers so you have them for comparison. The real takeaway is that guesswork is just that - inaccurate and as likely to be wrong as it is right. Having hard numbers to compare in your environment with what it looked like when it came out of the oven, versus what a user might be seeing if you trace their machine in it's current state, is the only way to actually be able to answer those questions with hard data that can back up your findings.

Then, and only then, will you know what your image and domain configuratiion do to boot times, and be able to answer the questions you are running into right now. In general, though, boot performance is more dependant on things like disk fragmentation, poorly performing antivirus software, driver delays, or network issues than you usually see with group policy performance delays - it's not that they don't or can't happen, they just usually aren't an issue in the overall picture (and just as with anything, lots of policy settings coupled with lots of preference items, especially if your policy calls lots of group policy extensions or re-ACLing of filesystem or registry locations due to what you set, can indeed show performance delays that you need to accept can happen).
My System SpecsSystem Spec

 Acceptable Domain Logon Times

Thread Tools

Similar help and support threads
Thread Forum
Initial logon Windows 7 - AD domain
I have a Windows 7 PC that is part of a domain, when the user goes to login, they hit CTRL-ALT+DELETE, then choose the profile to login to (Last known user / other user). In Windows XP, the login window would come up with the last know user name without hitting C+A+D.. I am not worried about the...
General Discussion
Logon with DUN locks domain account
Hello, Just figured out how to "Logon using Dial-up networking" in 7 enterprise. My VPN connection establishes but immidiately disconnects because something in the process is locking my domain user account. Ideas? Thanks, Jeff
Network & Sharing
Force only domain logon?
My users are kind of getting used to the new login screen. I have set the Default Domain Name in the regisytry and/or GPO. However, that default domain name seems to only work on the FIRST ATTEMPT. Should a user make a typo and login fails, the machine reverts over to Login to: localmachine...
Network & Sharing
Windows 7 Domain Logon takes 6 minutes
Can anyone help, this is turning out to be a nightmare. Got an image ready and use sysprep to add the PC to the domain and use the copy profile set to YES to make all users use the default profile... The profile is around 100MB which isn't so bad judging by the amount of software we have on...
Network & Sharing
Domain logon
I was wondering if its possible to stop using the 'slash' style logon, logoff and lock workstations screens when connected to a corporate domain, in similar style to how NT and W2K worked. If I recall correctly, in XP if its a member of the domain it reverts to this method and does away with the...
Network & Sharing

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 21:02.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App