skip to primary navigationskip to content
 

Office Volume Activation

Office Volume Activation Overview

With the release of Office 2010 Microsoft have expanded Volume Activation 2 to this product. Office activation works in a similar manner to Windows Volume Activation. You must have either a KMS or MAK key. KMS requires a local server which is available on the CUDN. The client machine must contact this server regularily for Office 2010 to remain activated. Microsoft Project is activated in the same way as Microsoft Office, so the instructions below apply to both Office and Project.

The versions of Office 2010 available from software sales (sales@ucs.cam.ac.uk) are Volume Licensed and have a KMS key built into the product already.  You should KMS activate Office 2010 where possible.  If the system is to be away from the CUDN on a regular basis, e.g. laptops, you should apply for a MAK key when purchasing the license. A MAK key can be requested later if necessary.  Volume License versions are for institutional use only.  Institutional machines are defined as being owned or leased and insured by the institution.

The ospp.vbs script

The configuration of Office volume license versions is done via the ospp.vbs (the Office Software Protection Platform) script. To use this script it is important that the command prompt window is run with Administrative privileges. If not logged in as a local administrator right-click on the cmd.exe icon and select Run As Administrator. The command shell will have Administrator: Command Prompt rather than just Command Prompt in the top left of the window.

Office 2010

For 32-bit versions of Office on 32-bit versions of Windows or 64-bit versions of Office 2010 on 64-bit versions of Windows the script is normally located in the following folder:

  • C:\Program Files\Microsoft Office\Office14

To change to the folder type the following in an administrative command prompt window:

 cd "C:\Program Files\Microsoft Office\Office14" 

If you are installing the 32-bit version of Office on 64-bit versions of Windows the script is normally located in the following folder:

  • C:\Program Files (x86)\Microsoft Office\Office14

To change to the folder type the following in an administrative command prompt window:

 cd "C:\Program Files (x86)\Microsoft Office\Office14"

NOTE: The quotes are needed to cope with empty spaces in the folder names.

Office 2013

For 32-bit versions of Office on 32-bit versions of Windows or 64-bit versions of Office 2013 on 64-bit versions of Windows the script is normally located in the following folder:

  • C:\Program Files\Microsoft Office\Office15

To change to the folder type the following in an administrative command prompt window:

 cd "C:\Program Files\Microsoft Office\Office15" 

If you are installing the 32-bit version of Office on 64-bit versions of Windows the script is normally located in the following folder:

  • C:\Program Files (x86)\Microsoft Office\Office15

To change to the folder type the following in an administrative command prompt window:

 cd "C:\Program Files (x86)\Microsoft Office\Office15"

NOTE: The quotes are needed to cope with empty spaces in the folder names.

Office 2016

For 32-bit versions of Office on 32-bit versions of Windows or 64-bit versions of Office 2016 on 64-bit versions of Windows the script is normally located in the following folder:

  • C:\Program Files\Microsoft Office\Office16

To change to the folder type the following in an administrative command prompt window:

 cd "C:\Program Files\Microsoft Office\Office16" 

If you are installing the 32-bit version of Office on 64-bit versions of Windows the script is normally located in the following folder:

  • C:\Program Files (x86)\Microsoft Office\Office16

To change to the folder type the following in an administrative command prompt window:

 cd "C:\Program Files (x86)\Microsoft Office\Office16"

NOTE: The quotes are needed to cope with empty spaces in the folder names.

For further information on the different versions of Windows and Office see the Version Suitability section below

Activating Office

The volume license version available from Software Sales comes with the KMS key already installed with the product. You will only need to change the key if you want to convert from KMS to MAK activation. See the section below Converting from KMS to MAK Activation..

Note: Systems which will be away from the CUDN for over 180 days in a continuous period should use Office with a MAK key, not KMS.

Setting the Activation Server and Activating

To use KMS activation you will need to set the system to use the Computing Services Volume License Activation Server (kms.csx.private.cam.ac.uk) using the ospp.vbs script. Navigate to the location of this script (see section above) and use the following commands:

