Skip to main content

Vmware view Sysprep customization steps

sysprep can be import by a file sysprep.inf for xp, 2003 and sysprep.xml for win 7,8, 2008 ,2012
Here you will find steps to create sysprep custom 

Sysprep customizing need to create before deploying new OS
Below image you will see sysprep list here we gonna create for xp machine

We are using xp sp3 as a parent vm. Xp machine need a patch, For 32 bit
 and for 64 bit

Once patch is install'd roboot xp and install view agent and install all required software in parent vm. Power off parent vm take snapshot if you want to created "view composer linked clone" OR do clone to template if you want to do "Full Virtual Machine"

For windows 7,8 Windows 2008 R2, no need to follow steps 1 to 4
1      1Download file
[note: link is to download xp sysprep tool ]

2. Open to vcenter vm
3. Go to path C:\ProgramData\VMware\VMware VirtualCenter\sysprep
The subfolders within the C:\ProgramData\VMware\Infrastructure\VirtualCenter\sysprep folder are:


4. Go to xp folder
Copy file and extract it
You will find deploy folder has these files:


5. From the vSphere Client Home inventory page, select Rules and Profiles > Customization Specification Manager.
Right click to Create a new specification icon to open the New VM Guest Customization Spec wizard
you will see options New, Import, Refresh
In "New" option you can create sysprep manually
In "Import" option you can import sysprep customized  .xml file
In "Refresh" you will refresh page

Click on New

a. Properties
Target virtual Machine OS
I have selected windows

if you tick on "Use Custom Sysprep Answer file"
you will have 4 steps only
b. Custom sysprep file[you need to import sysprep answer file i.e sysprep.inf or sysprep.xml Or you can create manually]
c. Network
d. Operating System Options
e. Ready to complete

Customization specification information
Give your parent vm os name or any other name

we did't tick since we are not using Custom Sysprep Answer file
so we will have 10 steps now
Select Windows from the Target VM Operating System drop-down menu, and enter a name and optional description for the specification
Click next

b. Registration information
 Type the virtual machine owner’s name and organization
Name : Desktop name
organization : Organization name

                                                              click next

C. Computer Name
Enter the guest operating system's computer name.
The operating system uses this name to identify itself on the network. On Linux systems, it is called the host name.
Enter a name
Type a name.
The name can contain alphanumeric characters and the hyphen (-) character. It cannot contain periods (.) or blank spaces and cannot be made up of digits only. Names are not case-sensitive.
(Optional) To ensure that the name is unique, select Append a numeric value to ensure uniqueness. This action appends a hyphen followed by a numeric value to the virtual machine name. The name is truncated if it exceeds 63 characters when combined with the numeric value.
Use the virtual machine name
The computer name that vCenter Server creates is identical to the name of the virtual machine on which the guest operating system is running. If the name exceeds 63 characters, it is truncated.
Enter a name in the Clone/Deploy wizard
The vSphere Client prompts you to enter a name after the cloning or deployment is complete.
Generate a name using the custom application configured with vCenter Server
Enter a parameter that can be passed to the custom application.

we have selected "use the Virtual Machine name"
                                                                  Click Next

d. computer license  
Provide licensing information for the Windows operating system and click Next.

For nonserver operating systems
Type the Windows product key for the new guest operating system.
For server operating systems
Type the Windows product key for the new guest operating system.
Select Include Server License Information.
Select either Per seat or Per server.
If you selectPer server, enter the maximum number of simultaneous connections for the server to accept.

e. Administrator Password
Configure the administrator password for the virtual machine and click Next.
Type a password for the administrator account and confirm the password by typing it again.
You can change the administrator password only if the administrator password on the source Windows virtual machine is blank.
If the source Windows virtual machine or template already has a password, the administrator password does not change.
(Optional) To log users into the guest operating system as Administrator, select the check box,
and select the number of times to log in automatically.

f. Time zone

Select the time zone for the virtual machine and click Next.
g. Run once
(Optional) On the Run Once page, specify commands to run the first time a user logs into the guest operating system and click Next.
See the Microsoft Sysprep documentation for information about RunOnce commands.

h. Network
Select the type of network settings to apply to the guest operating system.

Typical settings
Select Use typical network settings and click Next.
vCenter Server configures all network interfaces from a DHCP server using default settings.
Custom settings
Select Manually select custom settings.
For each network interface in the virtual machine, click the pencil icon.
Enter IP address and other network settings and click OK.
When all network interfaces are configured, click Next.

i.              Workgroup Or Domain
Select how the virtual machine will participate in the network and click Next.
Type a workgroup name. For example, MSHOME.
Windows Server Domain
Type the domain name.
Type the user name and password for a user account that has permission to add a computer to the specified domain.

j. Operating system Option
(Optional) Select Generate New Security ID (SID) and click Next.
A Windows Security ID (SID) is used in some Windows operating systems to uniquely identify systems and users. If you do not select this option, the new virtual machine has the same SID as the virtual machine or template from which it was cloned or deployed.
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.

h. Ready to Complete

Click Finish to save your changes.
 Once you created in client you can add new pool with new customized in view manager.
below you can find win xp is added in sysprep customization