Active Directory
3 TopicsMSTSC fails to connect with AD account if Win10 remote and over VPN
Background: Server 2012 R2 with domain. SonicWall VPN. Windows 10 Pro host workstations. Remote Desktop connectivity has recently been failing for remote Windows 10 users connecting to their Windows 10 workstations over a VPN if they use their Active Directory credentials. It used to work. If we remote into the same Windows 10 workstation host with same Active Directory credentials on the inside of the LAN (no vpn), it works. If we remote into the same Windows 10 workstation host with Active Directory credentials over the VPN from a Windows 7 workstation, it works. Only the remote OS has changed from original working scenario. If we remote into the same Windows 10 workstation with local credentials (to that host workstation) over the VPN from a Windows 10 workstation, it works. It seems to only be the combination of the VPN, Windows 10 as the remote workstation, and Active Directory credentials. If we change any one of those three conditions, it works. This suggests something about how credentials are checked from Win10 over the VPN is different than from Win7, and it seems to have changed within the last one or two months (updates?). How do I get remote Win10 workstations able to connect with Remote Desktop on Win 10 hosts using Active Directory credentials over the VPN? Head scratcher. Thanks in advance. Mark Raintree822Views0likes2CommentsWindows 10 slow logon preparing windows
Hi everyone, I posted this https://docs.microsoft.com/en-us/answers/questions/434889/windows-10-slow-logon-preparing-windows.html but the answer I got didn't point me anywhere so I'm trying my luck here as well. 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 the 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: Disabled logon script delay Disabled run logon script synchronously 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.Solved14KViews2likes5Comments