Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

You will need to troubleshoot if any modules were not installed successfully.

List of (known) Required Modules 

The following is a list of modules known to be required.  They should be installed in the order in which they appear because some are prerequisites for subsequent modules. The install_perl_libs.pl script will attempt to install these modules. Additional modules may be required depending on the Perl distribution. See the instructions below if an additional module needs to be installed.

What to do if a Module is Missing

  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

Once all of the required modules are installed, you should see something like this:

No Format

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

How to Install a Perl Module Manually

...

No Format
Can't locate HTTP/Headers.pm in @INC (@INC contains:...)

What to do if a Module is Missing

  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

Once all of the required modules are installed, you should see something like this:

...

Download Required Utilities

Windows XP Deployment Tools (Sysprep)

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:

Panel

/usr/local/vcl/tools/Windows_XP/Utilities/Sysprep

The Sysprep directory should already exist on the management node because it exists the Subversion repository.  There should also be a sysprep.inf file in the Sysprep directory.  This is the base Sysprep template file for VCL included in the Subversion repository.

The Sysprep directory should contain the following files at a minimum:

Panel

-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

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

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>

...