Sunday, October 5, 2014

How-to: Deploying Microsoft Office 2013 using SCCM 2012

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 2013Privacyand 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 isWindows 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.
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.


No comments:

Post a Comment