Microsoft SCCM 2012: Office Professional Plus 2013 SP1 (32-bit) Application

This post will focus on creating a package in SCCM for Microsoft Office Professional Plus 2013 SP1 (32-bit).  This package will uninstall previous 32bit Office instances.

Please note that the 32bit Office version will not uninstall previous 64bit instances.  If you have a mixed 32bit/64bit office environment you will need to setup other programs or packages to handle the uninstall of 64bit office.

Visio and Project can be packaged in a similar manner.  If you have a Visio/Project source media that is 32 & 64 bit make sure you choose the setup.exe located inside of the x86 or x64 folder depending on which version of the application you are publishing.

Note:  After installing Office 2013 with Service Pack 1 from the Volume Licensing Service Center (VLSC) with a customized MSP file using the Office Customization Tool (OCT), Lync and OneDrive for Business are not installed.

Please reference the following post if you run into this issue:
http://blogs.technet.com/b/odsupport/archive/2014/03/21/lync-2013-and-onedrive-for-business-are-not-installed-when-installing-office-2013-with-service-pack-1.aspx

To resolve the issue download the updated OCT from here (choose the version that matches your office installation):
http://www.microsoft.com/en-us/download/details.aspx?id=35554

Run the .exe to extract the files to a temporary location.  Once extracted grab the admin folder and copy it over your existing Office 2013 SP1 source admin folder.

Creating an Office Customization .msp file

In order to deploy office silently we will need to create an Office customization file.  This will include out product key as well as many other customizations.

First we need to go to the source where you Office install files are located and launch setup with the following command in order to start the Microsoft Office Customization Tool:

setup.exe /admin

Select Create a new Setup customization file for the following product.

Next we make any Office customizations that we would like to be applied to your Office install.  Following are the customizations I generally make to create a .msp that when applied will perform an install that requires no user interaction (progress bar only) as well as remove some of the initial popups users are prompted with.  In this case the .msp is for a MAK product key.

• Setup
• Installation and organization name
• Organization name: = your organization
• Licensing and user interface
• Select Enter another product key
• Product key: = xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
• Check I accept the terms in the License Agreement
• Display level: = Basic
• Check Suppress modal
• Check No cancel
• Modify Setup properties (Add these properties in)
• AUTO_ACTIVATE = 1 (Activates Office)
• SETUP_REBOOT = Never (Suppresses Reboot)
• Features
• Modify user settings
• Microsoft Office 2013
• Privacy
• Trust Center
• Disable Opt-in Wizard on first run = Enabled
• FirstRun
• Disable First Run Movie = Enabled
• Set feature installation states (Run from My Computer for all components)

Once you have made all of the changes that you would like to customize your Office installation select File, Save As.  Save the file in the Office\updates folder as customizations.msp.

Creating a SCCM Office 2013 Professional Plus 2013 (32-bit) Application

When creating an application for Office you will first point the application the proplusww.msi, but Office doesn't allow you to install an application directly from that MSI.  You are required to install Office by launching setup.exe.  You will see in the following steps that we will initially point it to the proplusww.msi, then go back in and e

• In the SCCM Console go to Software Library, Application Management, Applications, Create Application.
• General section. Select Manually specify the application information.  Next.
• General Information
• Name = Microsoft Office 2013 Professional Plus 2013 SP1 (32-bit)
• Administrator comments = Enter your admin comments here
• Publisher = Microsoft
• Software version = 2013 SP1
• Check Allow this application to be installed from the Install Application task sequence action without being deployed
• Next
• Application Catalog
• Icon.  Browse to the Office Setup.exe and select the Office icon from the list.
• Check Display as a featured app and highlight in the company portal
• Next
• Deployment Types
• Add
• General section. Select Manualy specify the deployment type information. Next.
• General Information
• Name = Microsoft Office 2013 Professional Plus 2013 SP1 (32-bit)
• Administrator comment = Enter your admin comments here
• Languages = English
• Next
• Content
• Content location = location of your source Office file
• Installation program = setup.exe
• Uninstall program = setup.exe /uninstall
• Next
• Detection Method
• Add Clause
• Setting Type = Windows Installer
• Product code = Browse to the proplusww.msi located in the proplus.ww folder of your Office source media
• Ok
• Next
• User Experience
• Installation behavior = Install for system
• Logon requirement = Whether or not a user is logged on
• Installation program visibility = Normal
• Next
• Requirements
• Free Disk Space of any local drive >=  3072 MB
• Operating System = Window 7 / Windows 8 / Windows 8.1 / Windows Server 2008 R2 (64-bit) / Windows Server 2012 (64-bit)
• Total physical memory >= 1024 MB
• CPU >= 1000 MHz
• Next
• Dependencies
• Next
• Summary, Next.
• Completion, Close.
• Next
• Summary, Next.
• Completion, Close.

Now right click on your application and distribute content.  Once the content has been distributed you can now deploy the application to collections.