Windows 10 slow logon preparing windows

Question

Hi everyone,

I know this issue is around for quite some time. But, from what I experienced in my testing, whatever I tried didn't exactly help.
Here is what my problem: A domain user logs into a domain computer. policy applies within 10-15 seconds which is good because we deploy preferences like drive maps, printers, file and folder options and internet settings. after applying the policies the display shows "Please wait for the local session manager" for a second or two and than we get the "Preparing Windows" message for 30 seconds.
I tried configuring the following:

1. Disabled logon script delay
2. Disabled run logon script synchronously
3. Added the DelayedDesktopSwitchTimeout DWORD registry and set the value to 0

Although the logon time got shortened I still get a black screen for 10 seconds or more which could alert the users.

Our active directory is 2016 but our domain functional level is 2008 r2 because of historic reasons.
our windows 10 are 1909 and above.

Don't know where else to turn to for help.

Rahamim.

Answer 1

I think I found out what happens and I just need confirmation:

During the login stage, since I deployed both mapped drives and printers with the update option via GPO and, to have everything deployed according to the GPO, the "Please wait" window shows up to have the map drives and the printers deployed and configured correctly.

I found that out because when I tried to search for a way to optimize the login I found the policy "Change Group Policy processing to run asynchronously". I know this is for slow networks but I think that a delay will apply regardless in order to make sure that the CSE of drive maps and printers does the work properly.

Rahamim.

Answer 2

Please run;

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
repadmin /showrepl >C:\repl.txt
ipconfig /all > C:\dc1.txt
ipconfig /all > C:\dc2.txt
ipconfig /all > C:\problemworkstation.txt

then put unzipped text files up on OneDrive and share a link.

Answer 3

Looks like there may be some replication and KCC problems. You'll need to check the event logs for more details. Also if the 192.168.x.x addresses are not domain controllers then remove them from DNS.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 4

Hi,
Just checking in to see if the information provided was helpful.
Please let us know if you would like further assistance.
Best Regards,
Vicky

Answer 5

I have already sent you the files and you told me there was an issue with KCC and replication.

Sorry, yes you did (buried in the threading)

The event logs should have more details.

--please don't forget to upvote and Accept as answer if the reply is helpful--