Before vCloud Director can perform guest customization on virtual machines with certain older Windows guest operating systems, you must install the appropriate Microsoft Sysprep files on each member of the server group.
Sysprep files are required only for some older Microsoft operating systems. If your cloud does not need to support guest customization for those operating systems, you do not need to install Sysprep files.
To install the Sysprep binary files, you copy them to a specific location on the server. You must copy the files to each member of the server group.
Verify that you have access to the 32- and 64-bit Sysprep binary files for Windows 2003 and Windows XP.
- Log in to the target server as root.
- Change directory to $VCLOUD_HOME/guestcustomization/default/windows.
[root@cell1 /]# cd /opt/vmware/vcloud-director/guestcustomization/default/windows
- Create a directory named sysprep.
[root@cell1 /opt/vmware/vcloud-director/guestcustomization/default/windows]# mkdir sysprep
- For each guest operating system that requires Sysprep binary files, create a subdirectory of $VCLOUD_HOME/guestcustomization/default/windows/sysprep.
Subdirectory names are specific to a guest operating system.
Table 1. Subdirectory Assignments for Sysprep Files Guest OS Subdirectory to Create Under $VCLOUD_HOME/guestcustomization/default/windows/sysprep Windows 2003 (32-bit) svr2003 Windows 2003 (64-bit) svr2003-64 Windows XP (32-bit) xp Windows XP (64-bit) xp-64
[root@cell1 /opt/vmware/vcloud-director/guestcustomization/default/windows]# mkdir sysprep/xp
- Copy the Sysprep binary files to the appropriate location on each vCloud Director server in the server group.
- Ensure that the Sysprep files are readable by the user
vcloud.vcloud.Use the Linux chown command to do this.
[root@cell1 /]# chown -R vcloud:vcloud $VCLOUD_HOME/guestcustomization