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.
This method assumes that Windows or Office has never been activated on this machine before. Complete the steps below during that 30-day period. As part of that process you'll be informed that you have 30 days to activate the product.
To use this method, first install the software (Windows or Microsoft Office). Please be sure that any firewalls between the client machine and the KMS server are open to incoming and outgoing traffic on TCP port 1688. KMS activation can be blocked by a firewall. If you are using virtual machines for testing and cross-compatibility on Macintosh computers, you'll need to use the manual method in those circumstances. With this method, you'll need to run commands on each machine - and for each software package - during the 30 day grace period after installation. This page describes how to manually activate products. The concept behind the procedure on this page is explained on our main KMS page.
If you're not one of those, you should talk to your TSP or net admin before proceeding. This page is intended for technical support providers and network administrators. Activate Desktop Edition of Microsoft Office 2016.Activate a Windows Operating System (All Supported Versions).