Excruciatingly Slow Login - Server 2012 R2 Remote Desktop

So just to be clear, the login is slow when being accessed over the internet?

Check event logs on the server(s) for any errors.
Check firewall logs for any indication of delays or problems. In addition as a test remove any restrictions on rules related to the RDS servers and give the rule the highest priority.

@masnrock - I will definitely give the VMQ setting a try.

@Brian B - Not over the Internet, but via RDP on their internal LAN. So, for example, a user with a thin-client terminal users RDP to connect to the application server, but their login takes a very long time hanging on the Welcome screen.

@masnrock - one other thing: do you think it makes sense to disable the VMQ on the physical adapter itself (on the Hyper-v host) or on the virtual switch (via a PowerShell cmdlet on one of the VMs)?

I am only just recently getting heavily into administering this setup and have not had to do this particular operation before.

Thanks.  :-)

Thanks for clarifying. I got crossed up by that word "locally".

Is there any difference if you log on as a user from your own station versus a thin client? Just trying to narrow down if there could be any issue regarding policy.

Logging in over RDP, regardless of whether it is done from a PC workstation or thin-client takes almost two minutes (20-25 seconds to secure the connection and establish the session, then another 90 seconds or so while the "Remote Desktop Configuration", "User Profile Service", "Folder Redirection Policy", etc. do their thing. A local login by the same user (i.e. sitting at the server console itself - not using RDP) takes around 30-35 seconds . . . which is still rather slow. But it is waaaay better than the time lag I'm experiencing over RDP.

Interestingly, there are no errors or even warnings in the System Event Log of the VM.

Thanks for the response. Down to general troubleshooting of slow logon steps at this point. Have to think about what else I have seen before. I have come across slowdowns caused by printer redirection in the past. So that's one thing to check. Try with anti-virus off and also check DNS settings are pointing to internal DNS servers only. I'll see what else I can think of.

Thanks, I really appreciate your efforts. I'm pretty sure it's going to end up being something quirky and obscure (like the VMQ the other poster mentioned - which I still haven't quite figured out how I should deal with). I say this only because this environment is presently a lab/testing platform only. It won't become a live production environment until I have these kinds of kinks worked out. As such there are no printers or virus protection in the mix.

There is, however, a domain with a pair of DCs (also Hyper-V VMs) and DNS is configured properly as far as I can tell.

I do wonder if it might be some weird group policy processing thing - but, as I indicated above, there is not a single error in the System Event log of the servers I'm attempting to RDP into. I will check the DC event log next.

Thanks again.  :-)

Chris - To answer your VMQ question, both.

@masnrock - I had to do a little research to get the proper PowerShell cmdlet to disable VMQ on the Hyper-V hosts (they are running Server Core with no GUI). But, I found it and implemented the change. OMG!! Logins are now practically instantaneous!

Thank you!!!

:-)