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.

Download the complete guide here in PDF format or read the the guide here. If I later decide to update this guide, I’ll only update the document. Not this blog post.

Prepare Office 2013 for deployment

Overview

This procedure describes how to prepare Microsoft Office Professional Plus 2013 to be installed unattended. The aim of this procedure is to create and prepare the installation source folder, for use with System Center 2012 Configuration Manager.

This procedure does not cover:

  • Download the Volume License Edition of Microsoft Office 2013 installation files.

Pre-requirements

In order for the operator to perform the steps describes below, the following requirements must be in place:

  • The operator must have access to the volume license edition of Microsoft Office Professional Plus 2013.

Process Steps

1. Copy all content from the Microsoft Office 2013 DVD to a source share like: \\SCCM01\Source$\Applications\Microsoft Office Professional Plus 2013 ENU\DT-MSI_x86\
(We need to create a subfolder for each deployment type).

2. Start the Office Customization Tool (OCT), by running Setup.exe /admin, from the source folder. (The OCT is available only with the volume license editions of Office).

How to: Deploying Microsoft Office 2013 using SCCM 2012

3. If required click OK to the User Account Control (UAC) prompt.

4. Verify that the correct product and version is selected, and click OK.

How to: Deploying Microsoft Office 2013 using SCCM 2012

5. In the Default File Types, pop-up, select the format you wish to use. The default is “Keep Current Settings”. In this example, I’ll select Office Open XML formats, and then click OK.

How to: Deploying Microsoft Office 2013 using SCCM 2012

6. In the Microsoft Office Customization Tool wizard, you can customize almost all available settings, but in this example, I’ll only configure a few of these settings, to make the installation unattended, and to provide a simple user experience to users, when they install Office 2013 from the System Center 2012 Application Catalog.

7. Select Install location and organization name, and fill-in your company name.

How to: Deploying Microsoft Office 2013 using SCCM 2012

8. Select Licensing and user interface, and select “I accept the terms in the License Agreement”. In the Display level, select Basic, and select both Suppress modal, and No cancel.

Note: If you do not plan to use KMS or Active Directory-Based activation, you should also specify the MAK product key on this page.

How to: Deploying Microsoft Office 2013 using SCCM 2012

9. Select Modify Setup properties, and click Add…

10. In the Add/Modify Property Value dialog box add the following information, and click OK:

Name: SETUP_REBOOT

Value: Never

How to: Deploying Microsoft Office 2013 using SCCM 2012

How to: Deploying Microsoft Office 2013 using SCCM 2012

11. To disable the Office 2013 Welcome screen, select Modify user settings, expand Microsoft Office 2013, Privacy and Trust Center. Select Disable Opt-In Wizard on first, and double click on the setting and select Enable.

How to: Deploying Microsoft Office 2013 using SCCM 2012

12. That’s it… Click File and then Save, and then save the MSP file in the Updates folder in the source folder.

How to: Deploying Microsoft Office 2013 using SCCM 2012

13. The source folder is now prepared for unattended installation, and if you run setup.exe, from the source folder, the installation should be 100% silent.

Create/import the Application for Office 2013

Overview

This chapter describes how to create an application in System Center 2012 Configuration Manager.

Pre-requirements

In order for the operator to perform the steps describes below, the following requirements must be in place:

  • The operator must have access to a system running the Configuration Manager Administration Console
  • The operator must be logged in with a user account with permissions to create and deploy applications.

Process Steps

1. In the Configuration Manager Console, navigate to Software Library / Overview / Application Management / Applications.

How to: Deploying Microsoft Office 2013 using SCCM 2012

2. In the ribbon menu, click Create Application.

How to: Deploying Microsoft Office 2013 using SCCM 2012

3. In the Create Application Wizard, verify that automatically detect information is selected and that the Type is Windows Installer (*.msi file), and click Browse…

How to: Deploying Microsoft Office 2013 using SCCM 2012

