Important: Active Directory-Based activation cannot be used to activate Office 2010. To get an opportunity to activate Office 2013 on the KMS-server, you have to install Microsoft Office 2013 Volume License Pack (like with the AD-based activation), select Key Management Service (KMS) as the type of. Microsoft Office 2010 Toolkit is the most trusted tool for Microsoft Office and Windows activation. Microsoft Toolkit is a blend of most activators. Microsoft Toolkit is a blend of most activators. Auto KMS and EZ-Activator modules are assembled to provide perfect activation measures.

1. Volume License Key

-->

Applies to:Volume licensed versions of Office 2019 and Office 2016, including Project and Visio

All 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. For more information, see How DNS is used to find a KMS host computer.

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 HKEY_LOCAL_MACHINESoftwareMicrosoftOfficeSoftwareProtectionPlatform registry key on the KMS client. The KMS host computer name is specified by KeyManagementServiceName (REG_SZ), and the port is specified by KeyManagementServicePort (REG_SZ). 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 Tools to manage volume activation of Office.

Configure KMS host caching

You 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 Tools to manage volume activation of Office.

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. Mio transfer hack c250 plus download.

To disable KMS host caching, type the following command, and then press ENTER:

To enable KMS host caching, type the following command, and then press ENTER:

Check the license status of Office

The following table describes the license state of the Office with respect to activation.

Volume License Key

License state	Description
Licensed	By 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-tolerance	If 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 notification	If 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 Tools to manage volume activation of Office.

Related topics

-->

Applies to: Office 2010

Topic Last Modified: 2012-11-20

This is a quick start guide for activating Volume License editions of Microsoft Office 2010. If you are not familiar with volume activation, see Windows Volume Activation Planning Guide (http://go.microsoft.com/fwlink/p/?LinkId=183040), Plan for volume activation of Office 2010, and Deploy volume activation of Office 2010. The intended audience is IT administrators who are familiar with Windows volume activation and who want to know which steps are required for volume activation of Office client products.

Volume License editions of Office 2010 require activation. The activation technology is based on the Windows Software Protection Platform. If you are familiar with Windows Key Management Service (KMS) or Multiple Activation Key (MAK) activation, you will be familiar with requirements for Office 2010 activation. This article describes the differences between Windows and Office. It also includes the steps that are required to activate Office 2010.

Important

This information applies to volume-licensed editions of Office 2010. It does not apply to Office Professional Plus for Office 365, which is licensed through subscription.
Office 2010 is supported on Windows 8 and Windows Server 2012.

In this article:

• Differences between Windows and Office activation

• Scenarios for Office 2010 volume activation

• Office 2010 volume activation methods

• Install and configure the KMS host

• Co-host an Office KMS host with a Windows KMS host

Differences between Windows and Office activation

Differences between Windows activation and Office activation with regard to both KMS and MAK are as follows:

For KMS activation:

• The activation threshold for the KMS host is five client computers. At least five physical or virtual computers that have Office installed must request activation before KMS clients can be activated.

• Only one KMS host key must be installed and activated on the Office 2010 KMS host. This KMS host then activates all Office 2010 products that have the KMS client key installed.

• When using slmgr.vbs commands on the KMS host, you must enter the Office 2010 activation ID (bfe7a195-4f8f-4f0b-a622-cf13c7d16864). For more information about the slmgr.vbs script, see Deploy volume activation of Office 2010.

• To ensure that the Office 2010 KMS host key is recognized, you must install the Office 2010 license files by downloading and running KeyManagementServiceHost.exe at the Microsoft Office 2010 KMS Host License Pack (http://go.microsoft.com/fwlink/p/?LinkID=169244) Web site.

For MAK activation:

• Each Office suite or product has its own MAK key.

• There are separate MAK keys for Microsoft Project 2010 and Microsoft Visio.

  For example, with a single MAK key, you can activate all applications in the Microsoft Office Professional Plus 2010 suite. However, you must enter separate MAK keys for Project 2010, Visio, or any of the Office Professional Plus 2010 suite products, such as Microsoft Word 2010 or Microsoft Excel 2010.

Scenarios for Office 2010 volume activation

Scenarios help users determine what best fits their current or proposed environment and they provide step-by-step guidance for activating the Volume License editions of Office 2010 software. The detailed steps for activation that are listed in the scenarios apply to all Volume License editions of Office 2010 client products (Office Professional Plus 2010, Visio 2010, and Project 2010).

The scenarios are located in the following articles:

• 
  Plan KMS activation of Office 2010

• 
  Plan MAK independent activation of Office 2010

• 
  Plan MAK proxy activation of Office 2010

• 
  Scenario: Core network - KMS activation of Office 2010

• 
  Scenario: Secure network - KMS or MAK activation of Office 2010

• 
  Scenario: Disconnected computers activating Office 2010

• 
  Scenario: Test or development lab activating Office 2010

Office 2010 volume activation methods

There are two methods for activating Volume License editions of Office 2010: Key Management Service (KMS) and Multiple Activation Key (MAK). For a detailed description of these two methods, see Review activation methods in Plan volume activation of Office 2010.

Install and configure the KMS host

Only the following operating systems can serve as the Office 2010 KMS host:

• Windows 8

• Windows Server 2012

• Windows Server 2003 Standard, Enterprise, and Datacenter editions (32-bit and 64-bit) or with any applicable service packs

  Important

  The Office 2010 KMS host is not supported on Windows Small Business Server 2003. For more information, see Microsoft Knowledge Base article 968915: An update is available that installs Key Management Service (KMS) 1.2 for Windows Server 2003 Service Pack 2 (SP2) and for later versions of Windows Server 2003 (http://go.microsoft.com/fwlink/p/?LinkId=183046).

• Volume License editions of Windows 7

• Windows Server 2008 R2

Important

The KMS host key for Office 2010 is not specific to a particular operating system. You can use it on any of the operating systems that are listed above. This includes both 32-bit and 64-bit editions.

The following operating systems are not supported as the KMS host:

• Windows Vista, all versions

• Windows Server 2008, including service packs

For more information, see Volume Activation 2.0 for Windows Vista and Windows Server 2008 (http://go.microsoft.com/fwlink/p/?LinkId=151726).

Co-host an Office KMS host with a Windows KMS host

If you currently have a Windows KMS host that runs on an operating system that supports an Office 2010 KMS host, we recommend that you use the same computer for your Office 2010 KMS host. You still must follow these steps to install and activate an Office 2010 KMS host key. For more information, see Plan volume activation of Office 2010.

To activate an Office 2010 KMS host on Windows Server 2003

• To configure an Office 2010 KMS host on Windows Server 2003, see To activate an Office KMS host on Windows Server 2003 in Deploy volume activation of Office 2010.

To activate an Office 2010 KMS host on Windows 7 or Windows Server 2008 R2

• The KMS host service is included as part of Windows 7 and Windows Server 2008 R2. For information about how to activate the KMS host on these two platforms, see To activate an Office 2010 KMS host on Windows 7 or Windows Server 2008 R2 in Deploy volume activation of Office 2010.

See Also

Concepts

Volume activation overview for Office 2010
Plan volume activation of Office 2010
Deploy volume activation of Office 2010
Tools to configure client computers in Office 2010
Troubleshoot volume activation for Office 2010

Other Resources

Office 2010 Volume Activation forum
Office 2010 forums