Slow logging process in all workstations and servers in the domain

Question

A few days ago, a problem started in this environment and now logging in any Windows 10 machine, or any server (except the domain controllers) takes more than 25 seconds. That is causing several other problems.

I have this escenario: a local domain running on domain controllers with Windows 2019 fully patched. The Domain functional level is Windows 2008 R2

This is affecting all users and client devices. When you hit enter, after typing the username and password you get the screen shown in the attached image, and after 25 or more second is that the username shows up in the screen and the real Login seems to start.

I ran dcdiag, SFC, DISM, checked replication, topology... and all those tools are showing that everything is ok, I moved my user account and my computer account to an OU that is not getting any GPOs and still I am getting the same problem of long delay to log in.

What can it be or what should I do to keep troubleshooting? Thanks in advance.

Answer 1

Hello there,

As you have stated that this a recent issue and it seems like you have done most of the troubleshooting steps , Have you made any recent updates that you are aware of on this device? If so try uninstalling them and check if this sorts out the issue

Are you using roaming profiles ?

Roaming profiles change the way group policy processing is performed. When roaming profiles are configured the processing is changed from “asynchronous” (background processing or multiple at a time) to “synchronous” (foreground processing or one at a time). This disables “Fast logon Optimization” which will delay the user getting the desktop by waiting for the network to initialize first.

So you have a slow logon https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/so-you-have-a-slow-logon-8230-part-1/ba-p/397103

Hope this resolves your Query !!

--If the reply is helpful, please Upvote and Accept it as an answer–

Answer 2

The problem is solved now. This solution worked

Removing the endpoints from Azure AD did it. (dsregcmd /leave). No idea why but it worked. It has nothing to do with Duo, the problem was affecting the logon in all devices, even those that had no Duo, Servers and Client endpoints