4. Navigate to the source folder (by using the UNC share path). \\SCCM01\Source$\Applications\Microsoft Office Professional Plus 2013 ENU\DT-MSI_x86\ProPlus.WW\, and select the ProPlusWW.msi file, and click Open.
Note: Microsoft Office Professional Plus 2013, should not be deployed as a native MSI file, but by selecting the MSI file when we create the application, things like deployemt type and detection methods are created automatically.

How to: Deploying Microsoft Office 2013 using SCCM 2012

5. On the General page of the Create Application Wizard page, click Next.

6. Verify that the imported information is correct, and that the import was successful, and click Next.

7. On the General Information page, verify that the Name is displayed like you would prefer to see it in the Console. Fill-in the Manufacturer (Microsoft), and the Software version (2013).

How to: Deploying Microsoft Office 2013 using SCCM 2012

8. In the installation program, delete the default value (msiexec.exe /i “ProPlusWW.msi” /q), and type Setup.exe.

How to: Deploying Microsoft Office 2013 using SCCM 2012

9. Verify that Install behavior is configured to Install for System, and click Next.

10. On the Summary Page, click Next.

11. On the Completion page, verify that the application was imported successful, and click Close.

12. In the Configuration Manager console, select Microsoft Office Professional Plus 2013.

How to: Deploying Microsoft Office 2013 using SCCM 2012

13. Select the Deployment Types tab.

How to: Deploying Microsoft Office 2013 using SCCM 2012

14. Right-click the deployment type Microsoft Office Professional Plus 2013 – Windows Installer (*.msi file), and select Properties.

How to: Deploying Microsoft Office 2013 using SCCM 2012

15. Select the Content tab, and change the content location to \\SCCM01\Source$\Applications\Microsoft Office Professional Plus 2013 ENU\DT-MSI_x86\, by removing the “\proplusww” in the end of the pre-configured location.

How to: Deploying Microsoft Office 2013 using SCCM 2012

16. Select the Programs tab and change the Uninstall program command to Setup.exe /uninstall.

How to: Deploying Microsoft Office 2013 using SCCM 2012

17. Select the Detection Method tab, and verify that a detection method for the MSI Product Code had been created.

How to: Deploying Microsoft Office 2013 using SCCM 2012

18. Select the Requirements tab, and click Add…

Note: You can create lots of requirement rules, but in this example, I’ll provide three common examples on requirement rules, you can use to target the right deployment type for the right system.

19. Create a Requirement rule with the following settings, and click OK.

a. Category = Device

b. Condition = Total physical memory

c. Rule Type = Value

d. Operator = Greater than or equal to

e. Vaule (MB)= 2048

How to: Deploying Microsoft Office 2013 using SCCM 2012

20. Click Add..

21. Create a Requirement rule with the following settings, and click OK.

a. Category = Device

b. Condition = Disk Space

c. Rule Type = Value

d. Select local logical drive = System drive

e. Operator = Greater than or equal to

f. Vaule (MB)= 2000

How to: Deploying Microsoft Office 2013 using SCCM 2012

22. Click Add…

23. Create a Requirement rule with the following settings, and click OK.

a. Category = Device

b. Condition = Operating System

c. Rule Type = Value

d. Operator = One of

Windows 7

Windows 8

How to: Deploying Microsoft Office 2013 using SCCM 2012

24. Click OK.

How to: Deploying Microsoft Office 2013 using SCCM 2012

Deploy Microsoft Office 2013

Overview

This chapter describes how to deploy Microsoft Office Professional Plus 2013 using System Center 2012 Configuration Manager.

Pre-requirements

In order for the operator to perform the steps describes below, the following requirements must be in place:

  • The operator must have access to a system running the Configuration Manager Administration Console
  • The operator must be logged in with a user account with permissions to create and deploy applications.

Process Steps

1. In the Configuration Manager Console, navigate to Software Library / Overview / Application Management / Applications.

2. Select Microsoft Office 2013 Professional Plus 2013.

How to: Deploying Microsoft Office 2013 using SCCM 2012

