Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Sysprep runs unexpectedly at each deployment of a cloned template (1007349)

Symptoms

  • When a template is deployed Sysprep is run every time the virtual machine is started
  • The template has been cloned from another copy of a Lab Manager configuration using VirtualCenter to create the clone

Resolution

If a new template is created by using VirtualCenter to clone an existing Lab Manager configuration and imported back to Lab Manager as a template, Sysprep may run every time the template is deployed.
 
This issue occurs because during deployment, lm-tools determines if it needs to run sysprep by checking for the presence of a machine.id in the virtual machine's .vmx file. If this entry is present, lm-tools, and therefore sysprep, runs. In this circumstance the cloned copy already has an entry and is stored in the template so each deployment triggers Sysprep.

To prevent sysprep from running unexpectedly:

  1. Undeploy the template in Lab Manager.
  2. Connect to the service console of the ESX host as root.
  3. Open the .vmx file for the template in a text editor.
  4. Remove the line that contains the machine.id value.

    For example:

    machine.id = "macaddr=00:50:15:3a:00:1c&bootproto=dhcp&computerName=hostname&UseSysPrep=Yes&MARKERID=524341316"
  5. Save the changes.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 0 Ratings
Actions
KB: