Deploy Office 2019 using SCCM through OSD


Hi All

Mainly an intune guy but have been asked to work with MECM/SCCM recently and unsure of how to do this.

As part of a new Windows 10 build, I am creating for a customer I need to also factor in some applications to be installed at build including Office 2019 and other ‘core’ apps.

I am assuming I need to either create a new application. What is the Office 365 client management feature which is found in software library, is this purely just to monitor office installs? I assume this isnt for Office 2019 though?

In terms of other applications, I have been provided applications which are in an exe format rather than msi, I am aware msi is a simpler approach but is there a way I can create packages using exes or do I need to covert these to msi for them to be used in MECM?

My plan is to create a OSD task sequence which will include all the applications to be installed at build. Would this be the right approach is there a better way? All applications need to be installed on all devices.

Sorry about some of the basic questions, this is probably easy stuff for an experienced member but for a newbie its a bit worrying!





Answers ( 8 )


    Hi Jitesh

    Which logs would you like me to share?



    Yes I can confirm the application installs fine through software center.

    I have included the application to be installed during the build task sequence but it fails when added in there with that exit code that I mentioned earlier.

    I am having the issue at the customers site, when I there on Monday I will post the logs many thanks

  1. Hello, You can check the step by step process in below guide and update if any issues!


    • After creating application you can inside Task Sequence steps!

      To learn about O365 Client Management feature! follow the below guide.



      Hi Jitesh Kumar

      So I attempted to follow this article but am finding that Office doesnt deploy as part of the OSD task sequence that has been created.

      I have also used attempt but this operates slightly differently as its using 32-bit rather than 64-bit.

      If anyone has attempted these steps in either one of these articles and ran into problems, it be good to hear from you…Likewise if you found it works I would be interested in hearing that also.


      • How are you attempting for deploy through Task Sequence ? Did you tried to install manually ? using setup.exe /Configure “Configuration.xml”

        If you able to create application package with your requirement then you add the step Install Application > Add your Office package in Task Sequence!

        All things you can customize either Its architecture (32 or 64 bit) or apps behavior using Here you can create new configuration as well as add your own previously created XML file and do further changes.

        First try to install manually with all required files! What challenges you facing please add details.

        Best answer

          Hi Jitesh

          Sorry for the delay in response.

          Yes I can confirm I deployed using the switch /configure nameofxml.xml and running manually on a client itself works fine. It installs silently without issue.

          I also set the application to deploy post OSD (using software centre) build and can confirm this also works by making it a required app but for some reason during build process on unknown machines it doesnt work. All other applications install fine though.

          When monitoring the task sequence I do see it fails with an error/exit code of 16389. When troubleshooting this error and when deploying through software centre, it failed and it was because the client cache size was too small, increasing this globally fixed that problem and it deploys fine that way just not through OSD Task sequence method. I can confirm that Office 2019 is listed as an application to install as part of the task sequence.

          Any help on this would be most appreciated.


          • Is the same Application package working via Software Center ? Just try to deploy the O365 package using custom Task Sequence in Imaged PC. Record your observation.

            Share the logs here – by hiding sensitive info! The error code 16389 is generic.

Leave an answer

Sorry, you do not have permission to answer to this question .