You can customize the Windows guest operating systems of the virtual machines when you deploy a new virtual machine from a template or clone an existing virtual machine. Customizing the guest operating system helps prevent conflicts that might result if you or other users deploy virtual machines with identical settings, such as duplicate computer names.
You can prevent Windows from assigning new virtual machines or templates with the same Security IDs (SIDs) as the original virtual machine. Duplicate SIDs do not cause problems when the computers are part of a domain and only domain user accounts are used. However, if the computers are part of a Workgroup or local user accounts are used, duplicate SIDs can compromise file access controls. For more information, see the documentation for your Microsoft Windows operating system.
Prerequisites
- Verify that all requirements for customization are met. See Guest Operating System Customization Requirements.
- Verify that there are customization specifications available for use. For information about creating a guest customization specification, see Create a Customization Specification for Windows.
Procedure
Results
When the new virtual machine starts for the first time, the guest operating system runs finalization scripts to complete the customization process. The virtual machine might restart several times during this process.
If the guest operating system pauses when the new virtual machine starts, it might be waiting for you to correct errors, such as an incorrect product key or an invalid user name. To determine whether the system is waiting for information, open the virtual machine console.
What to do next
After you deploy certain Windows operating systems that are not volume licensed, you might need to reactivate your operating system on the new virtual machine.
If the new virtual machine encounters customization errors while it is starting, the errors are logged to %WINDIR%\temp\vmware-imc. To view the error log file, from the Windows Start menu navigate to .