Troubleshoot Desktop Image Sysprep Errors
During the Power off & set as image operation, Nerdio Manager performs the following steps:
Power off the desktop image VM
Clone the OS disk and create a new temporary VM
Power on the new temp VM
Remove local user accounts to prevent Sysprep failing due to any per-user modern apps
Run Sysprep /generalize command
Wait for the Operating System to shut down
Capture the VM as image
Delete the old image and replace it with the new one
Delete the temporary VM
Check if the Power off & set as image process ends in an Error state at Step #6 with the following error:
Wait for Sysprep to complete (temp VM should automatically shut down).
If that is the case, then the Sysprep process failed and the OS did not shut itself down automatically, as it would have had the Sysprep /generalize process completed successfully.
To determine the cause of the Sysprep failure:
In the Azure portal, navigate to Virtual machines.
Locate the cloned desktop image VM.
Note: This VM name typically has a "-tmp" extension because it is a clone of the original desktop image VM.
In the blade on the left side, in the Support + troubleshooting section, select Reset password.
Create a local admin account.
RDP to the VM using the new local admin account (username = VMName\LocalAdminName).
Review the Sysprep log found in C:\windows\system32\sysprep\panther\setupact.log.
Tip: Start from the bottom of the Sysprep log, look for the last (chronologically) ERROR, and work your way up. This should help you determine what prevented the Sysprep from completing normally.
Resolve the problem.
In Nerdio Manager, select Cleanup next to the failed task.
Run the Power off & set as image process once again.
Note: Please see Troubleshoot Sysprep & Windows Defender ATP for additional troubleshooting assistance, if necessary.