RDS - the connection has been terminated because an unexpected server authentication certificate was received from the remote computer

Question

_{Monday, May 22, 2017 10:46 AM}

Hello,

since a few months I sometimes receive the following error when I try to connect to one of my Session Hosts:

"The connection has been terminated because an unexpected server authentication certificate was received from the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.

This error appears approximately on every ~5 connection to the Session Host and I only see it on Windows 10 machines (it seems our Windows 7 machine won't trigger this).

A bit more info: We use a Remote Desktop Collection with User Profile Disks (Remote Desktop - not Remote App).

After this error appears I receive the following Events in EventViewer:

20499 - Remote Desktop Services has taken too long to load the user configuration from server \xxxx.mydomainController.com for user xxx

1511 - Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.

Btw. I created this topic in the Windows 10 forum because of this thread: https:// social.technet.microsoft.com/Forums/SECURITY/en-US/dd5ba826-d131-43d9-8d1a-d8324dd5d5a1/rds-the-connection-has-been-terminated-because-an-unexpected-server-authentication-certificate?forum=winserverTS

Thanks for the help!

All replies (4)

_{Monday, May 22, 2017 12:44 PM}

Hello,

See if anything from this thread helps:

https://social.technet.microsoft.com/Forums/Windows/en-US/5871a96e-b80e-4c67-9b0c-1ff8f64565b4/windows-10-1607-update-not-working-with-remote-desktop-gateway-server?forum=win10itprogeneral

Regards,

Microsoft MVP (Windows and Devices for IT)

Windows Insider MVP

Windows Help & Support [www.kapilarya.com]

_{Tuesday, May 23, 2017 7:29 AM}

Hi,

Try to replace the current mstsc.exe and mstscax.dll from a system still running windows 10 build 1511.

Or using registry.

navigate to following registry key:

HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client

In the right pane of Terminal Server Client registry key, double click on the RDGClientTransport registry DWORD (REG_DWORD), set its value as 1.

About two event logs

1# 20499 - Remote Desktop Services has taken too long to load the user configuration from server

https://social.technet.microsoft.com/Forums/ie/en-US/c304382d-affb-4498-8aa6-0bd07feaa23f/event-id-20499-remote-desktop-services-has-taken-too-long-to-load-the-user-configuration-from?forum=winserverTS

the warning message is safe to be ignored

2# 1511 - Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.

https://social.technet.microsoft.com/wiki/contents/articles/3571.windows-user-profiles-service-event-1511-windows-cannot-find-the-local-profile-and-is-logging-you-on-with-a-temporary-profile.aspx

Delete the error SID and create a new profile

Regards

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Wednesday, May 24, 2017 8:31 AM}

Hi,

this did indeed help! It seems that the registry entry only enforces the option "Connect and don't warn me" under the advanced tab in Remote Desktop Connection.

While I am happy that I found a temporary solution I wonder if there is a better one than to change this setting on every windows 10 computer in the network.

But thanks so far!

Regards

_{Wednesday, May 24, 2017 8:56 AM}

Very well, glad to heat that you have found out a workaround by yourself.

You are welcome, I am happy to assist you with question.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].