none
Unlocking Windows 10 PC takes too long RRS feed

  • Question

  • Hi we have an strange issue. we have 2 2012 r2 Dc and one 2019 DC , FSMO roles are on 2019 DC. We configure that 10 minutes after no input pcs are locked out. The clients report that when they wanna unlock their pc it wait welcome screen almost 1 minute and then unlocks pc. 
    Friday, July 5, 2019 6:55 AM

All replies

  • Hi,

    Based on my understanding , the clients applied the screen lock policy successfully , and the problem is the unlocking time is too long,right?

    Does this issue happen to all clients  or just some of them?

    Best Regards,

    Fan


    Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Monday, July 8, 2019 2:42 AM
  • Hi,

     

    Just want to confirm the current situations.

     

    Please feel free to let us know if you need further assistance.

     

    Best Regards,

    Fan


    Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Wednesday, July 10, 2019 9:13 AM
  • yes. not all clients  only some clients suffering this behavior. Yes unlocking time is too long.
    Friday, July 12, 2019 10:36 AM
  • - Run "setL" command on the client machines from where it is taking long to unlock.

    -This gives you the DC authenticating the Client. 

    -Check if that the DC present locally or the DC authenticating is a remote DC. (Do you have a local DC available as per your configuration?) If its a remote site then it has to talk to the other DC remotely and may taking sometime to unlock depending upon your WAN speed and all. 

    -If the client authenticating by a remote DC though you have a local DC present, need to check the configuration in Sites and Services. 

    Please let us know your findings. 

    Friday, July 12, 2019 4:37 PM
  • all clients and DCs located in locally only, 
    Monday, July 15, 2019 10:19 AM
  • Hi,

    In your situation ,i would recommend  to trace the process with process monitor tool .

    Best Regards,

    Fan


    Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Tuesday, July 16, 2019 1:42 AM
  • which process and which monitoring tool
    Wednesday, July 17, 2019 11:22 AM
  • Hi,

    Article for your reference.

    https://social.technet.microsoft.com/wiki/contents/articles/10128.tools-for-troubleshooting-slow-boots-and-slow-logons-sbsl.aspx

    Best Regards,

    Fan


    Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, July 18, 2019 1:55 AM
  • hi thank you for the article, i successfully generate trace file and open but can not analyse it. There are a lot of information here.
    Thursday, July 18, 2019 3:43 PM
  • Hi,

    Log analysis is not supported because of some security rules.

    If there is no progress, I would suggest you contact Microsoft Customer Services and Support to get an efficient solution:

    http://support.microsoft.com/contactus/?ln=en-au

    Have a nice day!

    Fan


    Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Friday, July 19, 2019 2:23 AM