Configure Office 2010 to volume activate at the same time you install a MAK key

If you are using the Office Customization Tool (OCT) to configure a Multiple Activation Key (MAK) key, you can also activate Office 2010 at the time that you install the MAK key. A MAK key is one of the methods that Office Activation Technologies provides for activating products licensed under Microsoft Volume Licensing programs. By using a MAK key, clients activate Office 2010 online through Microsoft-hosted activation servers or by telephone.

To activate Office 2010 when you configure a MAK key in the OCT, you set the AUTO_ACTIVATE property value. Follow these steps:

1. In the OCT, select Modify Setup properties on the left pane, and then click Add in the right pane.

2. In the Add Property Value dialog box, in the Name box, type AUTO_ACTIVATE. Note that property names must be uppercase.

3. In the Value box, type 1, and then click OK.

Another option is to use the Config.xml file to set the AUTO_ACTIVATE property. For more information, see Setting element in Config.xml file in Office 2010.

For more information about volume activation in Office 2010, see the resources in the Plan for volume activation and Configure and deploy volume activation of Office 2010 sections of the Office 2010 Resource Kit.

Comments (7)

  1. DarrylMo says:


    See my comment to Jamie Kennedy. You either run the 'ospp.vbs /act'  command to activate manually or set AUTO_ACTIVATE in the OCT to automate the process. Also, did you place the OCT.msp file in the Updates folder before running the script?


  2. DarrylMo says:


    I asked internally about this issue. It’s possible that you have some sort of proxy in place, and that the process or user account under which the installation is running does not have permission to bypass the proxy.

    Is the user that’s running the script a local admin, and if not, have they set UserOperations=1 under

    HKLM SoftwareMicrosoftOfficeSoftwareProtectionPlatform as shown in…/ee624357.aspx


  3. DarrylMo says:

    @Jamie Kennedy: Set AUTO_ACTIVATE but don't also run ospp.vbs /act. the ospp.vbs commands are for setting things manually. Let the AUTO_ACTIVATE setting automate the process. Thx, Darryl

  4. gorilla uganda says:

    thanks for the information

  5. Jamie Kennedy says:

    I have tried setting the AUTO_ACTIVATE option in OCT, and tried running the OSPP.vbs /act as a argumant with no luck

  6. Andrew says:

    Thank you – all the other posts I found were trying to run a program after install to run ospp.vbs and it was never running.

  7. Cerbere says:

    I have been trying to deploy Office 2010 through Group Policy in Active Directory, using OCT to create a custom install, then launching it with the script on this page…/ff602181.aspx. I have set the AUTO_ACTIVATE property as outlined above, and the custom install works perfectly when run manually. However, when I use the script to launch it, the user is prompted to activate when first running any of the Office components. Any idea how I can have the install auto activate after being launched from a script? (I have already tried pathtoOSPP.vbs /act, without success)