Client Management Suite

 View Only
  • 1.  Unattend Files and 8.0

    Posted Jul 01, 2016 10:46 AM

    Hello everyone.

    I'm having a hard time understanding what in the world is going on with 8.0 and unattend files, how it all works.  Currently I point to a custom "sysprep" configuration (unattend answer file) when deploying a image, but with Windows 10 it's not working.  Windows 7, only some things worked.  This is being applied to a 64bit image.

    So my questions are:

    1. During an image capture, why the task of "Prepare for Image Capture" require the product key? (where's it saving it to? starting an unnatend to be stored on the image?)

    2.  When imaging, if I select a custom unattend file, where exactly is it suppose to be copied to? Windows\Panther or Windows\System32\Sysprep?

    3.  After imaging, Windows 10 boots and says "windows could not apply unattend settings during pass [specialize]".  My specialize area only has:

     <settings pass="specialize">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <RegisteredOrganization>removed</RegisteredOrganization>
                <RegisteredOwner>removed</RegisteredOwner>
                <ProductKey>removed</ProductKey>
            </component>
            <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <InputLocale>en-US</InputLocale>
                <SystemLocale>en-US</SystemLocale>
                <UILanguage>en-US</UILanguage>
                <UILanguageFallback>en-US</UILanguageFallback>
                <UserLocale>en-US</UserLocale>
            </component>
    
            <component name="Microsoft-Windows-TerminalServices-LocalSessionManager" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <fDenyTSConnections>false</fDenyTSConnections>
            </component>
        </settings>

    I tried to deploy the image only, with no "Boot To' after so I remain in automation.  Then when I do a directory listing for X: I see an unattend file in there, one that I'm not sure how it even got there. So I deleted the specialize section out, still the same error.  Because it just pushed the image, the rest of the contents of Windows (sysprep and panther) aren't actually accessible yet within automation command line.  Really at a loss here.

    Is there any documentation out there for this that I'm overlooking?

     



  • 2.  RE: Unattend Files and 8.0

    Posted Jul 01, 2016 10:55 AM

    Is it giving a Windows could not parse or process the unattended answer file for pass [specialize]?  If so, check that the machine name is not more than 15 characters.  Thanks,