Deploy Office 2019 using SCCM [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.
Since updates are cumulative and already included in the latest version of Office 2019 you don’t use Microsoft Updates or WSUS to update Office 2019. Instead you can use Microsoft Endpoint Configuration Manager to help you deploy and manage updates to Office 2019. 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.
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.
There are three files present in the folder.
- configuration-Office365-x64.xml
- configuration-Office365-x86.xml
- setup.exe
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).
<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>
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.
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.
Specify some information about Office 2019 application and click Next.
Add a new deployment type and on General page, select Manually specify the deployment type information. Click Next.
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.
"\\server\share\setup.exe" /configure config.xml
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”.
Adding a detection method is really important here. Add the Office 2019 detection method with following settings.
- 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.10336.20044
Click OK to close detection rule box. Click Next.
Specify the user experience settings for the application. Click Next.
Note that Office 2019 is compatible with Windows 10 OS only. Therefore you have to specify the OS requirements here. Click Next.
On the Completion page click Close. This will close create application wizard.
You 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.
Thank you for that lovely article!
However, l‘m struggling to set the source update product code for having the sccm source updater doing its magic. Our packaging department is giving us a freestyle string like officeproplus2019 en-us instead of a GUID so the CmdLets/GUI won’t accept it.
How are you dealing with the source updater topic? Do you use it at all or does our department give us wrong/bad data?
Dear Prajwal,
Thanks for the help provided, I had been stuck with the detection method error for two months and your article helped me resolved the issue.
Hello Prajwal, pls what is the detection rule for Visio Pro / Project Pro 2019 VL x64 when Office 2019 Pro Plus x64 is already installed ?
Andy, use HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration ProductReleaseIds.
It contains the Release IDs of all Click2Run Office products installed comma separated.
You can see a list of IDs here: https://docs.microsoft.com/en-us/office365/troubleshoot/installation/product-ids-supported-office-deployment-click-to-run
Hello Prajwal Desai, I am using the Office Deployment Tool to get updates for my non-internet connected PCs. When I execute the setup /download config.xml command, the version downloaded to my Office\Data folder is 16.0.10366.20016 which is much older than the version I got on my internet connected of 13121.20262. Do you know why? I tried Microsoft tech support but they could not help me.
Dear Prajwal Desai,
Thanks very much for your posts. Your blog is a favorite for me and my co-workers for answering SCCM questions. We are working on updating our Citrix farm from Office 2016 to Office 2019. While we have our xml files and deployment applications working fine, we are having issues pushing Office 2019 updates using CDN through SCCM. We have our Proxy open and accepting the Microsoft websites, and have created the deployment package, added O365 and Office 2019 in SUP, but when we go to download the .CAB file, it errors out. Any thoughts?
Brian
What errors do you see ?. Are your sure the downloads are allowed via proxy.
The you very much, working well, but i have some little problems:
How can i fix it?
here is my code:
<Configuration>
<Add SourcePath=”\\srvsccm01\d$\Csomagok\Programok\Microsoft\Office2019″ OfficeClientEdition=”64″ Channel=”PerpetualVL2019″>
<Product ID=”ProPlus2019Volume” PIDKEY=”” >
<Language ID=”hu-hu” />
<ExcludeApp ID=”OneDrive” />
</Product>
<Product ID=”ProofingTools”>
<Language ID=”hu-hu” />
</Product>
</Add>
<RemoveMSI All=”True” />
<Display Level=”None” AcceptEULA=”TRUE” />
<Property Name=”AUTOACTIVATE” Value=”1″ />
<Property Name=”PinIconsToTaskbar” Value=”TRUE”/>
<Property Name=”FORCEAPPSHUTDOWN” Value=”TRUE”/>
</Configuration>
Its very nice document but unfortunately I’ve got an error. I want to Install / Upgrade an existing ver. of Office installed in workstations.
” Unmatched exit code (17004) is considered an execution failure. AppEnforce 07/09/2020 3:47:51 PM 7236 (0x1C44)
”
Can you please assist for the solution?
We have our package set to the default log file setting, and we’re having problems. Where do the Office installation log files go when deployed during OSD? I can’t find them. From what I see online, I need to look in %temp%, but none of the user profiles have any log files related to the office installation at that path. I imagine they’re cleaned out at the end of OSD?
If you’re using a configuration file look into setting the Logging Level for each install.
I tried many tutorials including one on this website, but it never worked… on a client computer (in Software Centre) it just gets stuck saying “Waiting to Install” and never installs. I spent entire day trying various things – increasing cache in Configuration Manager, trying different Config files, manually editing it… Eventually, when I almost gave up, I went into Office 365 Deployment Wizard which is found inside my SCCM Current Branch, and even though the process looked suspiciously same, it did actually work.. Interestingly on a client PC I now have both Office 365 and Office 2019 VLK installed at the same time in Programs and Features..
Dear Prajwal
thanks for your great posts.
I did exactly as you guided but unfortunately i faced this error in deployment monitoring :
“Failed to verify the executable file is valid or to construct the associated command line.” error code: 0X87D01106
it would be appreciated if you help.
Regards
Check some threads from the community forums.
thank you. I assume that it is related to Ms project installation . but the point is i didn’t ask for it in my config.xml
Are you sure that the install command is correctly specified ?. What detection method are you using ?.
Hello again
1)my config file is :
–
–
–
–
2)My installation command is:
\\server\Sources\Application Package\Office 2019\setup.exe” /configure config.xml
3) Using sscmadmin account
4) AppEnforce log file :
<![LOG[ Prepared working directory: C:\WINDOWS\ccmcache\r]LOG]!
<![LOG[Invalid command line, quotes not properly closed in the command line]LOG]!
<![LOG[Invalid command line, quotes not properly closed in the command line]LOG]!
<![LOG[The network access account is not defined.]LOG]!
<![LOG[Invalid executable file \\server\Sources\Application]LOG]!
<![LOG[CommenceEnforcement failed with error 0x87d01106.]LOG]!
Have you noticed this “Invalid command line, quotes not properly closed in the command line”.
yes i noticed and checked my config file and other configuration. it would be really appreciated if you guide me which file or config i must change.
Best Regards
how can i re-pin start menu and taskbar items that got removed
I’m unable to download it. I’ve tried my own XML, the sample XML that comes with the tool, your XML, XML generated from the Office XML creation website.
Each time it will download 1.83GB of source files then errors out with error code 0-1007 (0). It suggests checking my internet connection and hard drive capacity. Both are fine.
I’ve tried on my work and home internet connection and on another separate computer at work and the same issue each time. Any ideas? Are you able to currently download it or is Microsoft having an issue?
I’ve been banging my head against the wall all day.
I’m also having this same issue, have you resolved yours?
Hello Prajwal:
I am attempting to deploy Visio and Project 2019 and am encountering some issues. I downloaded the 64 and 32 bit versions of the software without issue. I created install and uninstall xml files, tested them and they worked manually without issue. I began packaging in SCCM current branch and deployed it to a test machine. The software copied to the sccm cache and when the install began, I received the 0x800775E6(-2146994714) error. When checking the AppEnforce log, it shows that it prepared the command line->post install behavior is BasedOnExitCode->Waiting for process 1592 to finish. timeout=60 minutes->Process 1592 terminated with exitcode: 2147972582->Looking for exit code -2146994714 in exit code table…->Unmatched exit code (2147972582) is considered an execution failure. The app enforcement completed and nothing is installed.
Any assistance would be greatly appreciated.
Same issue here. Anyone with insight into this error condition?
Same issue ! How did you guys sorted it out ? Thank you !
This was solved on the Prajwal Community forums.
I don’t see how that link is related.
Bit late to the discussion but I encountered the same error as Joe. Couldn’t really find too many results online but managed to resolve in the end. Pretty much … deleted any existing Office 2019 deployment from the server, re-created a new Configuration.xml file, re-ran the office deployment tool (deep breath) … re-downloaded the Office package via an elevated command prompt then finally, re-created the deployment within SCCM. Worked fine afterwards
Hi Prajwal,
Just curious how are you installing Visio / Project after you initial installed Office. We are using SCCM we have a few scenario’s.
Default during OSD the 32-bit office client will be installed.
At a later time the user can request Visio and/or Project. So he/she will be added to the collection where he/she will get the installation of Project/visio. This application is created with the same version as the originial install. It can happen that the Office version is already updated and thus with installing Visio the result will be that the office version is “downgraded” a little. This is only the case for the build numbers.
For example;
Initial installed version 16.0.11328.20368
During a period of time the Office version is updated to 16.0.11328.20420
The user request Visio and the Visio installation application with version 16.0.11328.20368 will be installed, the result in Control Panel will be that Office ProPlus is ‘downgraded’ again to 16.0.11328.20368.
The Visio installation package has been downloaded and installed with the following XML
So the binaries for version 16.0.11328.20368 are available in de application content and we have not configured the XML to download content from CDN (CDNfallback).
Now we can always update the application with the latest update, but this is much work to do for Office / Visio / Project and also for the 64 bit clients.
What is the best way to accomplish this?
We are now creating one application with multiple deployments with requirements for 32/64 bit, and versions so a user with 1808 office cannot install 1902 visio.
I hope the above is a clear picture, and maybe you can shine your light on this matter.
With kind regards
Stefan
Hi, and what about to update Office 2013, during the instalation proces? I mean offline instalation…. From where/how to download/import updates? This updates have to be .msp file or it can be a .cap file?
Uninstall String: setup.exe /configure SilentUninstallConfig.xml
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
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 my post on that page.
Hi Dana, I have fixed the comment plugin issue.
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 doing wrong?
All and any comments or suggestions appreciated
Did you check appenforce.log file ?.
Hi Prajwal
You never got back to the Uninstall?
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!
Since updates are cumulative and already included in the latest version of Office 2019 on the Office CDN, you don’t use Microsoft Updates or Windows Server Updates Services (WSUS) to update Office 2019. But you can use Microsoft Endpoint Configuration Manager to help you deploy and manage updates to Office 2019, including controlling when and from where updates are applied.
Hey Prajwal,
Thanks for this awesome website!
Do you have a guide for that?
It seems like my MECM infrastructure is not able to update Office 2019 installations. KB3104046 looks like is the one I need to deploy but I am always getting error 0x87d00668.
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.
The location where Office 2019 looks for updates is specified in the configuration.xml file that you use to deploy Office 2019 with the Office Deployment Tool. If you don’t want computers installed with Office 2019 to connect to the Office CDN to get updates, you can configure Office 2019 to get updates from a shared folder from within your internal network. You can also configure update settings for volume licensed versions of Office 2019 by using Group Policy.
Can that GPO be pointing to my SCCM SUP and the updates be pushed via SCCM same as we did in older version of Office products? Any specific GPO that I should be looking for? Thanks again for your time.
How do you configure Office 2019 to get updates from a shared folder from internal network? Where do you download the 2019 Office Updates from and can you automate this?
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!
Yes you can do that.
Has anyone run into the 30088-1021 Error code? Attempting to deploy with SCCM1806.
Hi Mike, where are you seeing this error code ?. Can you create a support thread in the forums and attach screenshot ?.
Use Notepad++ instead of Notepad to edit the XML file.
Notepad messes up the code.
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.
https://www.prajwaldesai.com/sccm-configuration-manager-quiz-questions-part-1/
https://www.prajwaldesai.com/sccm-configuration-manager-quiz-questions-part-3/
Thank you so much. I will check that soon.
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.
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 (0x0020)
Performing detection of app deployment type Office Pro Plus 2019 Test SCCM test only(ScopeId_53BF64D9-F1F5-4EAD-9EDC-A7A04A2B3A22/DeploymentType_d5246753-be0e-4ea0-b20b-a5ac6e7684ac, revision 3) for system. AppEnforce 10/8/2018 2:12:46 PM 32 (0x0020)
+++ Application not discovered. [AppDT Id: ScopeId_53BF64D9-F1F5-4EAD-9EDC-A7A04A2B3A22/DeploymentType_d5246753-be0e-4ea0-b20b-a5ac6e7684ac, Revision: 3] AppEnforce 10/8/2018 2:12:46 PM 32 (0x0020)
App enforcement environment:
Context: Machine
Command line: setup.exe /configure configure.xml
Allow user interaction: No
UI mode: 0
User token: null
Session Id: 1
Content path: C:WINDOWSccmcachem
Working directory: AppEnforce 10/8/2018 2:12:46 PM 32 (0x0020)
Prepared working directory: C:WINDOWSccmcachem AppEnforce 10/8/2018 2:12:46 PM 32 (0x0020)
Prepared command line: “C:WINDOWSccmcachemsetup.exe” /configure configure.xml AppEnforce 10/8/2018 2:12:47 PM 32 (0x0020)
Post install behavior is BasedOnExitCode AppEnforce 10/8/2018 2:12:47 PM 32 (0x0020)
Waiting for process 1660 to finish. Timeout = 120 minutes. AppEnforce 10/8/2018 2:12:47 PM 32 (0x0020)
Process 1660 terminated with exitcode: 2147549183 AppEnforce 10/8/2018 2:12:51 PM 32 (0x0020)
Looking for exit code -2147418113 in exit codes table… AppEnforce 10/8/2018 2:12:51 PM 32 (0x0020)
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.
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
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?
Good question. I am sure about this and I haven’t tested this but i will try this in my lab setup.
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
There won’t be much updates for Office 2019, there shall be only security updates. I am sure the future updates can be still deployed via SCCM. May i know what issues are you facing wrt adding languages ?.
At the moment with application languages where it remains en-US only despite having added French and German too. For the proofing tool it works … but still experimenting 🙂 I’m sure might just be a space too much somewhere.
Redid a brandnew package and now all languages are properly available … now having issue to activate despite having added the KMS key to our KMS host 🙁 (always something).
On one of the computer that has office 2019, try activating manually and let me know what error you see.
Another day another issue 🙂 … Installation works fine now … all languages added as main application language and also proof reading. But how the hell do you remove this product? 🙂 I tried an uninstall command which uninstalled one of the three languages only … checked the full MS deployment doc and could not really find much about it …
Have you installed the Microsoft Office 2019 Volume License Pack on your KMS Host?
https://www.microsoft.com/en-us/download/details.aspx?id=57342
you use /configure and just use the Remove component
https://docs.microsoft.com/en-us/deployoffice/configuration-options-for-the-office-2016-deployment-tool#remove-element
Thank you for your article, but how exactly can we install security updates for Office 2019 using SCCM? There are quite a few guides on getting it installed, but nothing about keeping it up to date.
You can use Microsoft Endpoint Configuration Manager to help you deploy and manage updates to Office 2019, including controlling when and from where updates are applied.
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.
You are correct. But Office 2019 is still not listed under the products yet. I have informed this to the product team and they are working on it.
Thanks for the reply. I hope they get it updated soon. They seem to be dragging their heels on this one. Still waiting for some of my OVS customers to get Office 2019 keys assigned!
This will surely help lot of SCCM admins. Amazing work and keep it up.
Thank you. I appreciate that
Amazing guide. I am going to try this in my lab setup.
Cool.. Let me know how it goes.
Great guide as always Prajwal, Everything installed correctly for me except i am using a MAK Key, but word, excel all show activation required.
Use the same key and test if it activates the product. If the key is correct, the product should be activated based on the configuration file.