Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, October 27, 2015 1:08 AM | 1 vote
Hi ,
Need a solution for the time it takes to setup a user when tries to logon for the first time on to a windows 10 machine in a domain environment
The time it takes for a user's first logon is too long, even when we disable the "Show first sign-in animation" setting. I work at a large community college where employees and students frequently bounce from one computer to another in the computer labs, often never using the same computer twice. They login using their domain credentials.
Any solution for this would be much apprciated
Thanks,
Sam
All replies (12)
Wednesday, October 28, 2015 1:10 PM | 1 vote
Hi,
Things to look for in the traces are the following:
Valid DNS responses (does the query response match what was queried for?)
Delayed or unanswered responses (both from the DNS servers to domain controllers)
Kerberos failures
SMB failures
Numerous TCP resets or retransmits
A specific Domain Controller consistently used when the issue happens (possible issue with the Domain Controller itself)
Please follow steps in these blogs to check your issue:
http://blogs.technet.com/b/askds/archive/2009/09/24/so-you-have-a-slow-logon-part-2.aspx
Troubleshooting the intermittent slow logon or slow startup
http://blogs.technet.com/b/instan/archive/2008/04/17/troubleshooting-the-intermittent-slow-logon-or-slow-startup.aspx
Troubleshooting slow logon issues on domain-joined workstation/server
http://blog.dabasinskas.net/troubleshooting-slow-logon-issues-on-domain-joined-workstationserver/
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Wednesday, October 28, 2015 9:55 PM | 2 votes
I am not talking slow logon for win7
this issue is only for Win10 freshly imaged computers
setting up computer takes long when a user logon to that machine for the first time
after that if that user logback its a quick process and a new user logons to same machine now it takes long to setup apps and setting up computer for first time use
Thursday, October 29, 2015 2:28 AM | 2 votes
I am not talking slow logon for win7
this issue is only for Win10 freshly imaged computers
setting up computer takes long when a user logon to that machine for the first time
after that if that user logback its a quick process and a new user logons to same machine now it takes long to setup apps and setting up computer for first time use
Sam,
I see that, but the cause of the issue could be similar. Please test the suggestions in my last post.
For the domain user, the first logon will load the roaming profile and apply all group policies for the first time.
Also, since this issue only happened on first logon, consider if the roaming profile is too large. Please check it.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Thursday, October 29, 2015 2:52 AM | 2 votes
the users don't have any roaming profiles as I keep saying it only happening for Win10 not for Win7
what i am saying here is its taking long time to setup apps n preferences
its not about slow logon its about win10 takes time to setup for the first time
Thursday, October 29, 2015 3:09 AM | 1 vote
similar issue
Thursday, October 29, 2015 8:54 AM | 1 vote
similar issue
what about configure the DNS ip as your DC ip to check the issue?
It should be some delay when trying to find the DC to configure the account for the first logon with domain account.
Also, let me know how long it will take and help to capture the logon trace:
Please install Windows 10 ADK:
Click on "Download the Windows ADK for Windows 10"
http://go.microsoft.com/fwlink/p/?LinkId=526740
Check steps "Using XBOOTMGR to capture slow boots, or slow logons caused by slow boots"
http://social.technet.microsoft.com/wiki/contents/articles/10128.tools-for-troubleshooting-slow-boots-and-slow-logons-sbsl.aspx#Installing_XPERF_to_capture_a_slow_boot_or_logon_trace
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Thursday, October 29, 2015 6:45 PM
There really shouldn't be any "active setup" or "app setup" running every time a new profile gets created. Put the registry changes in the default profile, and be done with it.
Maybe there's some way to disable these things with Sysinternals Autoruns?
Thursday, October 29, 2015 9:20 PM
Hi JS2010,
There really shouldn't be any "active setup" or "app setup" running every time a new profile gets created. Put the registry changes in the default profile, and be done with it.
what changes to be made in the default profile can you please highlight
Thanks
Monday, November 2, 2015 4:02 PM
I was talking to microsoft, not admins. There's probably a lot of complex registry changes, some probably based on the current username(!). Maybe using SYsprep CopyProfile one and only time is the best solution. Or somehow run those commands and figure out what the changes are using Aaron Margosis's app install recorder script or something.
Tuesday, February 9, 2016 12:20 PM | 1 vote
Yes, here newly installed Windows 10 says "Welcome" to domain user for 10+ minutes first time. No problem with Windows 7.
Thursday, February 11, 2016 2:51 AM | 1 vote
This needs to be fixed by Microsoft. It's a huge problem. First logon takes way, way too long.
It's not an AD issue.
It's not a Group Policy issue.
It's not an issue with the profile.
It's an issue with Windows 10.
Where are we with fixing this, Microsoft? This was reported months ago.
Thursday, February 11, 2016 3:35 PM | 1 vote
Microsoft: active setup and app setup should be completely done away with. Run it one time, not an infinite amount of times for every new user, and keep the changes in the default profile.