Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Workaround for customization failure due to rearm count down to zero (52636)

Last Updated: 2/6/2018Categories: Best PracticesTotal Views: 5405Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Windows customization fails due to Sysprep complaining that there are no more rearms available, which is usually happen for Windows7 and Windows 2008 OS.

Customization fails and there is error message like “A fatal error occurred while trying to Sysprep the machine.”  and with the following in customization logs:

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

Purpose

Best practice to clone and customize a windows Virtual Machine.

Cause

Windows 7/Windows 2008 system by design has a rearm count of 3 after fresh install. This rearm count will be slip by 1 for each VM clone operation. And It will also slip by 1 for each “sysprep/generalize” operation which is part of windows customization process. And it will drop to 1 directly if activated by KMS server.

There are two scenarios customer may face this issue:

Repeated clone and customize a Windows template VM in chain. Some customer will clone and customize a windows GOS from a base template (Base VM->clone1, rearm count is 2). Then do clone and customize of this cloned VM (clone1->clone2, rearm count is 1). Then clone and customize it again and again which will make rearm count to 0 and result in customization failure.

Clone and customize a Windows template VM already activated by KMS server. Windows VMs activated by KMS server has rearm count of 1. Clone and then customize  the cloned VM will fail to sysprep.

Resolution

To workaround this issue,

Post vSphere 6.5 is to clone template VM without doing customization.

Run KMS activation manually since NICs are connected before customization.

Run VM customization will PASS.

Commands to activate VMs via KMS server.

​cscript \windows\system32\slmgr.vbs -skms YOUR_KMS_SERVER_ADDRESS
cscript \windows\system32\slmgr.vbs -ato

Related Information

This affects Windows7 and Windows Server 2008/Windows Server 2008 R2 OS
This is usually not found for Windows 8/8.1, Windows 10, Windows Server 2012/Windows Server 2012R2, Windows 2016 OS. As these newer windows OS usually have large rearm count for “1000” if activated by KMS.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
ブランチ ターゲット インジェクションに対するハイパーバイザーアシストによるゲストの軽減 (52085)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

Take Our Survey

Support Assistant