Versions Compared

Old Version 24

changes.mady.by.user Andy Kurth

Saved on

compared with

New Version 25

changes.mady.by.user Andy Kurth

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reverted from v. 23

...

No Format
============================================================================== 
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 
==============================================================================

...

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

...

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 download. Sysprep is included with Windows Vista and Server 2008 so you do not have to download Sysprep for these version.. 

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.

...

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:

...

  1. Start the vcld service:
    /sbin/service vcld start
    You should see output similar to the following:
    No Format
    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  ]
    Note: the vcld service can also be started by running the service script directly:
    /etc/init.d/vcld start
  2. Check the vcld service by monitoring the vcld.log file:
    tail -f /var/log/vcld.log
    You should see the following being added to the log file every few seconds if the management node is checking in with the database:
    No Format
    2009-06-16 16:57:15|15792|vcld:main(165)|lastcheckin time updated for management node 18: 2009-06-16 16:57:15