Unable to Save Credentials Password For Remote Desktop(RDP)

本文提供了解决Windows系统不允许使用保存的凭据登录远程计算机的问题的方法,适用于连接不同域的情况。通过配置本地策略编辑器,允许使用NTLM只用于服务器身份验证的保存凭据,实现无需每次都输入密码的便捷连接。

Link:Unable to Save Credentials Password For Remote Desktop(RDP)


“Your system administrator does not allow the use of saved credentials to log on to the remote computer terminal.server.com because its identity is not fully verified. Please enter new credentials.”

Reason: This happens when trying to connect to a computer / server in another domain and no trust relationships exists. Windows then steps back to use NTLM and the default domain machine policy prohibits use of saved credentials. You can change this domain based or for a individual machine:

This security measure could frustrating when you connect and disconnect a lot to the same (or many) terminal server. To get rid of it and to be able to use saved credentials in this situation you need to configure the following:


Doesn't matter how many times you have check the box save "password credentials". The very next time you try to login via RDP again and it will prompt for a password to be typed in.

Solution:

Open local policy edititor. Go to start ->run -> type gpedit.msc
Then Navigate to:
Computer Configuration ->Administrative Templates ->System -> Credentials Delegation
Then on the sixth line on the right side double click on "Allow Delegating Saved Credentials with
NTLM-only Server Authentication"

Click Enable and click on the Show button then in the Value box typeTERMSRV/terminalserver.domain.com
substitue terminalserver with your actual terminal server name.

Add “TERMSRV/” to the server list, then your domain, example: TERMSRV/mydomain.com. You can use one wildcard (*) in a name. For example to enable the setting on all servers in “mydomain.com” type “TERMSRV/*.mydomain.com” or for all servers use: TERMSRV/*


When finished, go to cmd console and type gpupdate to update the new policy or restart the computer.
Next time you try to login to the terminal server it won't ask password again.




这个错误信息 "Read config file error: Unable to find Credentials" 通常出现在使用 AWS CLI、Terraform 或其他需要访问云服务认证信息的工具时,表示程序无法找到有效的身份凭证(如 access key 和 secret key)。 可能的原因包括: 1. **未配置 AWS 凭证文件**:系统期望在默认路径(如 `~/.aws/credentials`)下找到凭证文件,但该文件不存在或格式不正确。 2. **环境变量缺失**:如果没有设置 `AWS_ACCESS_KEY_ID` 和 `AWS_SECRET_ACCESS_KEY` 环境变量,且没有本地凭证文件,就会报错。 3. **配置文件路径错误**:某些工具会读取特定配置文件(如 `config` 或 `credentials`),如果路径指定错误或权限不足,会导致读取失败。 4. **IAM 角色问题(在 EC2 中)**:如果你在 EC2 实例中运行程序,并依赖实例角色获取权限,可能是 IAM 角色未附加或权限不足。 5. **多用户或切换用户导致主目录错乱**:例如用 `sudo` 运行命令时,`~/.aws/` 指向的是 root 用户目录,而非当前用户。 ✅ 解决方法: - 手动创建凭证文件: ```bash mkdir -p ~/.aws cat > ~/.aws/credentials << EOF [default] aws_access_key_id = YOUR_ACCESS_KEY aws_secret_access_key = YOUR_SECRET_KEY EOF ``` - 设置环境变量(临时): ```bash export AWS_ACCESS_KEY_ID=AKIAIOSFODNN7EXAMPLE export AWS_SECRET_ACCESS_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY ``` - 使用 `aws configure` 命令初始化: ```bash aws configure ``` 然后按提示输入 Access Key、Secret Key、Region 和 Output Format。 - 检查文件权限(安全要求): ```bash chmod 600 ~/.aws/credentials chmod 700 ~/.aws ```
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值