Microsoft Volume Activation at UCLA

Microsoft has rolled-out a new type of product activation called Volume Activation (VA) for products such as Office , Windows and Windows Server. 

PLEASE NOTE:  These mechanisms are not yet required to use other Microsoft products, but Microsoft has stated that it is their plan to require this for other products in the future.

The needs of individual departments using Microsoft on campus vary, so it will be up to each department to determine which activation mechanism will best suit their needs.  Most departments will likely need to use a combination of these mechanisms.

One key point to keep in mind is that an “activation” is not the same as a “license”.  A “license” is the right to use a particular product.  An “activation” is a tool by which access to a “license” is achieved.  There could be multiple activations per license.  An example of this would be when a computer crashes and the license needs to be re-installed.  This would count as two activations, but as only one license.

For more information on Volume Activation, go to Product Activation and Key Information

For planning, deployment and operational guidance for activating volume-licensed editions of Windows 10, go to “Volume Activation Resources for Windows 10.

For planning, deployment and operational guidance for activating volume-licensed editions of Windows Server 2012, go to "Windows Server 2012 Technical Library".

KEY MANAGEMENT SERVICE (KMS)
MULTIPLE ACTIVATION KEY (MAK)
OEM ACTIVATION FOR NEW COMPUTERS WITH WINDOWS 10 OR WS12 PRE-INSTALLED
ADDITIONAL INFORMATION REGARDING ACTIVATION MECHANISMS

KEY MANAGEMENT SERVICE (KMS)

In general, KMS will be the best method by which to activate Office, Windows client or Windows on a server that is regularly connected to the campus network.  KMS is designed to be a lightweight, easy-to-use service.  It will activate any later version volume-licensed Office installation, Windows client or Windows Server on the KMS network.

KMS activations are non-perpetual.  Three days after installation, a computer configured for KMS activation will attempt to connect with the KMS server.  It will need to successfully connect within 30 days or it will go into reduced functionality mode.  After the initial connection, a computer will need to successfully connect with the KMS once every 180 days or it will go into reduced functionality mode.

In an effort to avoid any unnecessary duplication of effort and resources, a KMS campus-wide service has been established.  Every campus department has the option to use this KMS to activate Office, Windows client or Windows Server on all machines licensed to use those products. Access to the campus-wide KMS is limited to computers using a UCLA IP address. 

Here's detailed directions on how SYSTEM ADMINISTRATORS can activate via the UCLA campus KMS.

Here's detailed directions on how non-System Administrators (everyone else!) can activate via the UCLA campus KMS.

There is one KMS key to be shared by all campus units participating in both the MCCA and Select Agreements.  Each KMS key defaults to allow for six KMS key service installations.  When that limit has been reached, the campus must request that Microsoft increase the activation limit for our KMS key.  It is important that we know as a campus when we’re close to reaching that limit, so we can request that it be raised before running out of installations.  If your unit needs to set up its own KMS service, please contact Software Central .

The University of Wisconsin-Madison has posted a useful resource on how to convert a Windows computer from MAK to KMS activation.

Changing MAK to KMS Activation

NOTE*If you plan to activate against the KMS server on campus, do not enter the MAK key you may have received from SHI. Any key you may have received from SHI is a MAK key, not a KMS key.The ISO files from SHI are KMS by default. If you enter a MAK key you will negate the KMS licensing. In other words if you intend to activate against the campus KMS, do not enter the MAK key you get from SHI. The MAK key activates against Microsoft Servers the KMS service activates against UCLA KMS servers.

The keys that you get from SHI are MAK keys and are only intended for machines that don’t have connectivity to the UCLA backbone.

All Office 2013 and 2016 for Windows and Windows 10 volume-licensed products have a Generic Volume License Key (GVLK) preinstalled to activate against an Office 2013/2016 KMS host. If you entered a MAK key for a product and you want to change the activation method back to KMS, use the appropriate KMS client GVLK. For more information, see Generic Volume License Keys for KMS and Active Directory activation. The recommended way to enter the key is by using the Volume Activation Management Tool, VAMT. You can also use ospp.vbs /inpkey to enter the key.

For Office 2013/2016 suites, only one key is required for all the products in the suite. For example, if you use Office Professional Plus, you must enter only the Office Professional Plus 2013/2016 key for the complete suite. For a complete listing of the keys, see Generic Volume License Keys for KMS and Active Directory activation.

MULTIPLE ACTIVATION KEY (MAK)

In general, the MAK will be the best method by which to activate Office, Windows Client or Windows Server on a machine that is not regularly connected to the campus network.  A common example of this would be the laptop of a faculty member doing research in the field or a stand alone server that for whatever reason does not regularly connect to the campus network.

There is one MAK per product to be shared by all campus units participating in both the MCCA and Select Agreements.  Each MAK defaults to allow for a set number of installations.  When that limit has been reached, the campus must request that Microsoft increase the activation limit fo that particular MAK.  It is important that we know as a campus when we’re close to reaching that limit, so we can request that it be raised before running out.  If you ever attempt to use a MAK and receive a message that this limit has been exceeded, please immediately send an email to Software Central

If your unit is licensed for Office, Windows Client or Windows Server under either the MCCA or Select Agreements, then UC’s authorized reseller Software House International (SHI) can provide you with the appropriate MAK upon request.  Please be sure you indicate whether you obtained your licenses via the campus MCCA, or if you purchased via the Microsoft Select Plus Agreement (you may need to provide your PO number for Select Plus purchases) If you require a MAK for Office, Windows Client or Windows Server, please contact:

Lynda Olander
ucsystem@shi.com
800-535-5210

8am-7pm PST M-F

The MAK works similar to the current Volume License Key (VLK) in that you only need to enter the MAK into the client computer or server once.  The two main differences from the VLK are:

1)  The default limit on the quantity of activations for each MAK (detailed above).

2)  Under the old system, if a VLK was found to have been used to install licenses outside of the scope of the legitimate licensee, Microsoft would de-activate that VLK.  This would result in all installations under that VLK, both legitimate and illegitimate, no longer working until a new VLK was applied to each computer.  Under the new system, if a MAK is found to be used for illegitimate installation, Microsoft will only de-activate it for future installations.  Current legitimate installations would continue to function, but a new MAK would need to be used for future legitimate installations.

A MAK activated client will only need to be connected to the Internet one time for initial activation.

OEM ACTIVATION FOR NEW COMPUTERS WITH WINDOWS CLIENT OR WINDOWS SERVER PRE-INSTALLED

Most OEMs sell computers with Windows Client or Windows Server pre-installed. Vendors perform OEM activation by associating Windows to the firmware (BOIS) of the physical system. This occurs before the systems are sent to the customer, so that no additional actions are required of the end user. This method of activation is know as OEM Activation 2.0.

OEM Activation 2.0 is valid as long as the customer uses the OEM-provided image on a system. If you want to create a customized image, you can use the image provided by your OEM as the basis for creating your own custom image. Otherwise, you will need to use a different activation method.

If you are planning to purchase a new OEM computer with Windows Client pre-installed and your unit is licensed under the MCCA or Select Software Assurance, please read the Windows Client Upgrade Rights section before placing your order.

If your department purchases a new OEM computer with Windows Client pre-installed, it will come with an OEM activation key already configured.  The computer will need to be connected to the Internet for initial activation.  It will only need to activate once unless the machine is subsequently wiped clean and reinstalled.

ADDITIONAL INFORMATION REGARDING ACTIVATION MECHANISMS

Click here for Microsoft’s Volume Activation 2.0 Technical Guidance .

Click here for information on Microsoft's Volume Activation Management Tool