Now the Image is ready to deploy and the KMS server will receive different CMID’s from the servers. Now set make sure the Skiprearm is set to 0 at the following location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\SoftwareProtectionPlatform WMIC Class SoftwareLicensingService Call reArmWindows.
SLMGR REARM EXCEEDED HOW TO
Knowing this we searched how to reset the Rearm count and found an article that explained how we could reset the rearm count. which means that when you set SkipRearm then you don’t rearm the machine. We discovered that the “Remaining Windows Rearm Count” was 0. When testing this we discovered that the CMID keeps the same after rearming the Windows machine. 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.
Thus, you have an additional three times, new 30 days for the new activation.
SLMGR REARM EXCEEDED WINDOWS 10
A different CMID is needed to activate using KMS services. 1.) Extend trial test period on Windows 10 The command slmgr -rearm is actually provided, even if the hardware has been not replaced on the PC to enable reactivation with a new product key (Key). When working with Machine Creation Services we discovered that the Clients all have the same CMID.