Reset Windows Rearm count

When working with Machine Creation Services we discovered that the Clients all have the same CMID. A different CMID is needed to activate using KMS services. We searched for a solution and everyone mentioned rearming the machine, but then we received the message that we can’t rearm. We then searched for a solution but everyone was pointing out to set the Skiprearm to 1. When testing this we discovered that the CMID keeps the same after rearming the Windows machine.

We discovered that the “Remaining Windows Rearm Count” was 0. which means that when you set SkipRearm then you don’t rearm the machine. Knowing this we searched how to reset the Rearm count and found an article that explained how we could reset the rearm count. http://www.daniel-mitchell.com/blog/reset-windows-7-rearm-count/

To do this follow the below instructions:

  1. Create reset.bat on C:\
  2. add the following code:

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

  3. Restart your machine to repair mode using the F8 key.
  4. In the System Recovery Options menu, select Command Prompt.
  5. Now type in D:\reset.bat. The C-drive is used as a recovery partition.
  6. If the script is executed successfully, you should get the message “The operation completed successfully”.
  7. Reboot your machine.

Now the rearm count is reset to 5. You can check this using slmgr /dlv.

rearm count

Now set make sure the Skiprearm is set to 0 at the following location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\SoftwareProtectionPlatform

Now the Image is ready to deploy and the KMS server will receive different CMID’s from the servers.

Active Directory-Based Activation

In  previous post we Installed VAMT and then added licenses and devices, now we will create the possibility to use Active Directory-Based Activation. To use the Active Directory-Based Activation you need at least one Windows Server 2012 domain controller.

Installing Active Directory-Based Activation

To use AD-Based Activation you need to install the Volume Activation Services Server role. This can be done using the Server Manager. In the Server Manager click on Manage and then click Add Roles and Features.

Select Role-based of feature-based installation and click Next.

ADBA - Install (1)

Select the server which you want to install the Volume Activation Services on from the server pool and click next.

Select the Volume Activation Services in the Server Roles screen and click Next.

ADBA - Install (2)

A new screen (pop-up) will appear which displays the required features just select Add Features.

VAMT 3.0 Adding licenses and manage host (part 2)

In my previous post we installed VAMT 3.0 and created the database.

In this post we will add MAK and KMS keys and we will add some host to monitor the servers/clients to see if the activation is successful. Because you need at least 5 Servers or 25 Clients before KMS keys will work we are using MAK keys in this post.

When you opened VAMT and are connected to the database you will see the following screen.

VAMT 3.0 Overview

As you can see there are now products discovered or License keys installed.

To install the license keys “Right click” on the “Product keys” and select “Add product keys..“, then add the license keys into the box and click on “Add Key(s)” when you like to add multiple keys use a separate line for the different keys.

After the key is verified it will show up in the product keys overview.

VAMT Add Key

VAMT Keys

VAMT 3.0 Installation (part 1)

In this series I’m writing a 2 part article about how to install and configure VAMT.

When you want to manage your MAK or KMS licenses activation within your organization you can use Microsoft Volume Activation Management Tool (VAMT) version 3.0. Whit VAMT 3.0 you can add licenses, view activations and more. VAMT is part of the Windows Assessment and Deployment Kit (ADK) for Windows® 8. 

Before you can use VAMT you have to download it first at the following location: http://www.microsoft.com/en-us/download/details.aspx?id=30652

VAMT can be installed in the following Operating Systems:

  • Windows® 8
  • Windows® 7
  • Windows Server® 2012
  • Windows Server® 2008 R2
  • Windows Vista®
  • Windows Server® 2008

When using VAMT 3.0 you need an SQL server, when you don’t have an SQL server you can select the SQL 2012 Express to be installed on your system. The user who is installing VAMT needs DbCreator rights on the SQL server which you like to use. All other users which want to connect to the database need to be db_owner of the database used to install VAMT.

When installing ADK you need to specify the location the files are stored, in the screenshot below you can select to install or just download to install it on a separate computer, we will choose to install.

ADK Specify location to install

Change vDisk from MAK to KMS

When using MAK on a provisioned vDisk with multiple versions and you need to change the activation to KMS, it’s important to first create a Merge of the version to a now Base image. This has to be done because you need to change the Microsoft Volume Licensing option within the vDisk properties and dis can only be done on al the versions and only when the vDisk isn’t locked.

Important: you need at least 25 Windows 7 clients or 5 Windows 2008 R2 host using KMS to get it work.

After creating a Merge base, copy the VHD and PVP file and rename them to a appropriate name, in this example the new name is “XenAppKMS”, after renaming import the vDisk into the Provisioning Services Console and add it to a test or maintenance device.

 Imported XenAppKMS