Windows Server 2016 activation

The following information outlines preliminary planning considerations that require attention when using Key Management Service (KMS) activation involving Windows Server 2016. For information about KMS activation involving the operating system earlier than the operating system listed here, see Step 1: Review and select the activation method.

KMS uses client-server mode to activate the client. The KMS client connects to a KMS server (known as a KMS host) for activation. The KMS host must be on the local network.

KMS hosts do not have to be dedicated servers, and KMS can share a single host with other services. You can run a KMS host on any physical or virtual system running Windows 10, Windows Server 2016, Windows Server R2, Windows 8.1, or Windows Server 2012.

KMS hosts running on WINDOWS10 or Windows 8.1 can only activate computers that are running the client operating system. The following table summarizes the requirements for the network for KMS hosts and clients, including Windows Server 2016 and Windows 10 clients.

KMS can be hosted in may need to be updated with the KMS server to support activation of these newer clients. If you receive an activation error, check to see if you have the appropriate update listed below this table.
Volume License for Windows Server 2016	windowsserver windowsserver R2 Windows Server,	windows Server 2016 (all editions) Windows LTSB (2015) Windows 10 Professional Edition Windows 10 Enterprise Edition Windows Server R2 (all editions) Windows8.1 Professional Edition Windows 8.1 Enterprise Edition Windows Server 2012 (all editions) Windows R2 (all editions) Windows7 Pro Windows7 Enterprise Edition
Volume License for Windows 10	windows 7 Windows 8 Windows 8.1 Windows ten	windows 10 Professional Edition Windows 10 Pro n Windows 10 Enterprise Edition Windows 10 Enterprise Edition n Windows 10 Education Windows 10 Education Edition N Windows 10 Enterprise LTSB Windows 10 Enterprise Edition LTSB n Windows8.1 Pro Windows 8.1 Enterprise Edition Wind Ows7 Professional Edition Windows7 Enterprise Edition
"Windows Server R2 for Windows 10" Volume license	WindowsServer R2 Windows Server Standard Windows Server Datacenter Windows Server R2 Standard Windows Server R2 Datacenter Windows Server 2016	Windows 10 Professional Edition Windows 10 Enterprise Edition Windows Server R2 (all editions) Windows8.1 Professional Edition Windows 8.1 Enterprise Edition Windows Server 2012 (all editions) Windows R2 (all editions) Windows7 Professional Edition Windows7 Enterprise Edition

Note

You may need to install one or more of these updates, depending on the operating system that the KMS server is running and the operating system that you want to activate.

• KMS installations on Windows 7 or Windows Server R2 must be updated to support activation of clients running Windows 10. For more information, see Enable Windows 7 and Windows Server R2 KMS hosts to activate updates for Windows 10.

• KMS installations on Windows Server 2012 must be updated to support activation of clients running Windows 10 and Windows Server 2016 or later client or server operating systems. For more information, see the July 2016 update rollup for Windows Server 2012.

• KMS installations on Windows 8.1 or Windows Server R2 must be updated to support activation of clients running Windows 10 and Windows Server 2016 or later client or server operating systems. For more information, see the July 2016 update rollup for Windows 8.1 and Windows Server R2.

• Windows Server R2 cannot be updated to support activation of clients running Windows Server 2016 or later operating systems.

A single KMS host can support an unlimited number of KMS clients. If the number of clients exceeds 50, we recommend that you prepare at least two KMS hosts in case a KMS host is unavailable. Most organizational units run two KMS hosts to meet the needs of the entire infrastructure.

Meet the operational requirements of KMS

KMS can activate both physical and virtual computers, but to use KMS activation, the number of computers in the network must meet minimum requirements (called activation thresholds). KMS clients are not activated until this threshold is reached. To ensure that the activation threshold is reached, the KMS host calculates the number of computers on the network that request activation.

The KMS host calculates the number of recent connections. When a client or server contacts a KMS host, the host adds the computer ID to its count, and then returns the current count value in its response. When the count is high enough, the client or server is activated. The client is activated when the count is 25 or higher. When the count is 5 or greater, the server and the batch edition of Microsoft Office products are activated. KMS counts only the unique connections in the last 30 days and stores only 50 of the most recent contacts.

KMS activation is valid for 180 days, a period known as the activation validity interval. To remain active, KMS clients must connect to the KMS host at least once every 180 days to renew their activation. By default, KMS client computers try to renew the activation every 7 days. After the client's activation is renewed, the activation validity period will restart the calculation.

Meet KMS feature requirements

KMS activation requires a TCP/IP connection. The KMS host and client are configured by default to use domain Name System (DNS). By default, KMS hosts use DNS dynamic Update to automatically publish the information that KMS clients need to find and connect to a host. You can accept these default settings, and if you have special network and security configuration requirements, you can manually configure the KMS host and client.

After the first KMS host is activated, the KMS key used on the first host can be used to activate up to 5 additional KMS hosts on the network. After the KMS host is activated, the administrator can use the same key to reactivate the same host 9 times.

If your organizational unit requires more than 6 KMS hosts, you should request more activations for your organizational unit's KMS key-for example, if a Volume license agreement covers 10 physical locations, and you want a local KMS host in each location.

Note

To resolve this special situation, please contact your activation call center. For more information, see Microsoft Volume Licensing.

By default, a volume licensing version of Windows 10, Windows Server 2016, Windows 8.1, Windows Server R2, Windows Server 2012, Windows 7, Windows Se is run. RVer R2 's computer is a KMS client that does not require additional configuration.

If you want to convert your computer from a KMS host, MAK, or Retail edition of Windows to a KMS client, install the applicable KMS client installation key. For more information, see Appendix A:KMS Client Installation keys.

This article is from the "YQCD" blog, make sure to keep this source http://117295.blog.51cto.com/107295/1947271

Windows Server 2016 activation