forked from docs/doc-exports
Reviewed-by: Pristromskaia, Margarita <margarita.pristromskaia@t-systems.com> Co-authored-by: Zaoxu, Li <lizaoxu@huawei.com> Co-committed-by: Zaoxu, Li <lizaoxu@huawei.com>
6.2 KiB
6.2 KiB
How Do I Handle the Startup Failure of a Windows ECS Created from a Windows Image Generalized by Sysprep?
Symptom
- When you start the ECS, information similar to the following is displayed.
Then, the following information is displayed in the dialog box:
Windows could not parse or process the unattend answer file for pass [specialize]. A component or setting specified in the answer file does not exist. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup].
- Click OK. The following information is displayed in the dialog box:
The computer accidentally restarts or encounters an error. Windows installation cannot continue. Click OK to restart the computer and restart the installation.
- Open setupact.log in C:\Windows\Panther. The log contains the following information.
Solution
- Create an ECS from a public image. (You are advised to use a public image to create another ECS because Sysprep can be executed only for certain times.)
- Create an Unattend.xml file or modify the Unattend.xml file provided by the system.
- If you create an Unattend.xml file, ensure that the created file is used when you run Sysprep. For details about the file, visit:
- If you modify the Unattend.xml file (in the C:\Program Files\Cloudbase Solutions\Cloudbase-Init\conf directory), delete the RunSynchronous part from the file.
- Run Sysprep. For details, see Running Sysprep.
- Create an image from the ECS where Sysprep has been executed.
Parent topic: Image Creation



