Slow domain login on Windows7, but fine on XP
Hi
We have a Server 2008R2 domain, and are currently using XP clients, which take on average around 10 secs to logon and 14 secs to logoff. I've just purchased 2 new HP laptops with Windows 7 (64-bit) and both of them take about 2mins
to logon and 4:30 mins to logoff. Something's obviously not right but I'm finding hard to troubleshoot the issue. It is not down to the solid colour desktop background bug and it's not down to login scripts or local printers, as some other posts have suggested.
- There's a couple of errors in Event Viewer...
Application of user policy caused a slow down in the system start up process:
Name : PreShellInit
Total Time : 122373ms
Degradation Time : 118373ms
Incident Time (UTC) : 2011-12-12T15:11:33.687200400Z
and
Windows has started up:
Boot Duration : 207302ms
IsDegradation : true
Incident Time (UTC) : 2011-12-12T15:11:33.687200400Z
I'm not quite sure where to go from here, any suggestions?
thanks
Carter
December 12th, 2011 11:40am
getcarter15 wrote:
Hi
We have a Server 2008R2 domain, and are currently using XP clients,
which take on average around 10 secs to logon and 14 secs to logoff.
I've just purchased 2 new HP laptops with Windows 7 (64-bit) and both
of them take about 2mins to logon and 4:30 mins to logoff.
Something's obviously not right but I'm finding hard to troubleshoot
the issue. It is not down to the solid colour desktop background bug
and it's not down to login scripts or local printers, as some other
posts have suggested.
- There's a couple of errors in Event Viewer...
Application of user policy caused a slow down in the system start up
process:
Name : PreShellInit
Total Time : 122373ms
Degradation Time : 118373ms
Incident Time (UTC) : 2011-12-12T15:11:33.687200400Z
Are these the only slow downs you see in Event viewer? Did you search
for event ID 100-100 in the Microsoft - Windows -
Diagnostics-Performance log?
If these are the only slowdowns you need to look into your user
policies in effect. If you are running extensive scripts and accessing
various remote resources via your policies this time can be quite
normal, too.
and
Windows has started up:
Boot Duration : 207302ms
IsDegradation : true
Incident Time (UTC) : 2011-12-12T15:11:33.687200400Z
Can you post the content of the details tab for this event.
I'm not quite sure where to go from here, any suggestions?
thanks
Carter
Wolfgang
Free Windows Admin Tool Kit Click here and download it now
December 12th, 2011 4:53pm
WolfP wrote:
getcarter15 wrote:
Hi
We have a Server 2008R2 domain, and are currently using XP clients,
which take on average around 10 secs to logon and 14 secs to
logoff. I've just purchased 2 new HP laptops with Windows 7
(64-bit) and both of them take about 2mins to logon and 4:30 mins
to logoff. Something's obviously not right but I'm finding hard
to troubleshoot the issue. It is not down to the solid colour
desktop background bug and it's not down to login scripts or local
printers, as some other posts have suggested.
- There's a couple of errors in Event Viewer...
Application of user policy caused a slow down in the system start
up process:
Name : PreShellInit
Total Time : 122373ms
Degradation Time : 118373ms
Incident Time (UTC) : 2011-12-12T15:11:33.687200400Z
Are these the only slow downs you see in Event viewer? Did you search
for event ID 100-100 in the Microsoft - Windows -
That should have been event ID 100-110 - sorry for the typo!
Diagnostics-Performance log?
If these are the only slowdowns you need to look into your user
policies in effect. If you are running extensive scripts and accessing
various remote resources via your policies this time can be quite
normal, too.
and
Windows has started up:
Boot Duration : 207302ms
IsDegradation : true
Incident Time (UTC) : 2011-12-12T15:11:33.687200400Z
Can you post the content of the details tab for this event.
I'm not quite sure where to go from here, any suggestions?
thanks
Carter
Wolfgang
December 12th, 2011 5:14pm
Hi Wolfgang, thanks for your reply.
No, there are several other errors in Event Viewer relating to slow logon, some of them critical. A recurring one is a 101 error for our Antivirus taking "longer than usual" to start up. As a test i tried uninstalling the AV software and
tried it again and this time it took about 1:30 to log in so this is definitely a contributing factor and i'm looking into it's configuration to see if i can change anything to make a difference. I understand that 2-3 minutes isn't a VERY long time
to log in but as XP only takes about 10 seconds i can't help but wonder if there is a setting somewhere that I've missed. Would you say it's expected that W7 generally takes longer to log into a domain?
here's the details of the second Event I mentioned anyway....
Log Name: Microsoft-Windows-Diagnostics-Performance/Operational
Source: Microsoft-Windows-Diagnostics-Performance
Date: 13/12/2011 09:42:54
Event ID: 108
Task Category: Boot Performance Monitoring
Level: Critical
Keywords: Event Log
User: LOCAL SERVICE
Computer: myLaptop.myDomain.com
Description:
Application of user policy caused a slow down in the system start up process:
Name : PreShellInit
Total Time : 111964ms
Degradation Time : 107964ms
Incident Time (UTC) : 2011-12-13T09:38:30.734000500Z
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{CFC18EC0-96B1-4EBA-961B-622CAEE05B0A}" />
<EventID>108</EventID>
<Version>1</Version>
<Level>1</Level>
<Task>4002</Task>
<Opcode>33</Opcode>
<Keywords>0x8000000000010000</Keywords>
<TimeCreated SystemTime="2011-12-13T09:42:54.841259300Z" />
<EventRecordID>60</EventRecordID>
<Correlation ActivityID="{02EB4C50-F800-0002-E6EE-57F97AB9CC01}" />
<Execution ProcessID="1604" ThreadID="4192" />
<Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel>
<Computer>myLaptop.myDomain.com</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="StartTime">2011-12-13T09:38:30.734000500Z</Data>
<Data Name="NameLength">13</Data>
<Data Name="Name">PreShellInit</Data>
<Data Name="TotalTime">111964</Data>
<Data Name="DegradationTime">107964</Data>
</EventData>
</Event>
I'll update if i find a solution
thanks
Free Windows Admin Tool Kit Click here and download it now
December 13th, 2011 6:04am
Hi,
Please take a view at the similar thread below.
http://social.technet.microsoft.com/Forums/en-US/itprovistaapps/thread/c2dc0135-90bc-46a3-99de-c633346c43ea
Please see the reply by Eilatan.
Juke Chou
TechNet Community Support
December 14th, 2011 5:13am
getcarter15 wrote:
Hi Wolfgang, thanks for your reply.
No, there are several other errors in Event Viewer relating to slow
logon, some of them critical. A recurring one is a 101 error for our
Antivirus taking "longer than usual" to start up. As a test i tried
uninstalling the AV software and tried it again and this time it took
about 1:30 to log in so this is definitely a contributing factor and
i'm looking into it's configuration to see if i can change
anything to make a difference. I understand that 2-3 minutes isn't a
VERY long time to log in but as XP only takes about 10 seconds i
can't help but wonder if there is a setting somewhere that I've
missed. Would you say it's expected that W7 generally takes longer to
log into a domain?
here's the details of the second Event I mentioned anyway....
Log Name: Microsoft-Windows-Diagnostics-Performance/Operational
Source: Microsoft-Windows-Diagnostics-Performance
Date: 13/12/2011 09:42:54
Event ID: 108
Task Category: Boot Performance Monitoring
Level: Critical
Keywords: Event Log
User: LOCAL SERVICE
Computer: myLaptop.myDomain.com
Description:
Application of user policy caused a slow down in the system start up
process: Name : PreShellInit
Total Time : 111964ms
Degradation Time : 107964ms
Incident Time (UTC) : 2011-12-13T09:38:30.734000500Z
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Diagnostics-Performance"
Guid="{CFC18EC0-96B1-4EBA-961B-622CAEE05B0A}" />
<EventID>108</EventID> <Version>1</Version>
<Level>1</Level>
<Task>4002</Task>
<Opcode>33</Opcode>
<Keywords>0x8000000000010000</Keywords>
<TimeCreated SystemTime="2011-12-13T09:42:54.841259300Z" />
<EventRecordID>60</EventRecordID>
<Correlation ActivityID="{02EB4C50-F800-0002-E6EE-57F97AB9CC01}"
/> <Execution ProcessID="1604" ThreadID="4192" />
<Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channe
l> <Computer>myLaptop.myDomain.com</Computer> <Security
UserID="S-1-5-19" /> </System>
<EventData>
<Data Name="StartTime">2011-12-13T09:38:30.734000500Z</Data>
<Data Name="NameLength">13</Data>
<Data Name="Name">PreShellInit</Data>
<Data Name="TotalTime">111964</Data>
<Data Name="DegradationTime">107964</Data>
</EventData>
</Event>
I'll update if i find a solution
thanks
Yes, that is essentialy the same as the other event in your original
post. Did you already look into the details of the user policy?
BTW did you look into the details Tab of the startup event, which shows
the total boot duration, that is really very informative, too.
Wolfgang
Free Windows Admin Tool Kit Click here and download it now
December 14th, 2011 4:56pm
Do you have any applications assigned via group policy?
Are all of your applications compatible with Windows 7.
From your description i am getting that most of your network is running windows xp and your are slowly introducing Windows 7.
Check all of your installed application and see if they are compatible with Windows 7, you may need to start blocking some of them from Windows 7.
December 14th, 2011 11:31pm
Hi
yeah everything is compatible with Windows 7 and although we do have some Group Policy settings, none of them are related to applications. Actually, once logged in, every user connects through RDP to a terminal server to do their work so there is very
little software installed on the clients, apart from AV. I'll check the details of the details of the startup event and post back
Free Windows Admin Tool Kit Click here and download it now
December 20th, 2011 10:47am
Hi,
OK, you may also choose to take a boot trace to find out which step or thing cause this delay, take boot trace via xbootmgr which is a part of Microsoft Windows Preformace Toolkit.Juke Chou
TechNet Community Support
December 22nd, 2011 9:23pm
hi
ok, I've a boot trace with xbootmgr which shows the following...
The user profile really isn't that big so I don't think that it's size is the issue. I haven't mentioned before but a local login time is ok, it's just domain logins that are taking so long so I'm going to look again at Group Policies
and do some more digging.
Carter
Free Windows Admin Tool Kit Click here and download it now
January 4th, 2012 10:46am
Hi,
Please upload the trace file to Skydrive, we will help you analyze it.
Also, after disable HP serivices, how is it going now?Juke Chou
TechNet Community Support
January 5th, 2012 2:51am
I've never used skydrive before but have just logged in and tried to upload the .etl file but it exceeds the 100MB limit. Is the accompanying .cab file of any use? Who do i share it to?
Free Windows Admin Tool Kit Click here and download it now
January 5th, 2012 9:39am
ok
here's links to the ETL files, one with a domain login...
https://skydrive.live.com/redir.aspx?cid=c4e9a6411a0a7f9a&resid=C4E9A6411A0A7F9A!110&parid=C4E9A6411A0A7F9A!109&authkey=!AMOfO4oBcy_5AWk
and one with a local login...
https://skydrive.live.com/redir.aspx?cid=c4e9a6411a0a7f9a&resid=C4E9A6411A0A7F9A!111&parid=C4E9A6411A0A7F9A!109&authkey=!AKkOJ0hd-a0QEn0
I don't think they give us much information though.
I'm fairly sure this is network related as a local login is really fast and i think would have most of the same processes running at startup. Also it's very intermittient, sometimes the domain login can be very quick but not very often.
Also started getting this 5719 error in event log
This computer was not able to set up a secure session with a domain controller in domain DOMAIN due to the following:
There are currently no logon servers available to service the logon request.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator
January 6th, 2012 9:36am
OK, I think I've resolved this now. It was a combination of things: disabling unnecessary services at startup (particularly the HP ones) and the user profile. As it turns out the user's roaming profile had about 600MB of photos in it, which I had
previously removed (locally and on the server) but it must have synced when logged into another client and found it's way back in. After removing these, it was ok.
thanks for your help!
Carter
Free Windows Admin Tool Kit Click here and download it now
January 16th, 2012 6:57am
Hi,
Checkout this WMI hotfix ... you might find it helps improves boot times further (it did for me)
http://support.microsoft.com/kb/2617858 .
Give it a go and please vote as helpfull if it is
Thanks,
John
April 27th, 2012 9:03am