Deploying Office 2013 with SCCM 2012/R2
I am asked all the time while teaching SCCM classes “how do I deploy …. as an application package?” Until early 2013, that question centered primarily around Office 2010, but with the official release of Office 2013, followed by the standard nine to twelve month wait and see cycle traditionally engaged in by many enterprise IT departments having run its course, I am being asked more and more about how to deploy Office 2013 to the corporate desktop. I have put together a small “ how-to “ for you to use if/when you are ready to try out your deployment skills with SCCM 2012/R2 and Office 2013.
First you will need to prepare the installation media of Office 2013. The only “officially” supported media is the Volume License version, so make sure that you have got the right version of the media. (However, if you do not have VL media, you can still do the deployment and it will work just fine, or at least that is the rumor I have heard … J). You will need to download the Office 2013 Administrative Template files (ADMX/ADML) and Office Customization Tool. What you really need here is the Office Customization Tool. Now, copy all the contents of the media to a shared folder. If you have both the 32-bit and the 64-bit media source files, ensure that you put them into separate folders, as shown below.
Double-click to launch either the 32-bit or 64-bit version, based on whatever package you will want to create.
Select the check-box and then click Continue..
Browse to the location where you have copied the contents of the Office 2013 media, then extract it to the respective folders; 32-bit to the \\Source\Office 2013 Pro Plus\x86 and the 64-bit to the \\Source\Office 2013 Pro Plus\x64.
Once you have extracted it you will notice that three new folders have been created.
Now, go ahead and call setup.exe using the /admin switch.
If this is the first time you are running setup, select the default to create a new setup customization file.
The Office customization wizard appears. You can customize a large variety of settings based on the options available on the various screen of the wizard, as noted in the left-hand column of the screen.
Select the Licensing and user interface item from the navigation menu on the left. Here you will accept the terms in the License Agreement and change the Display level to Basic. Select the check-box beside Suppress modal and No cancel. If you are not using a Key Management Server (KMS) to activate your copy of Office, then alternatively you can enter the Multiple Activation Key (MAK) to activate your copy of Office.
Select the Set feature installation states item from the navigation menu on the left. For example if you only want to install Word, Publisher and Excel without PowerPoint, then you can do so here.
Now you will need to save these settings. Go to File > Save and save the file. The .MSP that is created must be place in the Updates folder where you copied your media contents to.
Now you have to create or import Office as an application from within the ConfigMgr console. You will need to browse to \Software Library\Overview\Application Management\Applications. Here you will right-click on Applications and then select Create Application.
Now you will need to browse to the location where you copied your media contents to. Make sure it is available via a UNC path, and select the proplusww.msi file in the proplus.ww folder; \\SetE-cm\source\Office\x64\proplusr.ww\proplusrww.msi then click Next.
The information about the application is imported for you from the .MSI file, so just click Next.
If you choose to, you can populate the information for administrator comments, manufacturer, software version and so on. At the Installation program text box, delete the existing msiexec /i “proplusrww.msi” /q and replace it with setup.exe. Leave any other information as found there as defaults, then click Next to proceed.
At the Summary page, click Next.
The application is created. Click the Close button.
Now you can see the application that you have just created. There are some settings in there that you will need to change. Click on the Deployment Type tab at the bottom of the screen, then right-click on the MSI Deployment Type and then select Properties.
Go to the Content tab and in the Content location text box, remove proplus.ww or proplusr.ww so it should look something like \\SetE-cm\source\Office\x64\
Go to the Programs tab and then in the Uninstall program text box, remove the existing content and then enter setup.exe /uninstall. Once finished, click OK to close the properties window.
In order to deploy the application you have just created, simply right-click on the application and then select Deploy.
In the General page, click the Browse button to select the collection.
Select the target User Collection for the deployment. You could also deploy to a Device Collection as well, if desired. Click Next at the General page to proceed.
At the Content page, click the Add button and then select the Distribution Point(s) that will be used.
At the Deployment Settings page, click Next to proceed.
At the Scheduling page, click Next.
At the User Experience page, click Next.
At the Alerts page, click Next.
At the Summary page, click Next.
At the Completion page, click Close.
Now we need to take a look at what we see from the client’s perspective. From your Windows client machine, open up your Internet Explorer and then browse to http://<ConfigMgr Server Name>/CMApplicationCatalog/
You should see the application that you have just deployed. Click the Install button, and then when asked if you are sure that you want to install the selected application, click Yes.
Here you can see that the installation has begun.
This is the basic UI you have chosen during the Office Customization Tool wizard. The user can only observe the installation process but cannot interfere with it.
You will need to wait a few minutes while the installation finalizes. Once it is done, SCCM will notify you that the installation has completed and you now have Office 2013 installed.
- Rockin’ the CASB – What you need to know about Cloud Access Security Brokers …
- Cloud Tweaks Blog … What Do You Know About Cloud Security?
- Security Awareness @ ISC2 Security Congress 2015
- Secure the Power of the Cloud … (and get certified while doing it)
- Announcing Exchange Server 2016 Preview!
- VMware Scripting Overview – A quick look under the hood
- Checklist: Use AD FS to implement and manage single sign-on with Server 2012/R2
- Checklist: Setting up a Federation Server (ADFS) for use with Office 365 on Windows Server 2008/R2
- The (ISC)² CISSP Domain Refresh … Are you prepared?
- vSphere 6.0 is on the way !!! …. Are you ready???