Packaging Office 365 for Deployment in System Center Configuration Manager SCCM current branch 1909

Packaging Office 365 for Deployment in System Center Configuration Manager SCCM current branch 1909


Software Library

Application Management

Office 365 Client Management

Click Office 365 Installer


Wizard opens


Enter name for the package and a storage location

Click next


Click Go to the Office Customization Tool


Select architecture (32 or 64)

Select products to deploy




Select Update Channel


Select primary language


Select install options (pin icons to taskbar, logging, shut down running apps)



Select packages to uninstall




Select Automatically accept the EULA

Select Product Key (MAK or KMS)


Select Product Activation type


Under General enter the organization’s name

Click Review


Select Default File Formats


Click Submit


Click Summary


Select NO

Click Next

Click Next at Confirm Settings


Wait for Progress screen to complete

At Completion screen, click Close

***********************************************************************************************************************
NOTE: The wizard does not provide an option for setting the display level. If you desire the            deployment to run silently, navigate to the file share where you saved the deployment files, edit the configuration.xml file

Change the line that reads:

<Display Level="Full" AcceptEULA="TRUE" />

To:

<Display Level="None" AcceptEULA="TRUE" />

*********************************************************************************************************************** 

The Application Package will now be available for distribution and deployment under Application Management - Applications



Unfortunately, the Office Customization Tool will specify the exact same detection method for any office package you create. So that if you create a base package of Office, another for Visio, and another for Project, Visio and Project will fail to install because Config Manager will see them as already installed (even though they are not) due to the detection method being the same.


Setting Type: Registry
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration"

To work around this issue, after packaging Visio, change the detection method to:
File System
Path: %ProgramFiles(x86)%\Microsoft Office\root\Office16
File: Visio.EXE
Version Greater than or equal to 16.0.10827.20181

after packaging Project, change the detection method to:
File System
Path: %ProgramFiles(x86)%\Microsoft Office\root\Office16
File: WinProj.EXE
Version Greater than or equal to 16.0.10827.20181