Requirements
Unique KMS key for Windows 7: xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Unique KMS key for Office 2010: xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Generic KMS client key for Windows 7: 33PXH-7Y6KF-2VJC9-XBBR8-HVTHH (Windows 7 Enterprise)
Note that you can find the operating systems KMS keys here:
KMS Client Setup Keys
http://technet.microsoft.com/en-us/library/ff793421.aspx
Generic KMS client key for Office 2010: VYBBJ-TRJPB-QFQRF-QFT4D-H3GVB (Office Professional Plus 2010)
Note that you can find the Office 2010 KMS keys here:
Troubleshoot volume activation for Office 2010
http://technet.microsoft.com/en-us/library/ee624355.aspx#section2_3
KMS Server: Windows 7 (You’ll need to use the version respective to the unique KMS key you purchased)
Step #1 – Enter unique KMS key onto Windows 7
Log onto the Windows 7 desktop that you will be using for your KMS server and enter the unique Windows 7 KMS key you purchased:
Ensure that activation has been successful:
Step #2 – Download the Microsoft Office 2010 KMS Host License Pack
To enter the unique Office 2010 KMS key you’ve purchased, you’ll need to download and install the Microsoft Office 2010 KMS Host License Pack onto your Windows 7 KMS server. You can download the installation binary here:
Microsoft Office 2010 KMS Host License Pack
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=25095
Execute the KeyManagementServiceHost.exe executable to install and then enter the unique KMS key for Office 2010 when prompted.
Step #3 – Enter generic client KMS key onto Windows 7
Log onto your Windows 7 client (not the KMS Windows 7 server) and enter the generic client KMS key. Note that if this is the first or less than 25th client, you will receive the following error:
Error Code 0xC004F038
This error is expected because you need a minimum of 25 Windows 7 desktops trying to activate in order for the KMS server to activate them.
To check to see how many Windows 7 clients are trying to activate against the KMS server, you can execute the following command on the KMS server:
cscript slmgr.vbs /dlv
Step #4 – Enter generic client KMS key into Office 2010
Log onto your Windows 7 client (not the KMS Windows 7 server), open an Office 2010 applications, navigate to File –> Help and enter the generic client KMS key. Note that if this is the first or less than 5th client, office will not activate but this is normal:
To check to see how many Office 2010 clients are trying to activate against the KMS server, you can execute the following command on the KMS server:
cscript slmgr.vbs /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864 on windows 7 host to check for office 2010 activation
Step #5 – Determine whether your KMS clients are trying to activate against the KMS server
Once you have your one or more KMS clients set up, tracking the activation requests from clients can be done by reviewing the logs on the KMS server in: Event Viewer –> Applications and Services Logs –> Key Management Service
In the Key Management Service window, you’ll see information logged as it pertains to the KMS service:
In the screenshot above, you’ll see the event ID 12290 information events logged and if you were to open up these events, you’ll be able to determine which hosts in your network has attempted to activate themselves against the KMS server.
For more information about how to read the information in these event 12290 logs, please refer to one of my previous blog posts:
Microsoft KMS Server Troubleshooting and Tips
https://blog.terenceluk.com/2012/01/microsoft-kms-server-troubleshooting.html
Step #6 – Start Activating
Now that you have set up your KMS server on Windows 7, continue with your deployment of the other Windows 7 desktops with Office 2010 by either:
- Entering the generic client KMS keys manually
- Use the Volume Activation Management Tool (VAMT) to enter the keys in bulk
——————————————————————————————————————————————————————
Hope this helps anyone looking for a walkthrough to set up a KMS server and the clients.
