Questions tagged with Windows Provisioning
Content language: English
Sort by most recent
IHAC who is using windows faster launch feature is seeing issues with the launch once out of 5 launches. When the AMI launch fails, SSM service is not activated and User data scripts are not executed. They are not able to find out the reason for AMI launch failure.
Customer is also having challenges as with SSM service not coming up they can’t log into the EC2 instance (RDP is locked down due to the InfoSec security requirements) to download log files. Is there any other option to offload the logs
I am struggling to figure out how administrate a SIMPLE AD from within a Workspace.
I have created a workspace with a new domain, and run up a Windows instance. When I added the AD DS and AD LDS Tool & DNS Server Tools, I was unable to edit any of the Users. Reading the help guides, it mentioned that you need to manage it via an EC2 instance.
So, I Run up an EC2 instance on the same domain, but now when I look at changing it tells me I need to be a domain admin, as I'm logged in as a local user. None of my user log ins work with EC2, and i'm completely locked out from being able to manage the AD.
How do I gain access to Admin the SIMPLE AD on a Workspace domain?
Hello,
Have a domain joined t3.2xlarge instance that I would like to upgrade to m6i.2xlarge according to the compute optimizer recommendation.
But after modifying the instance type, I receive the NLA error:

Cannot even RDP using the local Administrator account, the same NLA error displays.
This instance exists in ap-southeast-2 and done a few tests.
1. Changing back to t3.2xlarge, connected using domain credentials OK
2. Changing to m5.2xlarge, connected using domain crendentials OK
3. Added another NIC when it was on m6i.2xlarge, NLA error on the second interface.
4. (Don't think this matters, the instance is HVM) Upgraded to the latest PV driver, changing instance type to m6i.2xlarge, NLA error.
5. Launched a m6i.2xlarge instance in a different subnet(AZ), joined domain OK, connected using domain crendentials OK; changed to t3.2xlarge, NLA error; changed back to m6i.2xlarge, connected using domain crendentials OK
6. Launched another m6i.2xlarge instance in the same subnet as the t3.2xlarge, swapped the root volume, NLA error. Swapped back the volumes, connected OK.
Has anyone encountered this fault? How can I perform the necessary upgrade?
Kind regards,
Ken
Greetings,
I am running a MacBook trying to connect to an AWS Instance that is running, using Microsoft Remote Desktop.
I downloaded the Remote Desktop file, and added it to Microsoft Remote Desktop.
I have installed and launched Microsoft Remote Desktop.
I entered the Public DNS that is in the **Connect to instance**, get an error message.
Any suggestions to resolve this issue is much appreciated.
Thanks
Clive
ERROR
**We couldn't connect to the remote PC. Make sure the PC is turned on and connected to the network, and that remote access is enabled.
Error code: 0x204**
Windows firewall got enabled after that i am not able to connect instance using RDP, is there any way to disable windows firewall from console.
Regards,
Ali
Hello,
I tried to find a way to report an issue concerning the following Amazon AMI (Windows_Server-2022-English-Full-Base-2022.10.27 - ami-017cdd6dc706848b2).
I cannot install the OpenSSH server feature either programmatically or manually.
I have to go back to the 2022.10.12 AMI or run Windows Update to get the latest cumulative KB.
Let me know where I can report it.
Thanks.
AWS automatically assigned a reboot event to a Windows EC2 instance used in production, and scheduled it for a nice monday afternoon.
I tried all the official guides to at least postpone it to midnight, but the command in the "Actions" menu is disabled.
How can I proceed? :/
We setup a S3 File Gateway hosted as an EC2 instance following the instruction for creating a Storage Gateway and SMB File Share in this guide [Create and activate an Amazon S3 File Gateway](https://docs.aws.amazon.com/filegateway/latest/files3/create-gateway-file.html).
For now without any AD integration, just a configured password for the guest access.
However, on trying to mount the file share we keep getting the error "System error 53 has occurred - the network path was not found".
We already checked and tried all suggestions from [How can I troubleshoot when I'm unable to mount my Storage Gateway SMB file share?](https://aws.amazon.com/de/premiumsupport/knowledge-center/storage-gateway-troubleshoot-smb-mount/) and [Troubleshooting and best practices](https://docs.aws.amazon.com/filegateway/latest/files3/troubleshooting-gateway-issues.html)
The ports 445 and 139 are allowed in the Security Group and the state of the file share is `Available`.
For mounting we us a computer running Windows 10 Pro.
At this point we are not sure what else to try and welcome any suggestions.
Thanks
p.s. a test NFS file share with the same storage gateway is working
Sorry if this is basic but I'm new and in a bind.
Previously I was able to set up a GUI on my lightsail instance by following [this guide](https://aws.amazon.com/premiumsupport/knowledge-center/ec2-linux-2-install-gui/). It worked good but my project requires more RAM than I had available so I used a snapshot to start a new instance with better specs and shut the original down.
Now I am unable to get the GUI working. All is well up until:
> 3. Open the TigerVNC Viewer on your local computer. When asked for the VNC server hostname, enter localhost:1 and then connect to it.
TigerVNC throws the error "The connection was dropped by the server before the session could be established." I'm able to ssh into the instance, everything is installed and set up correctly (as far as I can tell), but for some reason I cannot tunnel in with TigerVNC. It worked on the previous instance.
I am trying to decipher the following statement (first bullet from [here](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volumes-multi.html#considerations)):
> You can attach a volume that is Multi-Attach enabled to Windows instances, but the operating system does not recognize the data on the volume that is shared between the instances, which can result in data inconsistency.
If OS doesn't recognize the data, then data inconsistency is least of my concerns, no? To summarize can I use multi-attach with Windows? Or the only option is FSx, that requires full-blown AD and therefore drives the price up?
In Coudformation templates, there is a section to specfiy commands like below. Under `fullServer` I am running the command `install`. However, when I look at the logs after cfn has run on the server, it shows
```
2022-10-20 13:41:25,780 [INFO] Command install succeeded
2022-10-20 13:41:25,796 [DEBUG] Command install output: $MAGIC
```
This is because the `$Magic` is how to declare and use variables in powershell where as cmd needs the `set` keyword. I would expect the output of this command to be `Command install output: I am from the full server env`.
```
"AWS::CloudFormation::Init": {
"configSets": {
"downloadS3Data": ["downloadS3"],
"Full": [{"ConfigSet": "downloadS3Data"}, "fullServer"],
"default": [ {"ConfigSet": "Full"}],
"App": [{"ConfigSet": "downloadS3Data"}, "appServer"],
"Interface": [{"ConfigSet": "downloadS3Data"}, "interfaceServer"],
"Notification": [{"ConfigSet": "downloadS3Data"}, "notificationServer"]
},
"downloadS3": {
"files": {
"C:\\ccw_downloads\\test.txt": {
"source": "https://ccw-to-rds-poc-1.s3.us-east-2.amazonaws.com/test.txt",
"authentication": "S3AccessCreds"
}
}
},
"fullServer": {
"commands": {
"install": {
"command": "echo $MAGIC",
"env": {"MAGIC": "I am from the full server env"},
"cwd": "C:\\ccw_downloads",
"waitAfterCompletion": 120
}
}
}
}
```
I would like to run the command with PowerShell and not cmd. Is there a way to specify that like I can with User Data?
I know that I could append `PowerShell -Command` to the beginning, making cmd call PowerShell and pass args. However, that would not allow me to use the enviornment variable `MAGIC`. For example `"command": "Powershell -Command 'echo $magic'"`
Dear Sir/Madam,
We would like to install our Windows App for multiple-user access under Citrix on AWS. What Citrix software should we use and how to install it on AWS?
Please advise.
Kind regards,
Eddie