The instance is unresponsive: Windows is still being configured. SysprepState=IMAGE_STATE_UNDEPLOYABLE

0

I'm trying to clone my Windows 2016 Server instance i-01. What I did:

  1. Installed latest drivers according to this article
  2. Rebooted successfully
  3. Run SysPrep

Now I can start my i-01 instance but it became inaccessible. I can't connect it via RDP. If I connect via AWS Serial Console, it shows me Windows is still being configured. SysprepState=IMAGE_STATE_UNDEPLOYABLE for many hours already.

What are the ways for further investigations?

Alex
gefragt vor 2 Jahren1775 Aufrufe
3 Antworten
1

You can detach the root volume from the instance and attach it to a new temporary instance as a secondary volume. That will allow you to take a look at the sysprep logs and figure out what went wrong. You can install EC2Rescue https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2rw-gui.html#ec2rescue-offline and collect the logs, then send it to AWS Premium Support for further analysis.

AWS
SUPPORT-TECHNIKER
beantwortet vor 2 Jahren
0

That error appears to come from Sysprep so my guess is that something has gone wrong with the Windows bootstrap/installation process. A quick search shows that there are several reasons why a server can end up in that state so I would troubleshoot with that error message as your starting point.

profile pictureAWS
EXPERTE
beantwortet vor 2 Jahren
0

Windows licensing/activation and trend micro installation failures which might stopped AMS boot script and send failure signal in cfn. Upon manually resolving the errors on the failed instance, create a new sysprepped AMI & instance which might resolve the issue.

AWS
Rao
beantwortet vor 3 Monaten

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen