Page History

...

1. Determine the name of the missing module by looking at the "Can't locate" line
2. Search for the missing module on search.cpan.org and install it manually
   _-or-_Try to install the module using the CPAN shell

...

The Windows XP Deployment Tools are available for free from Microsoft and are required in order for the capture of Windows XP VCL images to work.  The Sysprep utility is included in the Deployment Tools. 

Links to the downloads are below.  You should be able to use the SP2 or SP3 version assuming the image you are capturing contains Windows XP Service Pack 3.  We have seen problems with drivers not being installed correctly using the SP3 version of the deployment tools so the SP2 version is recommended.

...

Configure sysprep.inf

Your Windows XP product key needs to be entered into the sysprep.inf file.  Edit the following file:

WSName - Workstation Name Changing Utility

The WSName.exe utility is used to change the name of the computer while it is being installed.  Download the WSName.exe utility:

Download: WSName.exehttp://mystuff.clarke.co.nz/MyStuff/wsname.asp

Save the WSName.exe utility in the following location on the management node:

NewSID - Windows SID Changing Utility

NewSID.exe is used to change the SID of a Windows computer if Sysprep is not used.  Download the NewSID.exe utility:

Download: NewSID.exe

Save the NewSID.exe utility in the following location on the management node:

SPDrvScn - Windows Driver Scanning Utility

SPDrvScn.exe is used before an image is captured to enter the paths of drivers to the Windows registry so that they are loaded when Sysprep attempts to install devices.  Download the SPDrvScn.exe utility:

Download: SPDrvScn.exe

Save the SPDrvScn.exe utility in the following location on the management node:

Configure vcld.conf

1. Create the /etc/vcl directory:
   mkdir /etc/vcl 
2. Copy the generic vcld.conf file to /etc/vcl:
   cp /usr/local/vcl/etc/vcl/vcld.conf /etc/vcl
3. Edit the /etc/vcl/vcld.conf file:
   vi /etc/vcl/vcld.conf
   The following lines must be configured in order to start the VCL daemon (vcld) and allow it to check in to the database:
   • FQDN - the fully qualified name of the management node, this should match the name that was configured for the management node in the database
   • server - the IP address or FQDN of the database server
   • LockerWrtUser - database user account with write privileges
   • wrtPass - database user password
4. Save the vcld.conf file:
   <escape>
   :wq
   <enter>

...