It provides an additional layer of security from malicious software and users while using fewer resources in the process. As stated on Microsoft Community, Network Level Authentication is "an authentication method that completes user authentication before you establish a full Remote Desktop connection and the logon screen appears." Once you allow remote connections, you also have the option of only accepting remote connections using Network Level Authentication. Under Remote Desktop, there are two options:Īllow remote connections to this computerĪllow connections only from computers running Remote Desktop with Network Level Authentication (recommended) I deleted all non Windows standard fonts (my company had a policy to add some corporate fonts) from registry hive "HKLM\software\microsoft\windows nt\currentversion\fonts" and it started working inmediately.Įven if the cause of registry corruption may be different for different users, procmon showed me what was wrong.Windows 10 offers the same Remote Desktop Connection options as older Windows versions. So I've examined a server with process monitor (procmon.exe) and noticed a lot of overflow errors related to registry "HKLM\software\microsoft\windows nt\currentversion\fonts". Only chance to get them back to normal was to overwrite the C:\WINDOWS\SYSTEM32\CONFIG\SOFTWARE registry from backup C:\WINDOWS\SYSTEM32\CONFIG\REGBACK\SOFTWARE (server has to be powered off), but that not always worked. Server works OK, services run normally and can connect remotely with powershell and WindowsAdminCentre and my usual remote tools. No way to get into safe mode: always black. VMware console is black, RDP connection is black and it even happened with a physical server (but only domain joined servers).
I had a similar problem with Windows Servers (a mix from 2012 to 2019):
0 kommentar(er)
