When running sysprep using "VM Customization Specifications", sysprep.xml remains in the guest OS

Products

• VMware vCenter Server 8.0

Issue/Introduction

• When generalizing a Windows virtual machine using VM Customization Specifications, C:\sysprep####\sysprep.xml is left behind.
• If sysprep has been configured to assign a license key, the license key will be written in plain text in sysprep.xml.
  
  * sysprep####, where #### is a random four-digit number

Resolution

This is a known issue in vCenter 8.0 and vCenter 9.0 and not affected in vCenter 7.0.

Workaround

• Reboot the Guest OS after customization is complete.
• After rebooting, the C:\sysprep#### will be deleted.

Additional Information

This issue is resolved in vCenter 8.0 Update 3g.
This issue will be resolved in an upcoming release of vCenter 9.0.