Article ID: 2463130 - View products that this article applies to.
Note This issue does not affect clients who use MAK or retail keys to activate Microsoft Office 2010.
Volume license customers who downloaded and installed the version of Office 2010 Proofing Tools Kit that is dated November 5, 2010 (or an earlier version) may experience an issue when they try to activate Office 2010.
Any customer who installed the Proofing Tools Kit by using the default Config.xml file that was included with the kit sets the KMS host value on their client computers to a KMS host that is internal to Microsoft. This overwrites the value in the Config.xml file that existed before the Proofing Tools Kit was installed. This new value breaks automatic discovery of KMS hosts for every client on which the Proofing Tools Kit is installed. This issue then prevents Office applications from activating against the KMS host or hosts that were specified in the Office 2010 Config.xml file beffore the Proofing Tools Kit was installed.
Customers may not be aware of this issue for between 30 and 180 days:
This issue occurs because both the 32-bit and 64-bit versions of Office 2010 Proofing Tools Kit that (dated November 5, 2010 or earlier) have the following setting enabled in the Config.xml file:
Setting Id="KMSSERVICENAME" Value="oa-o14kms-02.redmond.corp.microsoft.com" />
Because the Config.xml element is shared across Office 2010, and installation of the Proofing Tools Kit overwrites the value that is listed above, activation for all Office 2010 client applications is affected.
To resolve this issue, customers who obtained a Proofing Tools Kit for Office 2010 on or before November 5, 2010 must determine whether they have deployed the Proofing Tools Kit to the client with the default Config.xml that was included in the kit or with a Config.xml file that they edited.
If the Proofing Tools Kit was deployed with an edited Config.xml fileCustomers who obtained the Proofing Tools Kit on or before November 5, 2010 and deployed it with a Config.xml file where they edited the <Setting Id= “KMSSERVICENAME” Value=” ” /> setting to include the KMS host addresses or addresses that are specific to their organization do not have to take any action.
If the Proofing Tools Kit was deployed without an edited Config.xml fileCustomers who obtained the Proofing Tools Kit on or before November 5, 2010 and deployed it to client computers without editing the Config.xml file can use either of the following methods to resolve the issue.
Method 1Delete the following registry subkey:
If you obtained the Proofing Tools Kit on or before November 5, 2010 but have not yet deployed itCustomers who obtained the Proofing Tools Kit on or before November 5, 2010 but have not yet deployed it to clients, have two options:
For more information about the Config.xml file in Office 2010, visit the following Microsoft TechNet website:
Article ID: 2463130 - Last Review: March 14, 2012 - Revision: 3.0