Deploying Office 2013 SP1 and Office Proofing Tools 2013 SP1 with SCCM 2012 R2

UPDATE: New blog post about Deploying Office 2016 available!

Link: Deploying Office 2016 and Office Proofing Tools Kit 2016 / Office 2016 language packs with SCCM 2012 R2

One of my tasks last month was to make Microsoft Office application packages in SCCM 2012 R2 which should be available in the whole University. The applications in question were Office 2013 SP1 and Office Proofing Tools 2013 SP1. This may sound a bit boring as it’s a very “mainstream” deployment. This was my first thought also, but I ran into a couple of problems I thought I’d share. I started out by reading a couple of basic guides and then customized according to my/our needs. None of the guides were fully working without tweaking however. Here are my steps:

Customizing Office 2013 SP1

  • Got a copy of Office 2013 with Service Pack 1 and extracted the iso. Our version is “Professional Plus” with Volume Licensing.
  • Fired up a command prompt and navigated to the extracted Office directory.
  • From here I ran “setup.exe /admin”  to launch the Office Customization Tool.
  • Customized the OCT settings according to our needs:
    • Setup/Organization Name
    • Setup/Licensing and user interface/Use KMS client key
    • Setup/Licensing and user interface/I accept the terms in the License Agreement, No tick in Competition notice, Tick for Suppress modal and No cancel.
    • Setup/Remove previous installations/Remove the following earlier versions of Microsoft Office Programs/Remove all
    • Setup/Modify Setup Properties:
      • AUTO_ACTIVATE, value 1
      • SETUP_REBOOT, value Never
    • Features/Modify user settings:
    • Features/Set feature installation states:

                    <Configuration Product=”ProPlus”>

                <Display Level=”none” CompletionNotice=”no” SuppressModal=”yes” AcceptEula=”yes” />
                <OptionState Id=”LyncCoreFiles” State=”local” Children=”force” />
                <OptionState Id=”GrooveFiles2″ State=”local” Children=”force” />
                <OptionState Id=”ExcelAddInPowerMapFiles” State=”local” Children=”force” />
                <OptionState Id=”ExcelAddInPowerPivotFiles” State=”local” Children=”force” />


      • With this file edited (and saved) and the .MSP-file from OCT saved in \Office_2013_extracted\updates , I was ready to deploy.


and probably many forgotten ones…


Deploying Office 2013 SP1

The deployment part was quite straight forward after the configuration part was done. I basically followed a (very good) guide from with some minor changes for our environment. Nothing worth mentioning here though.

Remember to install all Office updates after the deployment!



Customizing Office Proofing Tools 2013 SP1

We are using a Proofing Tools “CD” which include all of the proofing tool languages. Proofing Tools doesn’t/can’t change the UI language btw, only check the spelling. With this CD, there’s no need to separately download each proofing tool language. After some googling I stumbled upon which seemed useful. Once again I’ll share my configuration so you don’t have to scratch your own head. First off, there’s NO “setup.exe /admin” on this cd/iso. You have to manually specify the languages (proofing) you need. The file you need to edit is located on the extracted iso, in my case \Office_2013_Proofing_Tools_with_Service_Pack_1\proofkit.ww\config.xml. My file looks like this:

<Configuration Product=”Proofkit”>

    <Display Level=”none” CompletionNotice=”no” SuppressModal=”yes” AcceptEula=”yes” />
    <COMPANYNAME Value=”Abo Akademi” />
    <OptionState Id=”ProofingTools_1053″ State=”local” Children=”force” />
    <OptionState Id=”ProofingTools_1030″ State=”local” Children=”force” />
    <OptionState Id=”ProofingTools_1035″ State=”local” Children=”force” />
    <OptionState Id=”ProofingTools_1036″ State=”local” Children=”force” />
    <OptionState Id=”ProofingTools_1031″ State=”local” Children=”force” />
    <OptionState Id=”ProofingTools_1032″ State=”local” Children=”force” />
    <OptionState Id=”ProofingTools_1040″ State=”local” Children=”force” />
    <OptionState Id=”ProofingTools_1044″ State=”local” Children=”force” />
    <OptionState Id=”ProofingTools_2068″ State=”local” Children=”force” />
    <OptionState Id=”ProofingTools_1045″ State=”local” Children=”force” />
    <OptionState Id=”ProofingTools_1049″ State=”local” Children=”force” />
    <OptionState Id=”ProofingTools_1048″ State=”local” Children=”force” />
    <Setting Id=”SETUP_REBOOT” Value=”Never” />


This bypasses all prompts in the setup process and installs 12 proofing languages. I’m not going to list the languages here (OptionState Id values), as a table is available at: . That’s it for the configuration – now ready for deployment.

Source: plus all the forgotten ones…


Deploying Office Proofing Tools 2013 SP1

Internet is full of articles about deploying Office, but not so much about deploying the Proofing tools iso/CD. Most of the guides about deploying Proofing Tools with SCCM were about installing a specific proofing tool language, which you had to download separately. This method is fully working, but wasn’t what I was looking for. I got some ideas from for example, but this one was also only installing one language. The solution was to deploy using the custom.xml from above. Steps:


  • New Application, fill in the details according to your needs.
  • Deployment Type: MSI (so you get the MSI product code). This will be changed. Select the MSI from \\yoursccmserver\Software\Office_2013_Proofing_Tools_with_Service_Pack_1\proofkit.ww and finish the deployment type guide.
  • The MSI-file itself can’t deploy custom stuff so we need to change the installation to use our custom.xml (Fig 1)


          Fig 1. Remove the “\proofkit.ww” directory from the content location path.

  • Edit “programs” tab. The installation command should now include our custom.xml instead of the MSI-command. The command I used was: setup.exe /config \\sccm2012r2\Software\Office_2013_Proofing_Tools_with_Service_Pack_1\proofkit.ww\config.xml (Fig 2).


          Fig 2. Programs/Installation program

  • I also use a dependency so that Proofing Tools can’t/won’t be installed if Office isn’t detected. On the Dependencies tab, select “Add”. Call the group whatever you want and add Office 2013 SP1 as a dependency (Fig 3).


          Fig 3. Application Dependency.

  • I choose not to “auto install” Office with the proofing tools (Fig 4), as we sometimes just need to install proofing tools without office.


         Fig 4. More Dependency-properties.

  • The rest of the information should be fine. I use install for system, whether or not a user is logged on, hidden.




As a final note, do NOT use spaces in the directory name of proofing tools on the SCCM server. The custom.xml file will NOT be read correctly. I learned this the hard way after reading many office setup logs. (The logs are located in c:\windows\temp on the client during/after installation btw). I used the directory name “Office_2013_Proofing_Tools_with_Service_Pack_1” on our SCCM server.

Happy deploying! 🙂