WSM and KMS

The solution

Was not as simple as displayed in this document for me, here is what i had to do in additon.

The /rearm command was not enough, I had to run the slmgr.exe /ato in a startup script in order for the client to contact the license server. This solved the problem with Windows 7 Enterprise activation.

The there was office 2010. the CMID here is different, doesn't use the same ID as Windows, so you have to run a script C:\Program Files (x86)\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM. EXE. While the image is in private mode. Just run it right after you rearm windows, and then set the image back to volatile.

Also needed a startup script in my case here. this is my startupscriot, applied to the client OU:

"Activation.CMD":
ECHO OFF
C:\Program Files\Microsoft Office\Office14\OSPP.VBS" /ACT
cscript C:\windows\system32\slmgr.vbs /ato

You probably need to remarm both windows and office each time you update the image. Not sure how this goes with the max rearm count of 3 that you have in both office and windows.

Ketil Lidahl
Systems Consultant
Norsk Data Senter

I found it: https://support.wyse.com/OA_HTML/csk...ortByOrder%3D1

Ketil Lidahl
Systems Consultant
Norsk Data Senter

 Originally Posted by kel@nds.no 

Was not as simple as displayed in this document for me, here is what i had to do in additon.

The /rearm command was not enough, I had to run the slmgr.exe /ato in a startup script in order for the client to contact the license server. This solved the problem with Windows 7 Enterprise activation.

The there was office 2010. the CMID here is different, doesn't use the same ID as Windows, so you have to run a script C:\Program Files (x86)\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM. EXE. While the image is in private mode. Just run it right after you rearm windows, and then set the image back to volatile.

Also needed a startup script in my case here. this is my startupscriot, applied to the client OU:

"Activation.CMD":
ECHO OFF
C:\Program Files\Microsoft Office\Office14\OSPP.VBS" /ACT
cscript C:\windows\system32\slmgr.vbs /ato

You probably need to remarm both windows and office each time you update the image. Not sure how this goes with the max rearm count of 3 that you have in both office and windows.

Thanks Kel... I am going to try it.. It seems that some of the clients boot and don't get the message that they are activated.. I can run the /ato command from the CLI and it says it activated successfully. I will try this and hope that it clears up the one off's I have that do not... thanks!

WSM 5.0.1 has been released on 12/24/12 and it has a new feature that helps with rearming the OS: 
"Microsoft License Enabling for Streamed Clients - WSM allows administrators to check and enable Microsoft licensing using a UI as part of the image capture process and as part of the patching process. Thus reducing errors and making it easier to enable licensing via Microsoft KMS (Key management server). This is applicable only to Windows 7 Professional and Enterprise volume license editions."

Unfortunately this does not help with your KMS activation cound, and all I can tell is that it has worked for many others fine which profes it is feasable.

Hello mhaase, 
thank you for your reply, I finally won against KMS activation count (created, activated and deleted 25 VMs  )
I just updated WSM to version 5 and I'm starting to see the changes. However, I'm already stuck in a OS patching problem that I described in another thread.
Can you help me about that?

 Originally Posted by kel@nds.no 

You probably need to remarm both windows and office each time you update the image. Not sure how this goes with the max rearm count of 3 that you have in both office and windows.

On the PDF document linked above, at page #6, point n. 3/a, it says "rearm count is unlimited for activated KMS device". 

I have not tested it yet - I'm still trying to increase the KMS count to 25.... :'(