Office 2010 KMS activation key facts. KMS, which stands for Key Management Service Host, is software for Windows that works as a proxy for Windows Vista, Windows 7, and Office 2010 activation. Office 2010 volume editions are delivered with the KMS client, which doesn't have to be installed.
KMS clients will find the KMS host automatically through DNS. When an end user starts Office 2010 (no admin privileges required), the KMS client will contact the KMS host, which will then activate Office 2010 automatically. This means you don't have to enter a product key on the client side. Windows 7 (volume editions) and Windows Server 2008 R2 are delivered with the KMS host that can activate Office 2010. The KMS host for Windows Vista and Windows Server 2008 can't be used for Office 2010 activation. Make sure that a DNS server that supports SRV records is available and that you have sufficient privileges.
More information about KMS DNS configuration can be found. KMS 1.1 can be downloaded and installed on Windows Server 2003 SP1 or later:. After you install KMS 1.1, you have to. You need at least Windows Server 2003 SP2 for that. For all Windows editions, you will need the KMS host license files for Office 2010, which are included in the. Make sure your firewall allows outbound connections for the server where the KMS host runs.
The KMS host will contact Microsoft's activation service. You also need the Office 2010 KMS host product key, which you can get at the if you purchased Office 2010 licenses. You will also need the Office 2010 activation ID 'bfe7a195-4f8f-4f0b-a622-cf13c7d16864.'
. The KMS host has to be activated with these commands:slmgr.vbs /ipk slmgr.vbs /ato. You will need at least 5 Office 2010 installations before client activation starts (not 25, as for Windows Vista and Windows 7).
After installation, Office 2010 will work normally without activation for a grace period of 25 days. After this, users will see notification dialogs whenever they start an Office application. After the 30 th day, the, reminding you that activation has failed. There is no Reduced Functionality Mode like with the retail editions of Office 2010. Thus users can still continue with their work. You can 5 times to extend this grace period to 180 days. Every KMS-activated Office 2010 has to renew its activation after 180 days.
To verify which Office 2010 clients have been activated, you can use Microsoft's free. Additional reading:In my next post, I will cover Office 2010 MAK activation. I have been looking at the Microsoft documentation for an hour now and then I found your post - great work at summarizing and listing the need-to-knows.Also just a question: What would happen if I install Office 2010 on a PC before setting up a KMS host? When it prompts for a key can I just put in the KMS key and will this work? What I want to find out is whether it's absolutely necessary to install a local KMS host or can I still choose to activate with Microsoft from each PC if I have KMS key?
Activate volume licensed versions of Office by using KMS. 6/4/2019. 3 minutes to read.In this articleApplies to: Volume licensed versions of Office 2019 and Office 2016, including Project and VisioAll volume licensed versions of Office, including Project and Visio, have a Generic Volume License Key (GVLK) preinstalled. GVLKs support both Key Management Service (KMS) and Active Directory-based activation. On the KMS host computer configured to support volume activation of Office, you install and enable only one KMS host key to activate all volume licensed versions of Office.If the KMS host computer is available and properly configured, activation of Office occurs transparently to the user. Office is activated the first time it runs, provided that there have been at least four previous activation requests to the KMS host computer.
This is because the KMS host computer requires at least five requests before it begins activating clients.You don't have to do anything else to enable activation of Office by KMS. KMS clients can locate a KMS host computer automatically by querying DNS for service (SRV) resource records (RRs) that publish the KMS service.
Microsoft Office 2010 Kms
For more information, see.If the network environment does not use SRV RRs, you can manually assign a KMS client to use a specific KMS host computer by configuring the HKEYLOCALMACHINESoftwareMicrosoftOfficeSoftwareProtectionPlatform registry key on the KMS client. The KMS host computer name is specified by KeyManagementServiceName (REGSZ), and the port is specified by KeyManagementServicePort (REGSZ). The default port is 1688. These registry keys can also be set through by using ospp.vbs script. For more information about the ospp.vbs script, see.Configure KMS host cachingYou can configure whether or not the last used KMS host computer is saved to the cache on the KMS client. If the KMS host computer is not cached, the KMS client will query DNS every time that activation is attempted.
This means that the priority and weight parameters set for KMS host computers will be honored. If the KMS host computer is cached, the KMS client won't query DNS and instead will attempt to contact the cached KMS host computer that last resulted in successful activation.To configure KMS host caching, you can use the opss.vbs script. For more information about the ospp.vbs script, see.To configure KMS host caching, open an elevated command prompt on the KMS client computer and go to the Program FilesMicrosoft OfficeOffice16 folder. If you installed the 32-bit version of Office on a 64-bit operating system, go to the Program Files (x86)Microsoft OfficeOffice16 folder.To disable KMS host caching, type the following command, and then press ENTER: cscript ospp.vbs /cachst:FALSETo enable KMS host caching, type the following command, and then press ENTER: cscript ospp.vbs /cachst:TRUECheck the license status of OfficeThe following table describes the license state of the Office with respect to activation.
License stateDescriptionLicensedBy default, the KMS client requests activation with the KMS host computer one time every seven days. (The number of days is configurable.) This design allows the maximum possible time for the client to be in the licensed state.After the client is successfully activated, it remains in the licensed state for 180 days. When in the licensed state, users do not see any notification dialog boxes prompting them to activate the client. After 180 days, the activation attempt process resumes. If activation is continually successful, the whole activation experience is transparent to the user.Out-of-toleranceIf activation does not occur during the 180-day period, Office goes into the out-of-tolerance state for 30 days.
Users then see notifications that request activation.Unlicensed notificationIf activation does not occur during the out-of-tolerance state, Office goes into the unlicensed notification state. Users then see notifications that request activation and a red title bar.You use the ospp.vbs script with the /dstatusall option to check the license state for all Office clients. Use the /dstatus option to check the status of the local client. For more information about using the ospp.vbs script, see.
Related topics.