dcadler
asked on
Windows 8 Domain Login Still Takes 10 minutes to complete - Problem Continues
I thought this was solved under a prior question but it is still occurring so I am putting this out again.
To start with, I have a domain with two Windows 2012 domain controllers and several hundred newly imaged Windows 8 Pro laptops.
In my prior question, I thought that the following was true;
-----------------start initial assessment----------------
The first time I log into any of the laptop computers with an account that has not logged into the actual laptop computer before, it says logging in with the user name displayed for about 20 seconds and then the screen goes black for about 10 minutes before it comes back on and displays the Start screen.
After I log into a laptop the first time, subsequent logins to the same laptop with the same account takes less than 30 seconds. However, any time I log in with an account that has not logged into the laptop before, I get the 10 minute wait scenario.
-----------------end initial assessment----------------
I believed that the issue was caused by roaming profiles so I added some computer group policies to ensure that roaming profiles were disabled and this seemed to fix the problem.
However, now I have discovered that I still have the issue even if the user has logged onto the laptop before. It seems to be random as to whether a user who has logged in before will get a 30 second to start screen experience or a 10 minute to start screen experience. And sometimes a user who has never logged into the computer before will get a 30 second to start screen experience.
What is consistent is that when it happens, it as at about the 30 second mark. Then the screen goes black for almost 10 minutes, then the start screen appears and everything seems to work fine.
When I run GPRESULT /H and look at the result file, it does not list any errors.
All of the laptops are Lenovo Thinkpad Edge E531 units.
I have the same issue whether I am using the wired LAN connection or an 802.1x WiFi.
I still have existing Windows XP and Windows 7 computers on this network that do not exhibit this problem behavior when I log in as user with no prior local profile.
I have the following applications installed as part of the laptop base image. They all seem to be working properly;
Windows 8 Pro MOLP
MS Office 2010
Adobe Reader 11.0.0.3
Adobe AIR 3.7
Adobe Shockwave Player 12.0
Java RLE 7 update 25
Google Chrome (Stand alone Admin install)
MS IE IEAK Configuration
MS Silverlight 5.0
MS Visual C++ Runtime 2005SP1
MS Visual C++ Runtime 2008SP1
MS Visual C++ Runtime 2010SP1
MS Visual C++ Runtime 2012
Net Framework 3.5.1
Windows WSUS config
LightSpeed User Agent 2.01.06
Any ideas?
Thanks,
To start with, I have a domain with two Windows 2012 domain controllers and several hundred newly imaged Windows 8 Pro laptops.
In my prior question, I thought that the following was true;
-----------------start initial assessment----------------
The first time I log into any of the laptop computers with an account that has not logged into the actual laptop computer before, it says logging in with the user name displayed for about 20 seconds and then the screen goes black for about 10 minutes before it comes back on and displays the Start screen.
After I log into a laptop the first time, subsequent logins to the same laptop with the same account takes less than 30 seconds. However, any time I log in with an account that has not logged into the laptop before, I get the 10 minute wait scenario.
-----------------end initial assessment----------------
I believed that the issue was caused by roaming profiles so I added some computer group policies to ensure that roaming profiles were disabled and this seemed to fix the problem.
However, now I have discovered that I still have the issue even if the user has logged onto the laptop before. It seems to be random as to whether a user who has logged in before will get a 30 second to start screen experience or a 10 minute to start screen experience. And sometimes a user who has never logged into the computer before will get a 30 second to start screen experience.
What is consistent is that when it happens, it as at about the 30 second mark. Then the screen goes black for almost 10 minutes, then the start screen appears and everything seems to work fine.
When I run GPRESULT /H and look at the result file, it does not list any errors.
All of the laptops are Lenovo Thinkpad Edge E531 units.
I have the same issue whether I am using the wired LAN connection or an 802.1x WiFi.
I still have existing Windows XP and Windows 7 computers on this network that do not exhibit this problem behavior when I log in as user with no prior local profile.
I have the following applications installed as part of the laptop base image. They all seem to be working properly;
Windows 8 Pro MOLP
MS Office 2010
Adobe Reader 11.0.0.3
Adobe AIR 3.7
Adobe Shockwave Player 12.0
Java RLE 7 update 25
Google Chrome (Stand alone Admin install)
MS IE IEAK Configuration
MS Silverlight 5.0
MS Visual C++ Runtime 2005SP1
MS Visual C++ Runtime 2008SP1
MS Visual C++ Runtime 2010SP1
MS Visual C++ Runtime 2012
Net Framework 3.5.1
Windows WSUS config
LightSpeed User Agent 2.01.06
Any ideas?
Thanks,
McKnife
I read about that before - if I remember correctly, it only happens on sysprepped machines and looks like a bug that sysprep creates. Try without sysprep - if better, consider to involve microsoft support.
to verify the issue is it related to sys prep ... install a laptop using media and test...
if it's working fine that means there is something messing with base image...
i think you should do this
if it's working fine that means there is something messing with base image...
i think you should do this
ASKER
Any links to the sysprep info you are both referring to?
I have 640 laptops to deploy and I am using MDT2012 update 1 for the process. I have not heard of this issue before.
Thanks,
Dave
I have 640 laptops to deploy and I am using MDT2012 update 1 for the process. I have not heard of this issue before.
Thanks,
Dave
ASKER
Is there a way to tell what is going on during the login process when the screen goes black? A way to turn on logging of the login process?
ASKER
Unfortunately, that link did not have a posted solution. The difference between his issue and mine is that it doesn't always just happen on the first domain login. Sometimes, I have no issues and other times, it happens with each account login.
I use MDT2012 update 1 for my image deployment and followed the guidelines in the book Deployment Fundamentals, Vol. 4: Deploying Windows 8 and Office 2013 Using MDT 2012 Update 1 by Johan Arwidmark and Mikael Nystrom.
There are no errors in the event logs of the workstations. The GPResults report shows no errors. There is a warning referring to the AUInstallAgent taking too long but I believe that is a side effect and not the cause.
I will try procmon.
I use MDT2012 update 1 for my image deployment and followed the guidelines in the book Deployment Fundamentals, Vol. 4: Deploying Windows 8 and Office 2013 Using MDT 2012 Update 1 by Johan Arwidmark and Mikael Nystrom.
There are no errors in the event logs of the workstations. The GPResults report shows no errors. There is a warning referring to the AUInstallAgent taking too long but I believe that is a side effect and not the cause.
I will try procmon.
Based on the information you've given here, my best guess would be a login script or a Group policy preference trying to attach to a network resource that is not available, like a printer.
Do you have any login scripts or Group policy preferences configured? Do you have other computers running older versions of Windows using the same login scripts and policys that do not exhibit this behavior?
Do you have any login scripts or Group policy preferences configured? Do you have other computers running older versions of Windows using the same login scripts and policys that do not exhibit this behavior?
ASKER
I do have GPOs but when I review the GPResult file after the laptop finally displays the Start screen, all of the GPOs were applied successfully and there were now errors.
I will drop a sample laptop into a clean OU and log in with a clean user account to test.
I will drop a sample laptop into a clean OU and log in with a clean user account to test.
To make it really "clean", you would also have to block inheritance on that OU - just in case...
This wouldn't necessarily show up as an error. It could just be a script mapping drives that has a long timeout. Or the same with group policy preferences. If you map a printer or share with GPP, it might timeout but I'm not sure that would show up as an error in GPResults.
...but this wouldn't fit the problem description as it only happens at the first logon.
From the initial post in this thread:
"However, now I have discovered that I still have the issue even if the user has logged onto the laptop before. It seems to be random as to whether a user who has logged in before will get a 30 second to start screen experience or a 10 minute to start screen experience. And sometimes a user who has never logged into the computer before will get a 30 second to start screen experience."
Unless my reading comprehension is worse than I thought, I'd say it fits?
"However, now I have discovered that I still have the issue even if the user has logged onto the laptop before. It seems to be random as to whether a user who has logged in before will get a 30 second to start screen experience or a 10 minute to start screen experience. And sometimes a user who has never logged into the computer before will get a 30 second to start screen experience."
Unless my reading comprehension is worse than I thought, I'd say it fits?
I am sorry, I missed that - was it edited? ;)
No worries. :) I was probably late to the question, it was there when I got here.
ASKER
These are the specifics of the problem as it stands right now.
The problem: After a domain user types in their user name and password, the login process appears normal for the first 30 seconds. Then, instead of seeing the Start screen, the display goes black for anywhere from 10 to 20 minutes. After that, the Start screen displays and everything works properly.
This problem occurs intermittently. It is not specific to a user account or laptop computer. Often, the login works perfectly and the start screen displays in around 30 seconds after entering the user name and password. Other times, the same laptop or user account will have the long delay before the Start screen displays.
When the problem occurs, you can still move the mouse cursor around the screen even though the display is black.
This delay problem will happen when working at the local computer or through an RDP connection.
This problem never happens with Windows 7, Windows Server 2008, Windows Server 2008R2 or Windows Server2012. It only happens with Windows 8 Pro.
The problem: After a domain user types in their user name and password, the login process appears normal for the first 30 seconds. Then, instead of seeing the Start screen, the display goes black for anywhere from 10 to 20 minutes. After that, the Start screen displays and everything works properly.
This problem occurs intermittently. It is not specific to a user account or laptop computer. Often, the login works perfectly and the start screen displays in around 30 seconds after entering the user name and password. Other times, the same laptop or user account will have the long delay before the Start screen displays.
When the problem occurs, you can still move the mouse cursor around the screen even though the display is black.
This delay problem will happen when working at the local computer or through an RDP connection.
This problem never happens with Windows 7, Windows Server 2008, Windows Server 2008R2 or Windows Server2012. It only happens with Windows 8 Pro.
Did you try to inject and use procmon bootlogging?
ASKER
I am trying to set up procmon but it is difficult to do with this intermittent problem. This procmon, you have to log in first, launch procmon, set the boot logging option then restart and hope that the problem will happen on the next login. If not, you have to set the boot logging option again, then restart and try again.
So far, I have logged in on one computer with 12 different login accounts, going through the procmon setup each time, but have not been able to get the problem to occur.
It is hard to believe that Windows 8 doesn't have a better method for debugging activity during the login process. I used to be able to set a registry key in Windows XP and then I could view the debugging log after login, if there was a problem. That no longer works with Windows 8.
So far, I have logged in on one computer with 12 different login accounts, going through the procmon setup each time, but have not been able to get the problem to occur.
It is hard to believe that Windows 8 doesn't have a better method for debugging activity during the login process. I used to be able to set a registry key in Windows XP and then I could view the debugging log after login, if there was a problem. That no longer works with Windows 8.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK. I ended up putting the Windows Performance Toolkit on 8 of the laptops I am testing. That toolkit has the Windows Performance Recorder (WPR), which is the replacement for XPERF, and Windows Performance Analyzer (WPA). Part of WPR is the XBootMgr.exe, which allows me to record activities during the boot process. On each computer, I ran the command;
xbootmgr.exe -Trace Boot
This caused the laptop to reboot and start recording the boot and login process to the *.etl file.
After the laptop finally got to the desktop, ran the Windows Performance Analyzer and loaded the *.etl file that xbootmgr had generated.
I expanded System Activity-->Windows Logon-->Notification: StartShell-->SessionID2-->
In systems that did not have the delay, the AUInstallAgent didn't even take 1 second.
So, now I believe the issue has to do with the AUInstallAgent but I am having trouble finding information as to what it really is and what it is trying to do.
If I do a Search for AUInstallAgent in the Windows 8 search, I get nothing.
I looked in the local Windows services on one of the laptops I am testing and I find "Windows All-User Install Agent" is a service with a Service name of AUInstallAgent. I has a manual startup type. In the description, it says "Install AppX Packages for all users" and the path to executable is;
c:\windows\system32\svchos
After some googling, I have learned that the AUInstallAgent has to do with the install of Start Screen/Metro Apps and I found several posts saying that the service would not start and was preventing updates from the Windows store, but nothing about it causing slow domain logins.
So... does anyone have any ideas as to why this service seems to be randomly hanging for 600 seconds during domain user logon?
Thanks,
Dave
xbootmgr.exe -Trace Boot
This caused the laptop to reboot and start recording the boot and login process to the *.etl file.
After the laptop finally got to the desktop, ran the Windows Performance Analyzer and loaded the *.etl file that xbootmgr had generated.
I expanded System Activity-->Windows Logon-->Notification: StartShell-->SessionID2-->
In systems that did not have the delay, the AUInstallAgent didn't even take 1 second.
So, now I believe the issue has to do with the AUInstallAgent but I am having trouble finding information as to what it really is and what it is trying to do.
If I do a Search for AUInstallAgent in the Windows 8 search, I get nothing.
I looked in the local Windows services on one of the laptops I am testing and I find "Windows All-User Install Agent" is a service with a Service name of AUInstallAgent. I has a manual startup type. In the description, it says "Install AppX Packages for all users" and the path to executable is;
c:\windows\system32\svchos
After some googling, I have learned that the AUInstallAgent has to do with the install of Start Screen/Metro Apps and I found several posts saying that the service would not start and was preventing updates from the Windows store, but nothing about it causing slow domain logins.
So... does anyone have any ideas as to why this service seems to be randomly hanging for 600 seconds during domain user logon?
Thanks,
Dave
ASKER
The issue is definitely related to the All User Install Agent trying to check AppX packages against the registration source (Windows Store I assume. I am still trying to figure out why it is hanging but at least I know where to look now.
ASKER
I'm going to go ahead ands sign off on this. Even though it wasn't a fix, the recommendation for procmon got me digging until I found the Windows Performance Toolkit in the Win8 SDK and that resource allowed me to narrow down the reason for the delay.
Hi Mate,
What did you specifically do or change to fix this issue ? I am getting the exact same thing.
What did you specifically do or change to fix this issue ? I am getting the exact same thing.