Hello,

We just recently got a KMS key for MS project, and when I attempted to add the key to the KMS server, it causes the Office Professional Plus 2013 key to become unlicensed.  I understand Project is an office product, and I have an active KMS key for Office Professional Plus 2013, does this mean that key is what will be used to activate Project?

Thank You,

Thad

Hi Thad,

Please see the similar thread and Mr. Don has explained:

https://social.technet.microsoft.com/forums/office/en-US/d9fc307f-cbab-45c9-9fd4-e8a728fab308/installing-visio-2013-kms-key-on-kms-server

I copied here:

====

when I login to VLSC, I don't have different KMS pkeys for Office vs. Visio vs. Project.

they are named "Office 2010 Suites and Apps [KMS]" and "Office 2013 Suites and Apps [KMS]"

Depending on how you search or navigate within VLSC, there might appear to be KMS key for each suite/product, but you should find that the Office one is the same pkey as Visio and also Project.

Every time I've ever installed a KMS (I have done quite a few), the Office KMS will happily activate Office Std, Office ProPlus, Visio Std/Pro/Prem, Project Std/Pro.

(actually it's really easy to activate Visio Prem, since Prem is the default for the VL package of Visio. which is a problem if the customer is only licensed for a lesser edition of Visio.....)

====

Then we can use: slmgr.vbs /dli all

and also check the event logs on your KMShost, to see what it's getting and what it's giving out

Project 2013 uses the same activation ID as the matching Office suite, so if Project 2013 is not activating then Office 2013 would also be busted.

Regards,

George Zhao
TechNet Community Support