awsdocs / amazon-ec2-user-guide-windows

The open source version of the Amazon EC2 User Guide for Windows. To submit feedback or requests for changes, submit an issue or make changes and submit a pull request.

NOTICE

This repository is archived, read-only, and no longer updated. For more information, read the announcement on the AWS News Blog.

You can find up-to-date AWS technical documentation on the AWS Documentation website, where you can also submit feedback and suggestions for improvement.

amazon-ec2-user-guide-windows's Issues

Windows-InPlaceUpgrade-SecurityGroup

Can the Automation document be updated to require/optional for Security Group of the launched instance.
The issue I am facing is related to Directory Service. I do not want the restored instance to conflict hostname with original instance, hence I am trying to do upgrade while launching restored instance in a different VPC, but Automation document is pre-configured to fetch Original Instance Security Group ending up with the error below:

Automation Step Execution fails when it is launching the instance(s). Get Exception from RunInstances API of ec2 Service. Exception Message from RunInstances API: [Security group sg-0548fbbd181952f53 and subnet subnet-a6a0cbc0 belong to different networks. (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameter; Request ID: 1b7afa7f-2d3e-4b0b-9d60-70efad3292c0; Proxy: null)]. Please refer to Automation Service Troubleshooting Guide for more diagnosis details.

If I can set up Security Group, I can also avoid Domain Join even if restore happens in the same VPC, by blocking DNS Access outbound.

can't get past "get password"

I'm using Mac, and this is the first time I have seen this issue, I have launched other instances before successfully.

For over 8 hours I keep getting the message

"Password not available yet.
Please wait at least 4 minutes after launching an instance before trying to retrieve the auto-generated password.

Note: Passwords are generated during the launch of Amazon Windows AMIs or custom AMIs that have been configured to enable this feature. Instances launched from a custom AMI without this feature enabled use the username and password of the AMI's parent instance.

Try again."

my instance is running though. I'm I missing something?

There is no RSS feed for this guide

Hi All ,

There is no RSS feed for this guide .
Can you please look into adding the following functionality to this guide so we can follow updates added to the guide ?

see :
https://help.github.com/en/articles/atom-rss-feeds-for-github-pages

No mention of runAsLocalSystem element in the userdata document

In the https://github.com/awsdocs/amazon-ec2-user-guide-windows/blob/master/doc_source/ec2-windows-user-data.md document, there is no mention of the runAsLocalSystem element which I have discovered I need to use on VMs that join a domain

See thread here: https://forums.aws.amazon.com/message.jspa?messageID=899912

Inline codes should have back-ticks around it.

Ec2HandleUserData definition is misleading and does not match GUI

In Guide:
Creates and executes scripts created by the user on the first launch of an instance after Sysprep is run. Commands wrapped in script tags are saved to a batch file, and commands wrapped in PowerShell tags are saved to a .ps1 file.

In GUI:
Enable UserData execution for next service start (automatically enabled at Sysprep)

Is the EC2 Settings Config ("C:\Program Files\Amazon\Ec2ConfigService\Settings\Config.xml") option the same as what I'm seeing in the GUI for EC2 Service Properties > General > User Data?

Link for troubleshooting is not available: Windows Server Hacks: Remotely Enable Remote Desktop

http://archive.oreilly.com/pub/a/windows/archive/server-hacks-remote-desktop.html

bug in provided RestoreVssSnapshotSampleScript.zip

line 73 Add-EC2Volume -InstanceId $InstanceId -VolumeId $Volume.VolumeId -Device $DeviceTag.Value > $null
will try to mount all snapshots to one point, it should be
Add-EC2Volume -InstanceId $InstanceId -VolumeId $Volume.VolumeId -Device $Data.Device > $null

line 53 if ($SnapshotData.Device.Contains($BlockDevice.DeviceName) -or $BlockDevice.DeviceName -ne "/dev/sda1") {
will unmount all volumes except root, even when only one among multiple snapshots are being restored
-or $BlockDevice.DeviceName -ne "/dev/sda1" should be removed

Screenshot refresh

The screenshot refresh frequency is not mentioned in https://github.com/awsdocs/amazon-ec2-user-guide-windows/blob/master/doc_source/screenshot-service.md, also the ability or the lack thereof, to force a refresh of the screenshot by using AWS API or CLI is not mentioned.

Windows GPU Registry Changes

I'm guessing starting on the version of drivers starting 5XX the location of where the registry entry has changed from the documented path of:

HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global

to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm\Global

This path can be pulled from the Nvidia docs here: https://docs.nvidia.com/grid/15.0/grid-vgpu-user-guide/index.html#licensing-grid-vgpu

I was going to make a PR, however I'm not sure how the docs should be handled since this path is only for newer version of the driver. I confirmed that after making this change I was able to license the grid vGPU correctly.