A problem must have occurred during the image capture. Sysprep.exe should have run as the last step before the computer was shut down and the image files saved. When the image is booted, you should see a Windows setup screen. This is the result of running sysprep.exe before the image was capture.

To diagnose, look at C:\Windows\setupapi.log. If this file doesn't exist or doesn't contain any info on the date the image was captured then sysprep.exe didn't run.

Check if the following exist in the image (they should):

I would make sure sysprep.exe exists on your management node as described in the documentation and try to capture the image again. If sysprep still isn't running, please send the log output from the image capture.


Hartl, Gerhard L. wrote:
I never notice the sysprep run, the workstation also is not renaming itself.  
This is copied down during the base image capture correct?  Is there anything I 
can look at to diagnose?

- Gerhard

-----Original Message-----
From: Andy Kurth [mailto:andy_ku...@ncsu.edu] Sent: Saturday, May 29, 2010 11:43 AM
To: vcl-user@incubator.apache.org
Subject: Re: Sysprep Winxp

The steps on the following page should be all that is necessary:

Are you having trouble with Sysprep?

Just FYI - the code in the next release will make the Sysprep and management node configuration a little simpler. The requirement for the spdrvscn.exe utility has been removed and you will no longer need to configure the sysprep.inf file. The code scans all of the drivers which have been saved to the Drivers directories on the management node, dynamically generates the sysprep.inf file, and sets the DevicePath registry key (this is what spdrvscn.exe does).


Hartl, Gerhard L. wrote:
Aside from the sysprep files that are copied to the mgmt server and editing the sysprep.inf, what else is required for sysprep to function? Gerhard Hartl | PC/LAN Support Group
*O*ffice of *C*omputing and *C*ommunications *S*ervices
*O*ld* **D*ominion* **U*niversity | *ODU*
4700 Elkhorn Blvd | Norfolk, VA 23529
757.683.6980 | _gha...@odu.edu_ <mailto:gha...@odu.edu> | occs.odu.edu
/"The information in this email and any attachments may be confidential and privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient (or the employee or agent responsible for delivering this information to the intended recipient) please notify the sender by reply email and immediately delete this email and any copies from your computer and/or storage system. The sender does not authorize the use, distribution, disclosure or reproduction of this email (or any part of its contents) by anyone other than the intended recipient(s)./ /No representation is made that this email and any attachments are free of viruses. Virus scanning is recommended and is the responsibility of the recipient."/

No virus found in this incoming message.
Checked by AVG - www.avg.com Version: 9.0.819 / Virus Database: 271.1.1/2903 - Release Date: 05/29/10 02:25:00

Andy Kurth
Virtual Computing Lab
Office of Information Technology
North Carolina State University

Reply via email to