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
已提问 2 年前1777 查看次数
3 回答
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
支持工程师
已回答 2 年前
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
专家
已回答 2 年前
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
已回答 3 个月前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则