Issue Resolved.  Be sure when going through the image capture process for a 
Windows 7 image that "Use sysprep" under "Advanced Options" is set to "No."

On Mar 24, 2011, at 1:16 AM, James Patrick Sigmon wrote:

> Hey Gerhard,
> 
> Thanks for the info.  My OS is the Ultimate Edition and is 64 bit.  So I made 
> the following changes to the file:
> 
>       <component name="Microsoft-Windows-Shell-Setup" 
> processorArchitecture="x64" publicKeyToken="31bf3856ad364e35" 
> language="neutral" versionScope="nonSxS" 
> xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>             <Display>
>                 <ColorDepth>32</ColorDepth>
>                 <DPI>120</DPI>
>                 <HorizontalResolution>800</HorizontalResolution>
>                 <RefreshRate>72</RefreshRate>
>                 <VerticalResolution>600</VerticalResolution>
>             </Display>
>             <ComputerName>*</ComputerName>
>             <TimeZone>Eastern Standard Time</TimeZone>
>             <ProductKey>MyProductKeyforUltimate</ProductKey>
>         </component>
> 
> However, I'm still having the same issue, but the message has slightly 
> changed:
> 
> Windows could not parse or process unattend answer file 
> [C:\Windows\Panther\unattend.xml] for pass [specialize].  The answer file is 
> invalid.
> 
> Can you think of what else I might need to change?
> 
> Thanks again,
> 
> Patrick
> 
> 
> 
> On Mar 23, 2011, at 2:59 PM, Hartl, Gerhard L. wrote:
> 
>> VCL 2.2 does use a unattend.xml for sysprep.  It is located at 
>> /usr/local/tools/Windows_7/Utilities/Sysprep/Unattend.xml.  
>> 
>> Are you imaging Win7 x64 or x86?  What version?  Enterprise, Pro, Ultimate, 
>> etc?  The key provided is for the Enterprise edition and would fail if you 
>> are trying to create a Win 7 Pro image.   Also the processorArchitecture 
>> must equal the architecture you are trying to image. 
>> 
>> 
>> 
>> This is the section that is apparently your issue:
>> 
>> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" 
>> publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" 
>> xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"; 
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>> - <Display>
>>  <ColorDepth>32</ColorDepth> 
>>  <DPI>120</DPI> 
>>  <HorizontalResolution>800</HorizontalResolution> 
>>  <RefreshRate>72</RefreshRate> 
>>  <VerticalResolution>600</VerticalResolution> 
>>  </Display>
>>  <ComputerName>*</ComputerName> 
>>  <TimeZone>Eastern Standard Time</TimeZone> 
>>  <ProductKey>33PXH-7Y6KF-2VJC9-XBBR8-HVTHH</ProductKey> 
>>  </component>
>> 
>> 
>> 
>> - Gerhard
>> Old Dominion University
>> 
>> -----Original Message-----
>> From: Alexander Patterson [mailto:alexander.patter...@csueastbay.edu] 
>> Sent: Wednesday, March 23, 2011 2:20 PM
>> To: vcl-user@incubator.apache.org
>> Subject: Re: windows 7 sysprep???
>> 
>> Hello Patrick,
>> 
>> Windows 7 doesn't use sysprep. This is only used in Windows XP.
>> 
>> Check in your php table under Imagemeta for your Windows 7 image id # that 
>> your using that sysprep is set to 0 then give that a try.
>> 
>> For example
>> 
>> Your Image Id =6     
>> CheckUser =1
>> Subimage = 1         
>> Sysprep = 0  
>> 
>> -Alex
>> 
>> 
>> 
>> On Wed, Mar 23, 2011 at 11:14 AM, James Patrick Sigmon <jpsig...@ncsu.edu> 
>> wrote:
>>> Hey Guys,
>>> 
>>> I've run into a problem with captured windows 7 images.  They seem to 
>>> capture fine, but when you make a reservation for them they time out at the 
>>> "ssh step."  Looking at the console, I can see why.  There is a pop-up box 
>>> that reads:
>>> 
>>> "Windows could not parse or process the unattended answer file for pass 
>>> [specialize].  The settings specified in the answer file cannot be applied. 
>>>  The error was detected while processing settings for component 
>>> [Microsoft-Windows-Shell-Setup].
>>> 
>>> I've been frantically searching for a generic answer to this, and it sounds 
>>> like to could be a sysprep issue, however, the image is a virtual machine.
>>> 
>>> I'm still searching for solutions on my own, but I thought it would be best 
>>> to go ahead and post this issue as our pilot went live and I'm trying to 
>>> figure this out ASAP.
>>> 
>>> Any help is much appreciated,
>>> 
>>> -Patrick Sigmon
>> 
>> 
>> 
>> --
>> Thanks,
>> Alex  Patterson
>> User Support Services
>> Operating System Analyst
>> California State University, East Bay
> 

Reply via email to