The following instructions assume the VCL database has been installed and configured and that the managment node information has been added to the database as described on the web code installation page.
Check if a Subversion client is already installed on the management node by running the svn command. If not already installed, you can try to install it using yum with the following command:
yum install subversion
If yum is not available, visit http://subversion.tigris.org and follow the instructions for downloading and installing a Subversion client.
Download VCL backend code from the Apache Subversion repository and save it to /usr/local/vcl.
svn export https://svn.apache.org/repos/asf/incubator/vcl/trunk/managementnode/ /usr/local/vcl/
The VCL Perl code running on a management node requires several additional Perl modules available from CPAN - The Comprehensive Perl Archive Network. A search engine for CPAN modules is available at search.cpan.org.
A script is provided in the VCL repository called install_perl_libs.pl which will attempt to download and install the required perl libraries. Run the script:
perl /usr/local/vcl/bin/install_perl_libs.pl
A large amount of output will be displayed on the console the first time the script is run. It will pause if any of the module installations ask for configuration information. Accept all of the defaults by pressing enter when this happens.
Run the script a 2nd time to check if all of the modules the script is configured to install were successfully installed. Output similar to the following should be displayed for each module:
============================================================================== URL: http://search.cpan.org/CPAN/authors/id/T/TI/TIMB/DBI-1.609.tar.gz Module filename: DBI-1.609.tar.gz Module name: DBI-1.609 Module package: DBI Checking if DBI is installed Module is already installed: DBI ==============================================================================
Additional output will be displayed if a module has not been successfully installed. You will need to troubleshoot if any modules were not installed successfully.
Run the following command to execute the utils.pm file:
perl /usr/local/vcl/lib/VCL/utils.pm
Executing utils.pm does not actually do anything but this will tell you if VCL will be able to run. If any Perl modules are missing you will see "Can't locate" lines:
Can't locate HTTP/Headers.pm in @INC (@INC contains:...)
Once all of the required modules are installed, you should see output similar to the following:
BIN PATH: /usr/local/vcl/lib/VCL pre-execution: config file being used: /etc/vcl/vcld.conf Uncaught exception from user code: VCLD : /etc/vcl/vcld.conf does not exist, exiting -- No such file or directory BEGIN failed--compilation aborted at /usr/local/vcl/lib/VCL/utils.pm line 616. at /usr/local/vcl/lib/VCL/utils.pm line 616
/usr/bin/make install -- OK
Module Compress::Zlib (P/PM/PMQS/IO-Compress-2.020.tar.gz)
/usr/bin/make install -- OK
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.
Download: Windows XP Service Pack 2 Deployment Tools
Download: Windows XP Service Pack 3 Deployment Tools
The Sysprep files need to be extracted from the file you download which is in Microsoft's .cab format. It is easiest to extract the files on a Windows computer. Windows Explorer is able to open the .cab file and then the files contained within can be copied elsewhere. There are also some Linux utilities which claim to be able to extract .cab files.
Copy the extracted files to the following directory on the management node after they have been extracted:
/usr/local/vcl/tools/Windows_XP/Utilities/Sysprep
The Sysprep directory should contain the following files at a minimum:
-rw-rw-r-- 1 root root 25600 Aug 18 17:32 setupcl.exe
-rw-rw-r-- 1 root root 88576 Aug 18 17:32 sysprep.exe
-rw-rw-r-- 1 root root 2574 Aug 18 17:32 sysprep.inf
Your Windows XP product key needs to be entered into the sysprep.inf file. Edit the following file:
/usr/local/vcl/tools/Windows_XP/Utilities/Sysprep/sysprep.inf
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:
/usr/local/vcl/tools/Windows/Utilities/WSName/wsname.exe
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:
/usr/local/vcl/tools/Windows/Utilities/NewSID/newsid.exe
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:
/usr/local/vcl/tools/Windows/Utilities/SPDrvScn/spdrvscn.exe
Starting vcld daemon: BIN PATH: /usr/local/vcl/bin pre-execution: config file being used: /etc/vcl/vcld.conf FQDN is not listed pre-execution: process name is set to: vcld pre-execution: verbose mode is set to: 1 pre-execution: testing mode is set to: 0 pre-execution: log file being used: /var/log/vcld.log pre-execution: PID file being used: /var/run/vcld.pid Created process 23696 renamed to vcld ... [ OK ]
2009-06-16 16:57:15|15792|vcld:main(165)|lastcheckin time updated for management node 18: 2009-06-16 16:57:15