To set the KMS activation server enter:

cscript ospp.vbs /sethst:kms.csx.private.cam.ac.uk

Once the KMS server has been set you can activate Office by entering:

cscript ospp.vbs /act

You should see something like this:

activated

Activation can also be checked in any program in Office by clicking on the File tab and selecting Help in Office 2010 or Account in Office 2013

After activation Windows will attempt to renew activation every 7 days on a sliding 180 day grace period. After renewal the slider starts the 180 day grace period again.

Activating Computers Remotely

You can activate computers remotely simply by specifying the credentials you want to use as follows:

  • cscript ospp.vbs [Option:Value] [ComputerName] [User] [Password]

Converting from a KMS to MAK Key

Systems which will not be connected to the CUDN on a regular basis should use MAK rather than KMS activation. To do this you simply need to change the existing KMS key to a MAK key, available from Software Sales (sales@ucs.cam.ac.uk).

  • cscript ospp.vbs /inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

The system can then be activated in the same way:

  • cscript ospp.vbs /act

Troubleshooting

Firstly, make sure you have selected Run as Administrator when you start the command prompt.

Then rerun cscript ospp.vbs /sethst:kms.csx.private.cam.ac.uk making sure the address is correct.

Then check the service is available from the system you are trying to activate.
Download portqry from here: Microsoft Port Query V2, and attempt to connect to 1688 on kms1.csx.private.cam.ac.uk.
For portqry the syntax is:
portqry -n kms1.csx.private.cam.ac.uk -e 1688

Then check the error codes.

Checking Error Codes

If you receive any errors during the process of activation, eg 0xC004F042, you can check the full description with the following command:

  • cscript ospp.vbs /ddescr:0xC004F042

The most common error you normally see is 0x80070005, notably when trying to activate Office 10 on Windows Vista and Windows 7 systems.
This happens when you forget to select Run as Administrator. You need to do this on these systems even if your account is an Administrator account. If this is the case then go back to Step 1, and start again.

If you see error 0xC004F074 one possible problem is your system time and date. Make sure they are correct and the same as the server (ie G.M.T.)

Another cause of 0xC004F074 is the KMS server is incorrect. Re-set the KMS activation server, making sure it is set to kms.csx.private.cam.ac.uk

Error 0x4004F00C may indicate you are unable to activate via port 1688. Lapwing does not allow communication over this port therefore you cannot activate via Lapwing.

Software Protection Platform Service is not running Error message

If you receive:

  • Error: The Software Protection Platform Service is not running.
  • Current status: Stopped
  • Run: cscript ospp.vbs/ osppsvc restart

Go to Start, Control Panel, Administrative Tools, Services and make sure Office Software Protection Platform Service is started.

Testing KMS Actvity

There are a couple of commands which allow you to view and test the connectivity and history of KMS activation.

To check the KMS activation history to see whether the host was successfully contacted, enter the following command:

  • cscript ospp.vbs /dhistorykms

Useful links and Further Information

Full documentation is available from Microsoft. Some links can be found below.

Office volume activation overview

http://technet.microsoft.com/en-us/library/ee624349.aspx

Tools for configuring client computers in Office 2010

http://technet.microsoft.com/en-us/library/ee624350.aspx

Planning volume activation of Office 2010

http://technet.microsoft.com/en-us/library/ee624358.aspx

Version Suitability

Microsoft recommend most users install the 32-bit version of Office 2010 on both 32 and 64-bit Operating Systems because currently many common add-ins for Office will not function in the 64-bit edition. The 64-bit version of Microsoft Office 2010 is more suitable for users who commonly use very large documents or data sets e.g. need Excel 2010 to access greater than 2GB of memory. If you are going to use the 64-bit verson of Office you will need to upgrade or remove any 32-bit add-ins. In order to install a 64-bit version of Office 2010 users must have a 64-bit version of Windows. See http://technet.microsoft.com/en-us/library/ee681792.aspx and http://msdn.microsoft.com/en-us/library/ee691831(office.14).aspx