/build/static/layout/Breadcrumb_cap_w.png

System Image installation failure

Hi!

Testing to work with System Image. Have capture a working scripted installation and followed this guide under here:

Deployment to Nodes with the SAME Hardware: 

1. Install Windows Reference OS Image - install on same Hardware, with Drivers & Apps.  

2. Boot and install Device Drivers / Apps. 
3. Update Windows 
4. Sysprep /oobe /generalize - remove system-specific data from Windows Installation - Event Logs, Unique SIDs & other unique info.  - 
5. /oobe - instucts Windows  to run Windows Welcome at the next boot up. 
6. Shutdown - you can specify c:\Windows\System32\sysprep>sysprep.exe /generalize /oobe /shutdown
7. Boot to KBE (K2000 BOOT ENVIRONMENT) > Imaging> Capture image of this machine
8. Capture the Windows installation with K2000 
9. Create a Reference image to install with the same hardware. 


But when I test to install the capture image is not working. I think it fails on "Update Configuration For OS Tasks", after the first reboot.

Systen Image Details under here. Take a look at the Image Status, is that ok ?

umX62m.png


Asked 9 years ago 2933 views
5 Comments   [ + ] Show comments
  • May you try to deploy it to a VMWARE ESXi or VMWARE Workstation/Fusion and see if you experience the same issue?
    Do you have the same if you capture (and the you deploy) the image using the WIM format instead of the Kace one?
    Regards,
    Marco = StockTrader - StockTrader 9 years ago
  • WIM format works fine to deploy! BUT the image has dropped : windows 7 serial, domain, and I cannot log in to Windows =( - Swede 9 years ago
    • that is how sysprep works. You can set all those options in the answer file. - SMal.tmcc 9 years ago
      • see the answer for one of my files - SMal.tmcc 9 years ago
  • Thx! But can I use the same answer file I use to my scripted installation ? The answer file works just fine. Just copy it ? And where should I put this answer file? - Swede 9 years ago
    • you can put it where ever you want just need to call it with the /unattend: switch. Such as /unattend:c:\somedirectory\answerfile.xml - SMal.tmcc 9 years ago
  • http://technet.microsoft.com/en-us/library/cc721973%28v=ws.10%29.aspx - SMal.tmcc 9 years ago
  • But I mean should I put it like a Postinstallation task? - Swede 9 years ago
    • put the file on the master you are taking the image from and when you call sysprep.exe you call that file at the time. - SMal.tmcc 9 years ago
      • I was referring about join the domain as a post task vs including that in your sysprep file. That can be done either way. - SMal.tmcc 9 years ago

Answers (3)

Answer Summary:
Posted by: SMal.tmcc 9 years ago
Red Belt
3
here is one of my basic answer files:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="specialize">
        <component name="Microsoft-Windows-Deployment" 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">
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Path>net user administrator /active:yes</Path>
                    <Order>1</Order>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>
        <component name="Microsoft-Windows-IE-InternetExplorer" 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">
            <AllowedSites>*.tmcc.edu;*.unr.edu</AllowedSites>
            <BlockPopups>yes</BlockPopups>
            <DisableFirstRunWizard>true</DisableFirstRunWizard>
            <DisableWelcomePage>true</DisableWelcomePage>
            <LocalIntranetSites>*.tmcc.edu;*.unr.edu</LocalIntranetSites>
            <PrintBackground>true</PrintBackground>
        </component>
        <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">
            <ProductKey>33PXH-7Y6KF-2VJC9-XBBR8-HVTHH</ProductKey>
            <ShowWindowsLive>false</ShowWindowsLive>
            <TimeZone>Pacific Standard Time</TimeZone>
            <CopyProfile>true</CopyProfile>
        </component>
    </settings>
    <settings pass="oobeSystem">
        <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">
            <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <NetworkLocation>Work</NetworkLocation>
                <ProtectYourPC>3</ProtectYourPC>
            </OOBE>
            <UserAccounts>
                <AdministratorPassword>
                    <Value>VwBpAG4AZABvAHQWERHEWRJRKERSWGH0AG8AcgBQAGEAcwBzAHcAbwByAGQA</Value>
                    <PlainText>false</PlainText>
                </AdministratorPassword>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>VwBpAG4AZABvAasdfAGAGQAGVG8AcgBkAA==</Value>
                            <PlainText>false</PlainText>
                        </Password>
                        <DisplayName>2ndUser</DisplayName>
                        <Name>2ndUser</Name>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
            <RegisteredOrganization>TMCC</RegisteredOrganization>
            <RegisteredOwner>Staff</RegisteredOwner>
            <AutoLogon>
                <Password>
                    <Value>VwBpAG4AZABvAHcasfasdfvasdvfasvAG8AcgBkAA==</Value>
                    <PlainText>false</PlainText>
                </Password>
                <Enabled>true</Enabled>
                <LogonCount>3</LogonCount>
                <Username>administrator</Username>
            </AutoLogon>
        </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>
            <UserLocale>en-us</UserLocale>
        </component>
    </settings>
    <settings pass="generalize">
        <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">
            <OEMInformation>
                <Manufacturer>TMCC ITO</Manufacturer>
                <Model>Admin Image</Model>
                <SupportHours>8 - 5</SupportHours>
                <SupportPhone>673-7800</SupportPhone>
                <SupportURL>http://www.tmcc.edu/ito</SupportURL>
            </OEMInformation>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="catalog:c:/w7image64/install_windows 7 enterprise.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

You can also join it to the domain in the answer file, I do that as a post task instead.
Posted by: mikesharp1 9 years ago
2nd Degree Black Belt
3

Based on SMal.tmcc and what I'm reading seem you are not pointing your sysprep on line 6. to your answer file.

Shutdown - you can specify c:\Windows\System32\sysprep>sysprep.exe /generalize /oobe /shutdown

use this blog I posted a few days ago for reference.

http://www.itninja.com/blog/view/basic-understanding-of-imaging-syspreping-using-kace-2000-tips-and-tricks 

Posted by: Swede 9 years ago
Blue Belt
0
Hi!

Little update! Have done this:

1. Have installed Windows 7 with a working scripted install. No problem here, works fine.
2. I run this line, I just copy the answer file from the scripted install above. sysprep /generalize /oobe /shutdown /unattend:c:\windows\system32\sysprep\unattend.xml
3. Capture the image with KACE, I choosed WIM as image type. Becuse it`s smaller and a lot quicker I think.
4. Have test to deploy it to the same computer and another one. Everything seems to work find under the installation. no error in the deploy log after the deployment. But after the computer start, I got a error. "Windows cannot end the configuration of the system. Reboot computer and try again" but same note after that.

gKqJa2.jpeg

Any idea what could be wrong ?
Comments:
  • post or email me your answer file - SMal.tmcc 9 years ago
  • that is typically a sign of something wrong in the answer file. - SMal.tmcc 9 years ago
    • You got mail! - Swede 9 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