Deploy Office 2019 using SCCM [Using Office Deployment Tool]

In this post I will cover the steps to deploy Office 2019 using SCCM. Office 2019 is released along with new version of Office Deployment Tool. The Office 2019 is released for both Windows and Mac OS. Recently I published a post on Office 2019 overview and deployment info.

Please read that post before you plan to deploy Office 2019 using SCCM. Office 2019 uses only click-to-run installation technology. We know about this because Click-to-Run has been the installation technology for most Office products since the release of Office 2013.

The important question is should i deploy Office 2019 or go with Office 365. First of all if you have deployed Office 365 ProPlus to the users in your organization, you don’t need Office 2019. This is because most of the features introduced in Office 2019 are already covered in Office 365 plans.

My preference would be still Office 365 as you get updates frequently. Office 2019 is a software that is available as one time purchase. You can buy it from either online store or through volume license agreement. However you can expect only security updates for Office 2019 in future. Let’s proceed with deploying Office 2019 using Configuration Manager.

Step 1 – Install Office Deployment Tool

Download the office deployment tool from here. Right click the executable and run as administrator. You will now see Microsoft Office 2016 click-to-run administrator tool. Accept the license terms and click Continue.

Deploy Office 2019 using SCCM

Create a new folder such as Office 2019 within sources folder and select the folder. Click OK. The executable extracts setup and configuration files inside the selected folder.

Deploy Office 2019 using SCCM

There are three files present in the folder.

  • configuration-Office365-x64.xml
  • configuration-Office365-x86.xml
  • setup.exe

Deploy Office 2019 using SCCM

Step 2 – Create Configuration File

In the next step create a new text file and rename it as config.xml. Well, you can name it anything but ensure you specify .xml as extension. This file should be in the same folder where the setup and other config files are present.

Here is a sample configuration file that you can use it with office deployment tool. In my case I used the below configuration file. This configuration file downloads Office 2019 32-bit version. In addition the previous Windows Installer versions of Office are removed as part of the installation process.

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).


Deploy Office 2019 using SCCM

Step 3 – Download the Office 2019 installation files

In this step we will download Office 2019 installation files. Run the command prompt as administrator. Change the path to Office 2019 folder. Type the command setup.exe /download config.xml and press enter.

The Office 2019 installation files are downloaded and placed inside Office folder. The approx size of this folder after download is around 2.12 GB.

Deploy Office 2019 using SCCM

Step 4 – Deploy Office 2019 using SCCM

We will now deploy Office 2019 using SCCM. Launch SCCM console and create a new Application. On the General page, select Manually specify the application information. Click Next.

Deploy Office 2019 using SCCM

Specify some information about Office 2019 application and click Next.

Deploy Office 2019 using SCCM

Add a new deployment type and on General page, select Manually specify the deployment type information. Click Next.

Deploy Office 2019 using SCCM

Specify the content location. This is the folder where Office 2019 setup files are present along with setup and config files. Next, specify the installation program as per below format.

Note – I will update the uninstall command at later point of time.

Since I will be deploying Office 2019 to both 32-bit and 64-bit OS, I am going to check the box “Run installation and uninstall program as 32-bit process on 64-bit clients”.
Deploy Office 2019 using SCCM

Adding a detection method is really important here. Add the Office 2019 detection method with following settings.

  • Setting Type – Registry
  • 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.10336.20044

Click OK to close detection rule box. Click Next.

Deploy Office 2019 using SCCM

Specify the user experience settings for the application. Click Next.

Deploy Office 2019 using SCCM

Note that Office 2019 is compatible with Windows 10 OS only. Therefore you have to specify the OS requirements here. Click Next.

Deploy Office 2019 using SCCM

On the Completion page click Close. This will close create application wizard.

Deploy Office 2019 using SCCMYou have now packaged Office 2019 application. Finally deploy the Office 2019 to a device collection.

In my lab setup, i could install Office 2019 without any issues. Open the software center and select Office 2019 app and click Install. Monitor the installation progress by opening AppEnforce.log file.

Deploy Office 2019 using SCCM

You might also like

Leave a Reply

19 Comment threads
27 Thread replies
Most reacted comment
Hottest comment thread
newest oldest most voted

Uninstall String: setup.exe /configure SilentUninstallConfig.xml



We are deploying Office 2019 on SCCM clients that have Office 2010 installed.
The deployment starts, uninstalls Office 2010 but does not install Office 2019.
If we do it manually, it works perfectly.
Has anyone encountered this problem?
Thanks in advance

Dana Simison

Hi Prajwal; I can not reply to your comment to me, I keep getting a page can not be found message. So I am posting a new comment. I tested my deployment on 2 machines, on one machine the appenforce.log showed no warnings or errors. The second machine did show some errors about a network access account not being defined. However, yesterday morning I found your post on deploying Office 2019 with the Office 365 Client Manager. I followed that post and everything worked perfectly so I will make use of that. I did run into one snag so see… Read more »


hi there; Thanks for a great post. Unfortunately it’s not working for me. Following your instructions I downloaded the 64 bit version of Office with no problem. Then I created my config.xml file. At this I tested it manually by going to \\myserver\share\office2019\setup.exe /configure myconfiguration.xml. The manual install worked perfectly. Then I created the SCCM application and deployed it to a test computer. The software was copied to the sccm cache on the test computer but nothing happens after that. Nothing gets installed and then I get the message 0x87D00324(-2016410844). The programs was not detected following installation. What am I… Read more »

Thomas Ehler

Hi Prajwal

You never got back to the Uninstall?

Thomas Ehler

I’ll take the liberty to answer the question myself

setup.exe /configure UninstallProPlus2019Volume.xml

………. UninstallProPlus2019Volume.xml …………..





“Remove All” – Use “FALSE” to only uninstall “product ID”‘s listed



“Remove All” – Use “TRUE” to wipe out all


Hi Thomas,
Please, would you publish your uninstall .xml again, perhaps as .txt, so that it could be shown here? Thanx a lot!


Great guide – all of this works for me without issue. My only concern is future updates for Office 2019. I have read all the info MS posted about the clients connecting to their CDN for updates, but I was hoping to manage updates with WSUS. On my WSUS Server, I only see an an Office 365 Client in the “Products” list. Do you have any guidance on configuring updates?
Many thanks!


You may want to add the following line to the config.xml to force any apps that may be stopping the installation to halt and allow installation.


What line are you adding? I do not see it in your comment?


Hi Prajwal, as always a great guide for all SCCM admins here. It worked perfectly fine. Just a question about updates here. It looks like the Office updates option is enabled by default. How do we go about to disable that and let SCCM deploy updates in future. Your time is much appreciated as always. Thanks.

Eric Miller

Prajwal, I’m actually using your setup.xl but I also have a KMS server which is ready for Office 2019. Do I just remove the PIDKEY= and leave the comment for KMS activation? Thank you!

Mike Dickson

Has anyone run into the 30088-1021 Error code? Attempting to deploy with SCCM1806.


Use Notepad++ instead of Notepad to edit the XML file.
Notepad messes up the code.

Amit Prakash Rai

This comment is not related to this post. I am a big fan of your blog and read it from time to time.

I found below discrepancy in SCCM quiz questions part 1 and part 3:
Question 7 from part 1 and question 11 from part 3 are the same yet the answers for both the questions are different. Please do check it out if you get some time.
Below are the links for the part 1 and part 3 quiz questions.

kheenan halvorson

I am running into an issue, it is definitely downloading without issue but it says

invalid executable file “\shareOffice2019setup.exe”
enforce app failed (0x87d01106)
failed to invoke enforceapp on application handler (0x87d01106)
failed to enforce app, error 0x87d01106

we are running office 2016 pro plus now. So my question i guess is the registry stuff you included in your example not going to make this work.


So if I use my installation package with the flag to remove all previous installed software like follows it works:

If I tell the setup to leave previously installed Visio or Project versions like follows it fails:

Any idea what might be wrong? The installation log is really one of the worst ever … no clear failure message (at least for me). Thanks.

kheenan halvorson

I still havent gotten this to work. It fails when trying to run the executable. here is what the appenforcer log says, ive been stumbling on this for about a week now. Any direction would be greatly appreciated ++++++ App enforcement completed (8 seconds) for App DT “Office Professional Plus 2019 Test I Drive” [ScopeId_53BF64D9-F1F5-4EAD-9EDC-A7A04A2B3A22/DeploymentType_d0b1e7fc-d117-493b-b25f-35666f1725f9], Revision: 2, User SID: ] ++++++ AppEnforce 10/8/2018 1:39:51 PM 5236 (0x1474) +++ Starting Install enforcement for App DT “Office Pro Plus 2019 Test SCCM test only” ApplicationDeliveryType – ScopeId_53BF64D9-F1F5-4EAD-9EDC-A7A04A2B3A22/DeploymentType_d5246753-be0e-4ea0-b20b-a5ac6e7684ac, Revision – 3, ContentPath – C:WINDOWSccmcachem, Execution Context – System AppEnforce 10/8/2018 2:12:46 PM 32… Read more »


I have error -2147418113 and it turned out Skype for Business was running in the system tray, exited out of that and re-ran the SCCM installer and it worked.

Daniel Dodds

What would be the detection method for Project and Visio 2019?


Hi, I use the following so far:
Project – 32-Bit: %programfiles(x86)%Microsoft OfficerootOffice16WINPROJ.EXE
Project – 64-Bit: %ProgramFiles%Microsoft OfficerootOffice16WINPROJ.EXE

Project – 32-Bit: %programfiles(x86)%Microsoft OfficerootOffice16VISIO.EXE
Project – 64-Bit: %ProgramFiles%Microsoft OfficerootOffice16VISIO.EXE

Sandy Wood

Wondering what the effect of installing Office 2019 on an existing Office 365 installation. I’m guessing the Detection Logic will allow the installation based on Version but will Office 2019 uninstall Office 365 to you knowledge?


Hi. Great guide. Was able to set up Office 2019 in my lab. Just wondering how to deploy the updates to this. We clearly will not want Internet Updates but rather update via SCCM if that’s offered. Having some slight issues with adding all languages

Gregg Cooper

According to Microsoft, The Office 365 Management section should allow you to deploy and manage Office 2019. But it does not appear to be updated with this capability yet. Will you cover this method when it is updated? This seems the most logical way to deploy it from what I can see? All my customers are VL, so no Office 365. Therefore never used the 365 management interface.

Viraj P

This will surely help lot of SCCM admins. Amazing work and keep it up.


Amazing guide. I am going to try this in my lab setup.

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. AcceptRead More