3. In the ribbon, Select the Home tab, and click Deploy.

How to: Deploying Microsoft Office 2013 using SCCM 2012

4. On the General Page, click Browse… to select the target collection.

How to: Deploying Microsoft Office 2013 using SCCM 2012

5. Select All Users, and click OK.

How to: Deploying Microsoft Office 2013 using SCCM 2012

6. Click Next.

7. On the Content tab, click Add and then Distribution Point.

How to: Deploying Microsoft Office 2013 using SCCM 2012

8. Select the Distribution Point, and click OK.

How to: Deploying Microsoft Office 2013 using SCCM 2012

9. Click Next.

10. Complete the wizard, by Next 6 times and then Close.

End User Experience

Overview

This chapter describes the end user experience when deploying Microsoft Office Professional Plus 2013 using System Center 2012 Configuration Manager.

Pre-requirements

In order for the operator to perform the steps describes below, the following requirements must be in place:

  • The operator must have access to a Windows 7 or Windows 8 client system with the System Center 2012 Configuration Manager Client Agent installed.
  • The Windows Client must be joined to the same Active Directory forest as the Configuration Manager Site Server
  • The operator must be logged in with a domain user account that is a member of the All Users Collection in System Center 2012 Configuration Manager

Process Steps

1. Login to the Windows client, and start Internet Explorer.

Note: If you are using a Windows 8 client, you should start Internet Explorer from the Desktop. Not from the Modern UI Interface.

2. Open http://sccm01/CMApplicationCatalog.

3. Select Microsoft Office Professional Plus 2013, and click Install.

How to: Deploying Microsoft Office 2013 using SCCM 2012

4. On the Application Installation pop-up notification click YES.

How to: Deploying Microsoft Office 2013 using SCCM 2012

5. Verify that the application installation has started, and wait for the Installation to complete.

How to: Deploying Microsoft Office 2013 using SCCM 2012

6. When the software installation is completed, click OK.

How to: Deploying Microsoft Office 2013 using SCCM 2012

7. Start Microsoft Word, to verify that Microsoft Office has been installed successfully, and that the settings configured in the Office Customization Wizard, had been applied successfully.

The latest version of this document can be downloaded here:
http://www.ronnipedersen.com/configmgr-2012-guides/

/Enjoy

+Ronni Pedersen


