+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 16
Windows 7 Thread, Win7 Sysprep Woes : returned error code -1073425657 in Technical; Where I am with our win7 testing and deployment: 1. Win7 policies written and test PC locked down and desktop ...
  1. #1
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,286
    Thank Post
    80
    Thanked 45 Times in 31 Posts
    Rep Power
    30

    Win7 Sysprep Woes : returned error code -1073425657

    Where I am with our win7 testing and deployment:

    1. Win7 policies written and test PC locked down and desktop redirected etc.
    2. Test PC installed with all app and tested and those broke - fixed!
    3. Following this technet artice to create an image: Building a Standard Image of Windows 7: Step-by-Step Guide

    I get as far as the part titled : "Generalize the Image"

    Sysprep begins to run then BAM : A fatal error occurred while trying to Sysprep the machine"

    A bit of searching found this article by MS:
    An error message occurs when you run "Sysprep /generalize" in Windows Vista or Windows 7: "A fatal error occurred while trying to Sysprep the machine"

    It lists the cause of my error as:
    "This error may occur if the Windows Software Licensing Rearm program has run more than three times in a single Windows image"

    I am confused....has it run more than 3 times? Did I run it without knowing it? Does the PC run this itself and indeed over the course of the 3 days it's taken me to build the PC it's run in the background?

    It lists the solution to my problem as:
    To resolve this issue, you must rebuild the Windows image

    What does this mean? Surely it does nt mean start again and re-install win7 from scratch and all our apps again?

    It does say there is a workaround which is:
    To work around this issue, use the <SkipRearm> setting in an XML answer file (Unattend.xml) to skip the Rearm process when you build the Windows image.

    It then goes on to say:
    You must make sure that the <SkipRearm> setting is removed from the final unattended file that is used to deploy computers in a production environment. If <SkipRearm> is not removed from the unattended file that is used to deploy computers in a production environment, the KMS current client count does not increase for new clients that are added to the network.

    What does that mean?
    This is the final unattended XML that I am using is nt it? It's going to be captured by the imagex.exe process - or is there some way to edit the unattend.xml with the Rearm part - run sysprep - capture the image - and then replace the unattend.xml file with one with the rearm part taken out.

    Any suggestions?

  2. #2
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,286
    Thank Post
    80
    Thanked 45 Times in 31 Posts
    Rep Power
    30
    This is a copy of my unattend.xml
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
    <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    <SetupUILanguage>
    <UILanguage>en-US</UILanguage>
    </SetupUILanguage>
    <InputLocale>0409:00000409</InputLocale>
    <UserLocale>en-US</UserLocale>
    <UILanguage>en-US</UILanguage>
    <SystemLocale>en-US</SystemLocale>
    </component>
    <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    <UserData>
    <AcceptEula>true</AcceptEula>
    <FullName></FullName>
    <Organization>Our School</Organization>
    <ProductKey>
    <Key>OUR KEY</Key>
    <WillShowUI>Never</WillShowUI>
    </ProductKey>
    </UserData>
    </component>
    </settings>
    <settings pass="oobeSystem">
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    <OOBE>
    <HideEULAPage>true</HideEULAPage>
    <NetworkLocation>Work</NetworkLocation>
    <ProtectYourPC>2</ProtectYourPC>
    <SkipMachineOOBE>true</SkipMachineOOBE>
    <SkipUserOOBE>true</SkipUserOOBE>
    </OOBE>
    <TimeZone>GMT Standard Time</TimeZone>
    <UserAccounts>
    <AdministratorPassword>
    <Value>password</Value>
    <PlainText>true</PlainText>
    </AdministratorPassword>
    <LocalAccounts>
    <LocalAccount>
    <Password>
    <Value>password</Value>
    <PlainText>true</PlainText>
    </Password>
    <Description>initial user</Description>
    <DisplayName>school user</DisplayName>
    <Group>Administrators;Users;</Group>
    <Name>school</Name>
    </LocalAccount>
    </LocalAccounts>
    </UserAccounts>
    </component>
    <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    <InputLocale>en-gb</InputLocale>
    <UserLocale>en-gb</UserLocale>
    <UILanguage>en-gb</UILanguage>
    <SystemLocale>en-gb</SystemLocale>
    </component>
    </settings>
    <settings pass="specialize">
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    <CopyProfile>false</CopyProfile>
    <RegisteredOrganization>School</RegisteredOrganization>
    <RegisteredOwner>School</RegisteredOwner>
    <Display>
    <ColorDepth>32</ColorDepth>
    <HorizontalResolution>1024</HorizontalResolution>
    <RefreshRate>60</RefreshRate>
    <VerticalResolution>768</VerticalResolution>
    </Display>
    </component>

    </settings>
    </unattend>
    Last edited by kennysarmy; 25th March 2011 at 08:54 AM.

  3. #3

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,137
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    77
    Hi

    Are you use VL key for Windows 7?
    Have you tested the xml file again?
    Modify the xml file using WSIM.
    Are you still having the issue?

    Sukh

  4. #4
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,286
    Thank Post
    80
    Thanked 45 Times in 31 Posts
    Rep Power
    30
    Thanks for your reply.

    I am not entering a key when I install w7 - as I am using KMS to activate
    Yes I did have the foresight to take a ghost image prior to trying the syspre and I have tried again and got the same result.

    I did successfully create a win7 DVD with sp1 and ie9 which was done without using an answer file.
    My test build was installed from this DVD then I added all my apps.

    When I open WSIM and click to create a new answer file it says I should base this on an existing image - I am choosing the one from my DVD - I might try creating a new unattend.xml this way.

  5. #5

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,137
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    77
    Hi

    When you capture the image, I generally only use Windows tool where I can. Then you should create the unattend in WSIM using this image.

    Can you try to create a image and as you said, use this image to create the answer file and don't use the SkipRearm in the pass.

    Test and let me know how it goes.

    Sukh

  6. #6
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,286
    Thank Post
    80
    Thanked 45 Times in 31 Posts
    Rep Power
    30


    Fatal error again:

    this is the new unattend.xml

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
    <component name="Microsoft-Windows-International-Core-WinPE" 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">
    <SetupUILanguage>
    <UILanguage>en-gb</UILanguage>
    </SetupUILanguage>
    </component>
    <component name="Microsoft-Windows-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">
    <UserData>
    <ProductKey>
    <WillShowUI>Never</WillShowUI>
    </ProductKey>
    <AcceptEula>true</AcceptEula>
    <Organization>school</Organization>
    </UserData>
    </component>
    </settings>
    <settings pass="oobeSystem">
    <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">
    <OOBE>
    <HideEULAPage>true</HideEULAPage>
    <NetworkLocation>Work</NetworkLocation>
    <ProtectYourPC>2</ProtectYourPC>
    <SkipMachineOOBE>true</SkipMachineOOBE>
    <SkipUserOOBE>true</SkipUserOOBE>
    </OOBE>
    <UserAccounts>
    <AdministratorPassword>
    <Value>bAA0ADIANAA0ADcAMgA4AEEAZABtAGkAbgBpAHMAdAB yAGEAdABvAHIAUABhAHMAcwB3AG8AcgBkAA==</Value>
    <PlainText>false</PlainText>
    </AdministratorPassword>
    </UserAccounts>
    <RegisteredOwner>school</RegisteredOwner>
    <RegisteredOrganization>school</RegisteredOrganization>
    <ShowWindowsLive>false</ShowWindowsLive>
    <TimeZone>GMT Standard Time</TimeZone>
    </component>
    </settings>
    <cpifflineImage cpi:source="wim:d:/sources/install.wim#Windows 7 Professional" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>

  7. #7
    Paid_Peanuts's Avatar
    Join Date
    Jun 2007
    Location
    South Yorkshire
    Posts
    232
    Thank Post
    11
    Thanked 13 Times in 12 Posts
    Rep Power
    17
    How many times have you sysprep'd this image?
    Did you know you can only sysprep win7 3 times?! then it is game over and there is no work around! We got this message and racked our brains for ages until we found out the behaviour of sysprep.

    We build an image then ghost it. then we sysprep it, then if we have to revisit the image to ammend we ghost back to box then update - ghost back then sysprep again so the sysprep count always looks like its on '1'.
    Last edited by Paid_Peanuts; 25th March 2011 at 11:03 AM.

  8. #8
    cromertech's Avatar
    Join Date
    Dec 2007
    Location
    Cromer by the coast
    Posts
    731
    Thank Post
    177
    Thanked 109 Times in 97 Posts
    Rep Power
    54
    I've found this page How to Reset Available Remaining Rearm Count in Windows 7 My Digital Life

    And this section is what you need

    Quote Originally Posted by MyDigitalLife
    The said WPA vulnerability is related to a WPA registry key which contains Last Rearm Time information in Windows 7. When the WPA registry key is deleted, the whole licensing status of Windows 7 is re-initiated to the Initial Grace Period (more on Windows 7 and Visa license status), as if Windows 7 is just installed in OOBE (out of the box experience). The deletion of the WPA registry key is achievable with the following command:

    reg load HKLM\MY_SYSTEM “%~dp0Windows\System32\config\system”
    reg delete HKLM\MY_SYSTEM\WPA /f
    reg unload HKLM\MY_SYSTEM

    With the importance of WPA registry key, it’s understandable the Microsoft locks the key and all its sub-keys from been changed, modified, removed or deleted in normal user session. So users have to run the command manually from WinRE (Windows Recovery Environment) or WinPE (Windows Preinstallation Environment).

  9. #9
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,286
    Thank Post
    80
    Thanked 45 Times in 31 Posts
    Rep Power
    30
    What I did was :
    Install win7 from our original DVD media, then did all the MS updates and a few reg tweaks then sysprepped, created an image file using imagex and followed some instructions to merge the wim file in to our original media and created a bootable iso -which successfully installs windows 7.

    I used this DVD to install windows 7 again and then I installed all of our apps and tested it all.

    I've now come to create a new wim file and a bootable USB stick so we can roll this image out....

    Have I bust it by using the DVD I've created which was from a sysprepped image

    I'm really struggling to understand what the re-arm thing is and why this is so complicated.....

  10. #10
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,286
    Thank Post
    80
    Thanked 45 Times in 31 Posts
    Rep Power
    30
    Quote Originally Posted by cromertech View Post
    I've found this page How to Reset Available Remaining Rearm Count in Windows 7 My Digital Life

    And this section is what you need
    Thanks.
    Followed the procedures there to reset the rearm count to 5.

    Going to try again...

    But first will create another fall-back ghost image - un sysprepped of course...

  11. #11
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,286
    Thank Post
    80
    Thanked 45 Times in 31 Posts
    Rep Power
    30
    working

  12. #12
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,286
    Thank Post
    80
    Thanked 45 Times in 31 Posts
    Rep Power
    30
    bummer.....

    Created my wim file from imagex.exe

    PC rebooted and now I cannot login as the "administrator" account is disabled.

    Have added this in to my unattend.xml

    <LocalAccounts>
    <LocalAccount>
    <Password>
    <Value>password123</Value>
    <PlainText>true</PlainText>
    </Password>
    <Description>initial user</Description>
    <DisplayName>school admin user</DisplayName>
    <Group>Administrators;Users;</Group>
    <Name>school</Name>
    </LocalAccount>
    </LocalAccounts>

  13. #13

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,137
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    77
    Hi

    It is disabled be default. Please see.

    Enable and Disable the Built-in Administrator Account

    Sukh

  14. #14

    Join Date
    Mar 2011
    Location
    Bournemouth
    Posts
    280
    Thank Post
    16
    Thanked 74 Times in 64 Posts
    Rep Power
    21
    You can add a command to your xml file to enable the administrator account during sysprep. Add a synchronous command to your specialze sction using the app or paste in:

    Code:
            <component name="Microsoft-Windows-Deployment" 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">
                <RunSynchronous>
                    <RunSynchronousCommand wcm:action="add">
                        <Order>1</Order>
                        <Path>net user administrator /active:yes</Path>
                    </RunSynchronousCommand>
                </RunSynchronous>
            </component>

  15. Thanks to ChrisMiles from:

    kennysarmy (25th March 2011)

  16. #15
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,286
    Thank Post
    80
    Thanked 45 Times in 31 Posts
    Rep Power
    30
    Nice one Chris..

    I'm getting there with all this.....

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. Replies: 11
    Last Post: 15th March 2011, 11:01 AM
  2. [SIMS] Sims on Win7 install error [SOLVED]
    By edutech4schools in forum MIS Systems
    Replies: 12
    Last Post: 16th November 2010, 03:08 PM
  3. Eee PC 701 SD : Unknown Bios error. Error code =FFEF
    By JJonas in forum Netbooks, PDA and Phones
    Replies: 0
    Last Post: 11th November 2010, 11:15 AM
  4. Replies: 0
    Last Post: 29th December 2009, 02:27 PM
  5. error code is 7
    By stu in forum Windows
    Replies: 5
    Last Post: 17th June 2009, 03:56 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •