This post covers the Microsoft Office 2019 deployment using ConfigMgr. We will deploy Office 2019 (on-premise) version using Configuration Manager to our endpoints.
The steps covered in this post are bit similar to the ones covered in deploying Office 2019 ODT using SCCM. However with Office 2019 on-premise version, you already have the installation files with you. So there is no need to download them separately.
Before I cover on Office 2019 deployment using ConfigMgr, let us know the differences between Microsoft 365 and Office 2019.
Table of Contents
Difference between Microsoft 365 and Office 2019
There are few differences between Microsoft 365 and Office 2019, here are some details.
- Office 2019 (on-prem version) only gets security updates and no new features. Where as with Microsoft 365, you’ll get monthly quality updates.
- Office 2019 is sold as a one-time purchase, which means you pay and get Office apps for one computer. However, there are no upgrade options. This means if you plan to upgrade to the next major release, you’ll have to buy it at full price.
- Another difference is the pricing of these products. You can view the pricing page for more details.
Create Office 2019 Configuration.xml File
I have got Office 2019 on-premise version which has got all the data downloaded. What we need is a configuration.xml file that defines the entire setup.
Create a new text document and rename it as Config.xml. Open it with a notepad and enter the below details. I will be placing this file in Office 2019 folder.
Make sure you enter the correct source path. If you wish to add additional languages, you may do that by specifying under Language ID.
The PIDKEY is the product key for MAK activation. You don’t need to use PIDKEY if you’re activating Office 2019 with Key Management Service (KMS).
<Configuration> <Add SourcePath="\\corpsccm\Sources\Applications\Office 2019" OfficeClientEdition="32" Channel="PerpetualVL2019"> <Product ID="ProPlus2019Volume" PIDKEY="" > <Language ID="en-us" /> </Product> <Product ID="ProofingTools"> <Language ID="en-us" /> </Product> </Add> <RemoveMSI All="True" /> <Display Level="None" AcceptEULA="TRUE" /> <Property Name="AUTOACTIVATE" Value="1" /> </Configuration>
Create Office 2019 Application in Configuration Manager
We will now create Office 2019 as new application in Configuration Manager. In the SCCM console, go to Software Library\Application Management\Applications.
Right click Applications and click Create Application. On the General page, select Manually specify application information. Click Next.
Specify the Microsoft Office 2019 details. Click Next.
Add a new deployment type. Select Manually specify the deployment type information. Click Next.
Specify the content location. This location contains the Office 2019 setup files.
Specify the installation program as “setup.exe” /configure config.xml.
In this step we add a Microsoft Office 2019 detection rule. Enter the below configuration and click OK.
- Setting Type – Registry
- Hive – HKEY_LOCAL_MACHINE
- Key – SOFTWARE\Microsoft\Office\ClickToRun\Configuration
- Value – VersionToReport
- Enable “This registry key is associated with a 32-bit application on 64-bit systems”
- Data Type – Version
- Select “This registry setting must satisfy following rule to indicate the presence of this application”
- Operator – Greater than or equal to
- Value – 16.0.10730.20102
On the User Experience window, specify the settings and click Next.
You may specify the install requirements. Click Next.
Click Next on remaining pages and finally on Completion windows, click Close.
Office 2019 Deployment Using ConfigMgr
Now that we have packaged the office 2019 application in ConfigMgr, it’s time to deploy the app to Windows 10 devices.
First of all, distribute the Office 2019 on-premises application to distributions points. Once the content is ready with DP, right click the Office 2019 application and click Deploy. You may either deploy to a user collection or a device collection.
Login to one of the client machine and launch Software Center. Select Microsoft Office Professional Plus 2019 and click Install.
Using CMTrace tool, open the AppEnforce.log file to monitor Office installation process. The exit code 0 means the application installed successfully.
Prepared command line: "C:\Windows\ccmcache\6\Setup.exe" /configure config.xml Executing Command line: "C:\Windows\ccmcache\6\Setup.exe" /configure config.xml Working directory C:\Windows\ccmcache\6 AppEnforce Post install behavior is BasedOnExitCode AppEnforce Waiting for process 9600 to finish. Timeout = 120 minutes. AppEnforce Process 9600 terminated with exitcode: 0 Looking for exit code 0 in exit codes table... Matched exit code 0 to a Success entry in exit codes table
This completes the Office 2019 deployment using ConfigMgr and I hope this post helps.