Comments

  1. 2 question :)

    1) i have Microsoft office 2007 already installed before, but after installing office 2013 the software center requires me to reboot the system, can i prevent this message (i mean i want to deploy the office but run at time after installing no need to restart).

    2) can you guide me to the best practice for software deployments for clients, for example is it better to make it silently 100 & required or available, should it be non silent… etc.
    i know it depends on the organization and the requested software’s but there is a general principles for the best practice where you force the clients to follow your roles.

    & thank you very much

    • Hi Mohammed,
      1. If you add the SETUP_REBOOT=Never to the custom properties (view the first part of the article), you should be just fine.
      2. As you state it really depends on the organization and the requirements, but my experience is that when customers start to use the Application Catalog, they find that users can help them themself alot more if we give them the change, by making applications available to them.
      And the best part is, that we (the Guys in IT) don’t have to spend valuable time adding users or computers to Collections every time someone needs an app.

      • Ronni

        i need a help in this issue, i feel it is easy but for some reason i tried to solve it but no succeed

        i created Application (available not required) for Adobe Pro (the latest version) (with uninstall choice) and i assigned it to a user, the APP showed in the application catalog (and it is working fine installing and running), but also it showed in software center (list).

        the issue:
        i removed the application beginning by deleting deployment( that assigned to the user) then deleting the deployment type then deleting the application (it self) from SCCM (right click & Delete).

        it disappeared from the Application Catalog (that’s good), but it did not disappear from the software center list.

        i tried to find away to do it but no succeed, all the websites talks about uninstalling the application (but i already configured it ), but my issue is that i removed the application (delete it totally) and still stuck in the software center
        is there a way to remove it totally from software center list.

        thank you & regards

  2. Ronni Pedersen
    January 20, 2013 - 11:57

    Hi Moahmmed,

    I think this is by design that the application will remain in the software center as long as the application is installed on the client. The reason is that the user can use the software center to uninstall the application again if it’s no longer required.

    Are you using SCCM 2012 RTM or SP1 ?

  3. i think i am using SCCM 2012 RTM and soon the release of SP1 i will install it, but for CAS it is SP1

    it have gone, but it took too long to go from software center.
    it goes in the next day, and each time i create Application and install and remove,it will be removed totally form software ceneter in the next day.

    it is noisy because each time you make a test you should use many names for the file or you wait for next day for to be removed and retest again.

  4. i have posted but unsure, any way i am using as i think SCCM 2012 RTM

    it have gone but in the next day, and continues like that…!

  5. Why can’t the world have more people like you?

    Thank you. So clear, and it works.

    Excellent

  6. Hi Ronni – great document. Thanks for taking the time to share it

    Couple of question around Office 2013

    1. You place the MSP into the Updates folder. I’ve always put it into the root folder and then called setup.exe /adminfile xxx. I tried putting the .MSP into the x86 folder with the above command but it failed
    2. Do MS now recommend using the X64 subfolder for 64 and same for X86 – previously it was recommended to use the 32-bit flavour even on 64 bit?. Again how does this fit in with the MSP on the root folder i.e. is the msp independent of the O/S type or do you have to have a separate one in each sub-folder?

  7. Hi,

    On the client I get the following error:
    Software Center: the software change returned error code 0x87d00607 (-2016410105)
    Eventviewer: application failed to download content with error code of -2016410105

    the software is located on a server/share that is not the SCCM server.

    regards,
    Rob

  8. Hi Rob

    du you got a Resolution of this Problem? i have the same error message.

    many thanks for your feedback

  9. Brian Hampson
    July 22, 2013 - 17:40

    Nice clear and concise article with good pictures!

    I know this post is old now, and it’s possible you may not see this, but…. I have a question.. what if I want to do to different installs with different customizations? Do I need to copy the entire source tree and drop in a new MSP? Seems a bit painful.

  10. Hey Ronnie, Great Article
    my questions are on the end user side, when they got the program installed (in my case lync 2013) they get asked if they want to use recommended settings or not, in regards to updates, and they get prompted to activate the program by phone or internet.
    I added the Product key with the OCT, is there a way to make the programs automatically be activated and not prompt for the recommended settings?

    • Hi Jesper,

      If you use a KMS Server for activation, you don’t need to manually activate office/lync.

  11. MARCELO FORNAZARI
    September 6, 2013 - 15:52

    Hello Ronni, okay?

    Excellent article and quality. Really good. I would like to ask you whether it is possible automatizarmos this facility so that the user does not interact any longer and get automatically installed on his machine? What options should I check?

    Thanks and a hug,
    Marcelo

    • Hi Marcelo,

      Just deploy the application as required to the user (or device) and it should be installed automaticlly.

  12. Is anyone else having issues with upgrading from Office 2010? My MSP is set to remove all old office applications but it is not properly uninstalling Outlook 2010. I’ve tried having SCCM run a bat that taskkills all office apps before running setup.exe, but 90% of our upgrade deployments have experienced this. did not have this problem going from 2007 to 2010.

    • Carrie,
      I had these problems as well. After testing with this script the install works much better.

      taskkill.exe /f /im winword.exe
      taskkill.exe /f /im excel.exe
      taskkill.exe /f /im msaccess.exe
      taskkill.exe /f /im outlook.exe
      taskkill.exe /f /im officelivesignin.exe
      taskkill.exe /f /im infopath.exe
      taskkill.exe /f /im onenote.exe
      taskkill.exe /f /im onenotem.exe
      taskkill.exe /f /im powerpnt.exe
      taskkill.exe /f /im mspub.exe
      taskkill.exe /f /im mspscan.exe
      taskkill.exe /f /im mspview.exe
      taskkill.exe /f /im ois.exe
      Taskkill.exe /IM osaui.exe /F
      taskkill.exe /f /im communicator.exe /t
      taskkill.exe /f /im ucmapi.exe /t

      Wmic product where “name like ‘%%Microsoft%%Lync%%2010%%'” call uninstall /nointeractive
      msiexec /qn /x {90120000-0020-0409-0000-0000000FF1CE}

      Jason Oliphant

  13. Ronni,
    Thanks for the great common sense article.
    Can you tell me how to tell SCCM to run from DP instead of downloading this huge content to each machine in corp.?
    I know of the setting for slow networks to run from DP but what if I want it to run from DP to ALL machines regardless of network speed?
    Thnks in Advance. If I posted twice sorry.

  14. Hi Ronni!
    Fine instruction for Office 2013 deploy. I have one question.
    We deployed Office 2013 without MS-Access. Some of our colleague needs MS-Access. What is the best way to deploy only Access on an existing Office2013?
    Thank you for your Info!
    BR Mercy

    • Ronni Pedersen
      February 1, 2014 - 12:24

      You need to make a custom XML file that will add access to the existing installation.
      You also need to add a check for access to your detection method

  15. Just came across this article while looking into setting up Office 2013 as an application rather than a package.
    Have you tried leaving the detected uninstall program (msiexec /x blah /q)? As that matches the uninstall string in the registry (minus the /q), so presume it should work…

    Also, does the ‘technology’ being set to Windows Installer when using this method cause any problems?

    Cheers
    Jay

    • Ronni Pedersen
      February 1, 2014 - 12:13

      No I dont use the msi as the uninstall command, and I don’t think it’s supported. But you can test if you like.
      The main reason for me to use the Windows Installer deployment type insted of the script deployment type, is to make the wizard simpler, and it will create detection methods for you.
      Anthoner thing is that MSI deployment types at default supported by the MDT UDI wizard for detection.

  16. Great guide worked like a charm.

    I had no idea you could just type things like setup.exe into the Installation Program, as it only lets you search for MSIs… this is awesome.

  17. Great article, thank you very much for creating it. It worked first time out with no problems at all. I used your article to setup a deployment of Office 2013 32 bit. However if I try to deploy to a computer that has a 64 bit version of Office on it then it fail. Any suggestions as to how to handle this?

    Thanks again. All and any comments are greatly appreciated.
    D

    • Ronni Pedersen
      March 9, 2014 - 08:14

      I have not tested that specific scenario.
      But I would suggest that you create a new application for the 64-bit version of office, and then use the uninstall deployment before installing the 32-bit version (I dont think they can co-exist og the same machine).

      • Hi Ronni;

        Thanks for your reply, I’m pretty sure they can’t co-exist either nor do I want them to. However I’ve yet to figure out a way to get the old Office uninstalled and then install the new office.

        I’ve tried a Task Sequence that has a command line to uninstall the Office and then an application install but this keeps failing. The command line I’m using works from a command prompt.

        Thanks again

  18. How would we go about installing just Lync2013 on a computer which is running Office2010?
    Then later how would we update Office2010 to Office2013? From memory you can’t re-run the “setup.exe /adminfile ***.msp” to modify an already installed instance of Office.

    Cheers

  19. How do you deal with multiple .MSP files for different features of Office. You can create different deployment types in SCCM but how can you force it to the one you want – particularly during OSD build?. With a package/program you could “hard-code” to select the MSP file you want but not sure how an Application/deployment type can cope??

    • Deployment types are really meant to be used for things like managing different operating systems or other basic hardware/software based configurations. You can’t just pick a specific deployment type when deploying an application like you do a package. (kinda really annoying sometimes I must admit, but it has other benefits)

      So I would create separate applications for the individual .msp file’s you want to use for maximum flexibility in OSD. In situations like this I create a folder that contains all of these separate applications that relate to one common sort of ‘package’ just for administrative ease.

Leave a Reply

Your email address will not be published / Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">