Troubleshoot Desktop Image Sysprep Errors

Troubleshoot Desktop Image Sysprep Errors

During the Power off & set as image operation, Nerdio Manager performs the following steps:

  1. Power off the desktop image VM

  2. Clone the OS disk and create a new temporary VM

  3. Power on the new temp VM

  4. Remove local user accounts to prevent Sysprep failing due to any per-user modern apps

  5. Run Sysprep /generalize command

  6. Wait for the Operating System to shut down

  7. Capture the VM as image

  8. Delete the old image and replace it with the new one

  9. 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:

  1. In the Azure portal, navigate to Virtual machines.

  2. 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.

  3. In the blade on the left side, in the Support + troubleshooting section, select Reset password.

  4. Create a local admin account.

  5. RDP to the VM using the new local admin account (username = VMName\LocalAdminName).

  6. 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.

  7. Resolve the problem.

  8. In Nerdio Manager, select Cleanup next to the failed task.

  9. Run the Power off & set as image process once again.

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request

Comments (0 comments)

Article is closed for comments.