• Open the Remote Desktop Connection window
• Expand the options section by clicking the down arrow in the bottom left corner
• Under the general tab under logon settings check the "allow me to save credentials" checkbox.

• Edited by Acreed02 Monday, June 15, 2015 5:05 PM
• Proposed as answer by ZigZag3143xMVP, Moderator Monday, June 15, 2015 5:06 PM

If you made sure to check that box, then check the "save my credentials" when entering them and you still get the error, then apply this global policy.

• Edited by Acreed02 Monday, June 15, 2015 5:26 PM corrected wording
• Marked as answer by F7H2fw Monday, June 15, 2015 9:50 PM

Your credentials did not work.
Your system administrator does not allow the use of saved credentials to log on to the remote computer 192.168.1.111 because its identity is not fully verified.  Please enter new credentials.  Rubbish.  This comes out of MSTSC.   I *AM* the system administrator and I would allow the use of saved credentials if I knew what Windows was complaining about.  What exactly is the solution to thi

• Open the Remote Desktop Connection window
• Expand the options section by clicking the down arrow in the bottom left corner
• Under the general tab under logon settings check the "allow me to save credentials" checkbox.

• Edited by Acreed02 14 hours 10 minutes ago
• Proposed as answer by ZigZag3143xMVP, Moderator 14 hours 8 minutes ago

That was the first thing I tried.

If you made sure to check that box, then check the "save my credentials" when entering them and you still get the error, then apply this global policy.

• Edited by Acreed02 13 hours 49 minutes ago corrected wording
• Marked as answer by F7H2fw 9 hours 24 minutes ago

Credentials Delegation (whatever that is) turns out to be relevant privilege in this case. Fix for system administrator not allowed to save credentials in remote desktop client. The article says to find the group policy for Allow delegating saved credentials, the default condition of which is to deny delegating saved credentials.  There is a related group policy for NT Lan Manager.  The article does not state whether the group policy change is required on the client machine or the server machine.  So I changed it in both places.  It also doesn't mention the required reboot.  Once done the group policy change works like magic.  (SNARK ON) Thanks to all the parties involved in formulating corporate policy that says nobody need document any of this. Special award to whoever approved the error message wording.  (SNARK OFF)