Microsoft KB Archive/929828: Difference between revisions

From BetaArchive Wiki
m (Text replacement - "<" to "<")
m (Text replacement - ">" to ">")
 
Line 90: Line 90:
== WORKAROUND ==
== WORKAROUND ==


To work around this issue, use the <SkipRearm&gt; setting in an XML answer file (Unattend.xml) to skip the Rearm process when you build the Windows Vista image.<br />
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 Vista image.<br />
<br />
<br />
The following text is an example of an XML answer file:
The following text is an example of an XML answer file:
<pre class="fixed_text"><settings pass=&quot;generalize&quot;&gt;
<pre class="fixed_text"><settings pass=&quot;generalize&quot;>
         <component name=&quot;Microsoft-Windows-Security-Licensing-SLC&quot; processorArchitecture=&quot;x86&quot; publicKeyToken=&quot;31bf3856ad364e35&quot; language=&quot;neutral&quot; versionScope=&quot;nonSxS&quot; xmlns:wcm=&quot;http://schemas.microsoft.com/WMIConfig/2002/State&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;&gt;
         <component name=&quot;Microsoft-Windows-Security-Licensing-SLC&quot; processorArchitecture=&quot;x86&quot; publicKeyToken=&quot;31bf3856ad364e35&quot; language=&quot;neutral&quot; versionScope=&quot;nonSxS&quot; xmlns:wcm=&quot;http://schemas.microsoft.com/WMIConfig/2002/State&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;>
             <SkipRearm&gt;1</SkipRearm&gt;
             <SkipRearm>1</SkipRearm>
         </component&gt;
         </component>
     </settings&gt;</pre>
     </settings></pre>
<br />
<br />
<br />
<br />
'''Note''' You must make sure that the <SkipRearm&gt; setting is removed from the final unattended file that is used to deploy computers in a production environment. If <SkipRearm&gt; 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.
'''Note''' 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.


</div>
</div>

Latest revision as of 09:25, 21 July 2020

Knowledge Base


An error message occurs when you run "Sysprep /generalize" in Windows Vista: "A fatal error occurred while trying to Sysprep the machine"

Article ID: 929828

Article Last Modified on 8/13/2007



APPLIES TO

  • Windows Vista Enterprise 64-bit Edition
  • Windows Vista Ultimate 64-bit Edition
  • Windows Vista Business
  • Windows Vista Business 64-bit Edition
  • Windows Vista Enterprise
  • Windows Vista Ultimate



SYMPTOMS

When you try to run the System Preparation Tool (Sysprep) in Windows Vista, and you use the /generalize option, you may receive the following error message:

A fatal error occurred while trying to Sysprep the machine.

The Setupper.log file may contain lines that resemble the following:

Error [0x0f0082] SYSPRP LaunchDll: Failure occurred while executing 'C:\Windows\System32\slc.dll, SLReArmWindows', returned error code -1073425657


Error [0x0f0070] SYSPRP RunExternalDlls: An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -1073425657


Error [0x0f00a8] SYSPRP WinMain: Hit failure while processing sysprep generalize providers; hr = 0xc004d307


Note The Setupper.log file is located in the \Windows\System32\Sysprep\Panther folder.

CAUSE

This error may occur if the Windows Software Licensing Rearm program has run more than three times in a single Windows Vista image.

RESOLUTION

To resolve this issue, you must rebuild the Windows Vista image.

WORKAROUND

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 Vista image.

The following text is an example of an XML answer file:

<settings pass="generalize">
        <component name="Microsoft-Windows-Security-Licensing-SLC" 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">
            <SkipRearm>1</SkipRearm>
        </component>
    </settings>



Note 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.

MORE INFORMATION

The Windows Software Licensing Rearm program restores the Windows system to the original licensing state. All licensing and registry data related to activation is either removed or reset. Also, any grace period timers are reset.

To run the Rearm process in Windows Vista, use one of the following methods:

  • Run Sysprep /generalize on the computers that are used to build the custom Windows Vista image.
  • Run the Slmgr.vbs script in an elevated Command Prompt window. For example, run cscript c:\windows\system32\slmgr.vbs –rearm.

Note Administrative credentials are required to run the Rearm process. The Rearm process can be run a maximum of three times in a Windows Vista image. For more information about the System Preparation Tool, click the following article number to view the article in the Microsoft Knowledge Base:

299840 How to use Sysprep with Windows Product Activation or Volume License Media to deploy Windows XP



Additional query words: WinVista Sysprep

Keywords: kbtshoot kbprb kbexpertisebeginner KB929828