- 最新
- 最多得票
- 最多評論
Hi,
I see that you’ve mentioned your issue above. Could you please try to redo your configurations as follow:
Security Group setting : Inbound Rules: RDP source anywhere. Outbound Rules: All traffic destination anywhere.
"If you choose Anywhere, you enable all IPv4 and IPv6 addresses to access your instance using the specified protocol. If you are adding rules for ports 22 (SSH) or 3389 (RDP), you should authorise only a specific IP address or range of addresses to access your instance."
Please see the following document for Security group rules for different use cases: https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/security-group-rules-reference.html
You can also create a new local administrator account by using the following commands:
- net user <NEW_USER_NAME> <PASSWORD> /add
- net localgroup administrators <NEW_USER_NAME> /add
Should you have any issues with running the SSM commands deattach this role ‘’AmazonSSMManagedInstanceCore’’ and continue to run the commands again. https://docs.aws.amazon.com/systems-manager/latest/userguide/setup-launch-managed-instance.html#setup-launch-managed-instance-existing
After creating the new user using SSM Run commands. Connect to your instance using the credentials of the new user. Thereafter, you can reconfigure the local administrator password from the OS.
Additionally, if your instance is domain joined please use the domain controller to change the passwords of your users.
I hope this helps.
Thank you.
相關內容
- AWS 官方已更新 6 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前