Windows 10 Creators Version (1703) RDP now fails to cache cridentials
We are using an ERP solution hosted on remote Windows 2008 servers. The connection is accomplished via RDP. We have 14 users with Microsoft Surface Pro 4's running Windows 10 that have updated to Creators Version 1703. Microsoft has made changes to RDP (specifically the two files mentioned in the attached document). We performed this work around on several machines and then last week two of the Surfaces applied new updates and this "broke" again. Near as I can tell Microsoft removed NTLM from this version of RDP which is still required to login to our hosted servers. Has anyone else run into this? If so, have you found a permanent solution? Very frustrating.
Guide-to-Fixing-RDP-Error-in-Window.docx
Guide-to-Fixing-RDP-Error-in-Window.docx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I have seen this myself and the only way I was able to "fix it" was to go to each PCs local "credentials manager" under both web and windows and remove saved credentials and then re-save/re-create them.
ASKER
Guys, thanks for the feedback. I want to approach this incrementally. We've tried the sledge hammer approach with command line changes and moving files which seems to revert after new updates. I want to try Lionel MM's solution which we have been considering but haven't had time to implement. Film at eleven on that. To McKnife's suggestion, getting specific configuration information from the hosting people amounts to pulling hens teeth. I will select one of you in a day or two as these computers are in and out of the office daily. I have to nail one of them down to test on. Thanks again.
I'd setup a test environment. Two VMs (10, 2008) will be enough.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You should take the time to setup a clean 2008 VM. Just ten minutes and you know.
ASKER
McKnife I don't have the resources to setup a 2008 VM
All that takes would be a 2008 server trial ISO https://www.microsoft.com/en-us/download/details.aspx?id=5023 and a hypervisor.
ASKER
McKnife,
I see what you are saying and I do appreciate your input. However, I'm forced in this situation to work with an outside source for a solution. I have forwarded all of these comments to them in the hope that they will review them and see what might be done on their end. I don't have control over this server. Doing a test in-house is of little value in garnering a solution. I believe it is clear enough that if both ends of the connection are running the latest versions with compatible settings it's going to work. Thanks again.
I see what you are saying and I do appreciate your input. However, I'm forced in this situation to work with an outside source for a solution. I have forwarded all of these comments to them in the hope that they will review them and see what might be done on their end. I don't have control over this server. Doing a test in-house is of little value in garnering a solution. I believe it is clear enough that if both ends of the connection are running the latest versions with compatible settings it's going to work. Thanks again.
ASKER
No other response was adequate
- Security Layer
- Encryption level
- Allow connection only from computers running Remote Desktop with Network Level Authentication.
https://social.technet.microsoft.com/Forums/windowsserver/en-US/58eafd83-18cf-4e78-ae13-b5a28f3370bb/weird-remoteapp-rdp-error-your-computer-cant-connect-to-the-remote-computer-because-a-security?forum=winserverTS