

These items indicate that the Office 2010 KMS host key is successfully installed and activated. In the following example, key items are Partial Product Key: XXXXX and License Status: Licensed. The output of a computer which has the Office 2010 KMS Host License Pack installed resembles the following.

To determine whether a computer has the Office 2010 KMS Host License Pack installed and has an active Office KMS host, run the following command:Ĭscript slmgr.vbs /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864 It's not common to create an Office KMS host unintentionally, because setting up an Office KMS requires a specific product key and the installation of the Microsoft Office 2010 KMS Host License Pack. In DNS Manager, locate the appropriate forward lookup zone, and then delete the _vlmcs SRV records that exist for each computer which is not to serve as a Windows KMS host.įor more information, see the following articles: Run the following command to display the license information for the installed and active Windows edition: To restart the Software Protection Service, run the following commands: net stop sppsvc To prevent instability in the license service, restart the system or the Software Protection Service. Run cscript slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx, where xxxxx-xxxxx-xxxxx-xxxxx-xxxxx is Windows product key (there should be 25 numbers). To resolve this issue, follow these steps on the computer(s) in question, replace the KMS product key and convert it to a KMS or MAK client: In many cases, Windows KMS hosts may be unintentionally set up by users who mistakenly entered a KMS host product key, instead of a Windows client product key. Running this nslookup command frequently reveals _vlmcs SRV entries that are tied to unauthorized Windows or Office KMS hosts. Review the kms.txt file, and it should contain one or more entries similar to the following: _vlmcs._ SRV service location: Nslookup -type=srv _vlmcs._tcp >%temp%\kms.txt To determine whether a KMS client can locate a KMS host or whether unwanted KMS hosts exist on the network, run a command similar to the following: Discover Office and Windows KMS hosts through DNSīy default, Windows and Office clients discover KMS hosts through DNS and a related _vlmcs SRV record.

The following steps are similar in Office KMS 2010, 2013, 2016, and 2019.
