Rearming Office 2010, the CMID not changing

Hi

I use MDT to deploy Windows 7 images.  I have Office 2010 in the image.

I install Windows7, Office 2010 then rearm Office 2010 using c:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\ospprearm.exe which successfully completes.  I've tried with and without a administrative cmd prompt.

I then sysprep and capture the image, then deploy.

Its been working fine, but in my latest image its not longer working.  When I deploy the image, Office 2010 is activating on the KMS but running cscript C:\program files\microsoft office\office14\ospp.vbs /DCMID on the client they have the same CMID.

I've tried rearming again on one of the new clients, and then checked the CMID and it didn't change.

Any ideas?

September 19th, 2013 3:47pm

Just tried rearming again and then activating.  Activating says Licenced and remaining grace is 180 days.

I've then tried the ospp.vbs /DCMID again and that cmd now says Client Machine ID (CMID): Not Found

whats that mean?

Free Windows Admin Tool Kit Click here and download it now
September 19th, 2013 3:49pm

Hi

There are a number of reasons why this can occur.  For example:

  • Not running sysprep /generalize on your image.       Note that sysprep /generalize is required when creating an image.  See KB162001 for more information
  • Running sysprep with unattend.xml that contains the      <SkipRearm> setting set to 1.  It is not recommended to create      images with this setting but if you do use it you must set it to 0 or      remove it before you reseal the image for the final time

To determine if you are encountering this you can use the Key Management Service Log do the following:

1.On your KMS host open Event Viewer

2. Right click the Key Management Service Log and choose Save all events as

3. Change the Save as type to Text(Tab Delimited)(*.txt)

4. Save the file as KMS.TXT

5. Close out of the Event Viewer completely

6. Open Excel

7. Click File, Open, and browse to KMS.TXT

8. You should see the Text Import Wizard. Choose the following options

    Delimited

    Start Import at Row: 8

    Delimiters: Comma

9. When complete the data may look all messed up. Dont worry we will correct that

10. Click the upper left of the spreadsheet to select the entire spreadsheet

11. Click Data, Sort, In the Sort By selection choose Column D

12. When complete you should see the data sorted in columns.

For more information, refer to the link below:

http://blogs.technet.com/b/askcore/archive/2009/10/16/kms-host-client-count-not-increasing-due-to-duplicate-cmid-s.aspx

http://blogs.technet.com/b/deploymentguys/archive/2011/06/15/deploying-volume-activation-for-office-2010.aspx

Regards

Tylor Wang
TechNet Community Support

September 20th, 2013 8:54am

Like this?

C:\Program Files\Microsoft Office\Office14>cscript ospp.vbs /dcmid
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

---Processing--------------------------
---------------------------------------
Client Machine ID (CMID): Not found.
---------------------------------------
---Exiting-----------------------------

Are you sure that the KMSclient pkey is effective?
The above output is expected if an MAK pkey is used.
Check by using:
cscript ospp.vbs /dstatusall

Here is an example of MAK (a KMSclient would show reversed for License Status=LICENSED):

---------------------------------------
SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c
LICENSE NAME: Office 14, OfficeProPlus-KMS_Client edition
LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel
LICENSE STATUS:  ---UNLICENSED---
ERROR CODE: 0xC004F014
ERROR DESCRIPTION: The Software Licensing Service reported that the product key
is not available.
---------------------------------------
SKU ID: fdf3ecb9-b56f-43b2-a9b8-1b48b6bae1a7
LICENSE NAME: Office 14, OfficeProPlus-MAK edition
LICENSE DESCRIPTION: Office 14, RETAIL channel
LICENSE STATUS:  ---LICENSED---
ERROR CODE: 0 as licensed
Last 5 characters of installed product key: V8H2H
---------------------------------------

Free Windows Admin Tool Kit Click here and download it now
September 20th, 2013 9:54am

No sysprep /generalize is done,  i do that through the inbuilt task sequence in MDT 2012

I think I've found out the issue.

We have Office 2010 and Lync 2013, we got Lync before Microsoft pulled the standalone product.

It seems you have to run ospprearm.exe from the office15 folder in program files\microsoft office and not the office14 or the common files folder.

September 20th, 2013 11:32am

Like this?

C:\Program Files\Microsoft Office\Office14>cscript ospp.vbs /dcmid
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

---Processing--------------------------
---------------------------------------
Client Machine ID (CMID): Not found.
---------------------------------------
---Exiting-----------------------------

Are you sure that the KMSclient pkey is effective?
The above output is expected if an MAK pkey is used.
Check by using:
cscript ospp.vbs /dstatusall

Here is an example of MAK (a KMSclient would show reversed for License Status=LICENSED):

