How-to: Deploying Microsoft Office 2013 using SCCM 2012

This Step-by-step guide describes how to prepare and add Microsoft Office 2013 Professional Plus to the Application library of System Center 2012 Configuration Manager (SCCM), by using the designated functions for doing this in the Configuration Manager Console interface.This g

4.8 Star
62,438 times
Add to favorites
System Center
E-mail Twitter Digg Facebook
  • still prompted the users to reboot
    2 Posts | Last post January 23, 2015
    • i tested this and followed your guide to the letter. when the user installs the software, after it is done the user gets a message telling them they need to reboot before they could use the software. also.... not all office 2010 professional plus is removed after its all done. i still see lonks to it in add/remove programs
    • Hi Menz01,
      I would recommend that you create an uninstall job for the Office 2010, and then use the built-in superseded feature in SCCM to make sure that the Office 2010 gets uninstalled before you install the newer version.
  • Office 2013 Activation
    3 Posts | Last post June 24, 2014
    • Is there a way to remove the product activation wizard from running the first time an Office 2013 application is opened? I followed the instructions to create a custom MSP file as per your instructions and users are still asked to activate office 2013. 
      Thank you. 
    • Never mind I seem to have forgotten to add the AUTO_ACTIVATE = 1 property to my MSP which I had done in my previous Office 2010 install. 
    • I'm glad you found the solution AND that your shared it here :-)
  • Uninstall 2010 first?
    2 Posts | Last post June 24, 2014
    • We have 2013 packaged up to install but our machines currently have Office 2010 and Lync 2010 installed.  Is there an easy way to combine these so if they go to the Software Center and choose to install office 2013, that it will first uninstall Office 2010 and Lync 2010 and then do the Office 2013 install?
      I'm brand new to SCCM 2012.
    • The function you're looking for is supersede. In SCCM 2012 you can supersede an old application with a new version and require that the old version gets removed first.
      But you can also make Office 2013 uninstall 2010 first (that's the default behavior)
  • Strange Task Sequence Issues
    2 Posts | Last post May 19, 2014
    • Hello,
      We used your build process and have a good working Office 2013 install.  When we run the application as a one-off install, it will install in 20 min and finish as it should..However, when we run the same application as a variable in the OSD task sequence, the system will take about 5 hours to install it, including about 3-4 hours where the system seemingly stops as there is no disk activity, and nothing running in the task manager (setup.exe) on the machine being imaged / setup.  Eventually, it will run and install fine...
      We have talked with MS abotu this and they really have no idea what is going on, so figured I give you a crack..
    • I know this might not be the answer you want to hear, but without going into further details, I normally don't recommend using Application in OSD Task Sequences (unless I really have to).
      My advice it to create a simple Package that will install Office as part of your OSD Task Sequence.
  • prompt to close Office apps
    2 Posts | Last post May 19, 2014
    • is there a way to have the installer prompt users, then automatically close office apps for the install/upgrade?
    • I would recommend that you take a look a the "PowerShell App Deployment Toolkit".
      This Tool can help you with that.
      More information:
  • says Installing forever
    7 Posts | Last post February 04, 2014
    • Hello Ronni,
      thanks for tutorial, I follow it, and pushed it via sccm2012sp1, and it does push to my test machine, but it just keep saying installing for two hours and still nothing.
      I ran the command setup.exe /adminfile 2013Mak.MSP
      am I doing something wrong?
    • It can be many things, but it's most likely your msp file that is not 100% unattended.
      You dont need to specify the msp file in the command. Just put the file in the updates folder.
      Try to execute setup.exe outside SCCM. If it's not 100% unattended it wont work inside SCCM.
      Hope it helps....
    • Hey Ronni, ok so I copied the msp file to the updates file, and changed the sccm command to just run setup.exe..  It runs as if its installing manually and prompts user to choose options.
      I Tested, by going to the source folder where I copied office 2013, and I run setup, and it does run the msp. What do you think could be wrong?
    • nvm, I rebooted the machine, and try to run it, and now it says installing. Lets see if it gets stuck at installing or actually finishes the install.
    • Ok, it didn't work. It keep saying installing until it times out after 2 hours. I run setup manually, and it does install fine with the MSP file. Which log file I should be looking for to troubleshoot?
    • so I switched the commandline from setup.exe to 2013Mak.MSP, and that installed right away with no problems. going to test some more.
    • Try putting your 2013Mak.msp file in the "updates" folder of the root installation directory.  By default, Office will install all .msp files that are in that folder when setup.exe is run.
      My silent install is all configured from a "config.msp" in my updates folder, and it runs perfectly fine.
  • Do you think you may want to point out this is NOT for Office 365?
    2 Posts | Last post January 14, 2014
    • I went through a pretty painful process of learning to deploy Office 2013, and everyone in the entire Microsoft Company kept trying to refer to this guide. 
      Well... this does NOT work if you have Office Subscription Licenses.. 
      If you have Subscription licensing, all you need to do is obtain the actual Iso files from the installation CD and then use the xml file along with The Commandline used in Task Sequence and in Packages : "setup.exe" /config "updates\configuration.xml" - You will also need to update your configuration.xml file according to your Path of your ISO source files. 
      It took nearly a month to figure that out, but well worth it as i have over 500 Employees in our company. 
    • Hi Chis,
      Thanks for your feedback..
      I assume that "Office Subscription Licenses" is equal "Office 365".
      Yes. This guide is not for Office 365, but I'm working on a guide for Office 365 right now.
  • Deploying MS Project 2013 STd
    2 Posts | Last post January 14, 2014
    • Ronnie, trying to deploy MS Project 2013 Std using the same steps.
      All installations fail due to a "time-out"? ANy suggestions?
    • Can you install Project 100% silent outside of SCCM?
      It sound like the installtion might prompt you for some kind of input in the background.
  • And also.... 365 Subscription Licensing...
    2 Posts | Last post January 14, 2014
    • 365 Subscription Licensing Does work with the Office 2013 install. Microsoft for whatever reason wants System Administrators to individually install a Click to Run file on every PC. That's insane and a complete waist of time, resources, and bandwidth. 
      When you complete the install it will tell you that the license has expired. The Fix for this is .... Running the following via command line:
      C:\Program Files\Microsoft Office\Office15\cscript ospp.vbs /act
      Alternative to running the command you can also repair the installation, but again MUCH FASTER than Click-to-run.. it's AWFUL. Not to mention if you lose your subscription authentication from the Client PC. You can't repair the installation at all because it's running from Microsoft's servers. 
      Just thought i would give this info to anyone who's trying to deploy Microsoft Office 2013 via System Center Configuration Manager.
    • Hi Chris,
      Office 365 Professional Plus can be deployed just fine using SCCM 2012.
      However this guide is not for Office 365 :-)
      I do plan to publish a new guide for Office 365 very soon (if time permits) 
  • Office 2013 Features & SCCM 2012
    2 Posts | Last post August 08, 2013
    • Hello Ronni,
      first of all, thank you for your useful guide.
      Then I'm writing to ask you for some questions/suggestions regarding Office 2013 Deployment with SCCM 2012.
      The idea is to create a Default/Basic Office 2013 MSP file (placed under "updates" folder), with all Features excluded by installation – Word, Excel, etc. ... – with the exception of Office Shared Components and Office Tools; then manage Features installation/removal (Word, Excel, PowerPoint, Lync, etc. ...) with xml configuration files.
      Microsoft Lync 2013
      Installation program: setup.exe /config "MyCustomizations\Lync2013-Install.xml"
      Uninstall program: setup.exe /config "MyCustomizations\Lync2013-Uninstall.xml"
      Microsoft Office 2013 (Word, Excel, PowerPoint)
      Installation program: setup.exe /config "MyCustomizations\Office2013-Install.xml"
      Uninstall program: setup.exe /config "MyCustomizations\Office2013-Uninstall.xml"
      The question is this: Does it exist a sort of "Feature Product Code" I can refer to (if exists) for "Detection Method" ? Or should I use a different method (e.g. Registry Keys) ? Could you give me some suggestions based on your experience ?
      I hope to be clear.
      Thank you a lot,
      Luca Fabbri
    • I don't have a good answer to you question, but I think the easiest way to check for a specific feature, would be to just check if the *.exe exits (excel.exe, outlook.exe etc.).
      But you'll have to test it :-)
11 - 20 of 20 Items