---------------------------------------
SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c
LICENSE NAME: Office 14, OfficeProPlus-KMS_Client edition
LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel
LICENSE STATUS:  ---UNLICENSED---
ERROR CODE: 0xC004F014
ERROR DESCRIPTION: The Software Licensing Service reported that the product key
is not available.
---------------------------------------
SKU ID: fdf3ecb9-b56f-43b2-a9b8-1b48b6bae1a7
LICENSE NAME: Office 14, OfficeProPlus-MAK edition
LICENSE DESCRIPTION: Office 14, RETAIL channel
LICENSE STATUS:  ---LICENSED---
ERROR CODE: 0 as licensed
Last 5 characters of installed product key: V8H2H
--------------------------------------

Free Windows Admin Tool Kit Click here and download it now
September 20th, 2013 12:14pm

It seems that office15 (lync 2013) has taken over shared files.  I can only rearm by running ospprearm.exe from c:\program files\microsoft office\office15\ospprearm.exe

When it activates with KMS, the "Requests with License Status Initial grace period:" is going up for office15 product but not office 2010 product on the KMS server.

September 20th, 2013 12:16pm

Rearming clears that CMID code, and ospp.vbs /act gives it a new CMID

this seems to be correct, it's what I'd expect to see happen
Free Windows Admin Tool Kit Click here and download it now
September 20th, 2013 9:36pm

It seems that office15 (lync 2013) has taken over shared files.  I can only rearm by running ospprearm.exe from c:\program files\microsoft office\office15\ospprearm.exe

When it activates with KMS, the "Requests with License Status Initial grace period:" is going up for office15 product but not office 2010 product on the KMS server.


I've not deployed a mixture of Office product/versions, so I can't tell you what to expect in this scenario.
I would have thought that at worst, you might need to ospprearm both products, or, that the newer ospprearm would cover all products, but, I've never tried it.
September 20th, 2013 9:39pm

After testing ut does increment both Office 2010 and Lync 2013 so if you have two different versions of Office products you rearm all Office products by running ospprearm.exe from the latest version of office e.g.  rearm by running ospprearm.exe from c:\program files\microsoft office\office15\ospprearm.exe

I wrote a script that checks what is present and runs the appropriate ospprearm if anyone is interested.

Free Windows Admin Tool Kit Click here and download it now
September 30th, 2013 6:07am

Hi Chris,

Could you share the script with us. Can you also advise if rearming Office 2013/Lync 2013 that it will also rearm the Office 2010 install.

April 12th, 2015 1:52pm

Hi Chris,

Could you share the script with us. Can you also advise if rearming Office 2013/Lync 2013 that it will also rearm the Office 2010 install.


rem Checks if Office 15 (2013) is present
:Office15Check
IF NOT EXIST "%ProgramFilesPath%\Microsoft Office\Office15\ospprearm.exe" GOTO Office14Check

rem Checks if the registry key has been placed to whether the script has been run/Office rearmed before
reg query HKLM\Software\Microsoft\Office\15.0\Common\OSPPREARM
if %errorlevel%==1 (goto RUNoffice15) else (goto End)


:RUNoffice15

set ProgramFilesPath=%ProgramFiles%
"%ProgramFilesPath%\Microsoft Office\Office15\ospprearm.exe"

rem Add Registry Key to say its already been done so that it doesn't get rearmed when script runs again
REG ADD "HKLM\Software\Microsoft\Office\15.0\Common\OSPPREARM"

rem Activate Office
cscript "%ProgramFilesPath%\Microsoft Office\Office15\ospp.vbs" /act

Exit

rem Checks if Office 14 (2010) is present
:Office14Check
IF NOT EXIST "%ProgramFilesPath%\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\ospprearm.exe" GOTO End

:RUNoffice14

rem Checks if the registry key has been placed to whether the script has been run/Office rearmed before
reg query HKLM\Software\Microsoft\Office\14.0\Common\OSPPREARM
if %errorlevel%==1 (goto RUNoffice14_1) else (goto End)

:RUNoffice14_1

set ProgramFilesPath=%ProgramFiles%
"%ProgramFilesPath%\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\ospprearm.exe"

rem Add Registry Key to say its already been done so that it doesn't get rearmed when script runs again
REG ADD "HKLM\Software\Microsoft\Office\14.0\Common\OSPPREARM"

rem Activate Office
cscript "%ProgramFilesPath%\Microsoft Office\Office14\ospp.vbs" /act


:End
Exit

Free Windows Admin Tool Kit Click here and download it now
April 12th, 2015 2:21pm
I couldn't remember on the issue with activating 2013 and if that did 2010 also, but looking at the script confirms my thoughts, that if you have something of 2013 and 2010, activate 2013 and that activates 2013 and 2010.
April 12th, 2015 2:22pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics