- #CONFIGURATION FILE FOR OFFICE 2019 STANDARD INSTALL#
- #CONFIGURATION FILE FOR OFFICE 2019 STANDARD UPDATE#
- #CONFIGURATION FILE FOR OFFICE 2019 STANDARD UPGRADE#
- #CONFIGURATION FILE FOR OFFICE 2019 STANDARD WINDOWS 10#
- #CONFIGURATION FILE FOR OFFICE 2019 STANDARD SOFTWARE#
The package has been distributed to the 3 distribution points.įrom now on, within my task sequences, I created six tasks using the same package and specified in each one which program has to be run.
#CONFIGURATION FILE FOR OFFICE 2019 STANDARD INSTALL#
I named each program accordingly to get an idea of what they install and on which site they have to be installed. In Mecm console, I created a package using that source folder and got six programs in the same package with almost the same command line “setup.exe /configure x.xml” where x.xml is obviously replaced with A.xml, B.xml, etc. Numerous other settings can be set within the same xml (be aware that it can take some time to review all of them).ģrd – I created a source folder containing only 7 files : setup.exe and the 6 xml files (say A.xml, B.xml, etc.) which weigh only 5.10 Mo in total, setup.exe being 5.04 by itself. On each site, I set an automatic task on a server to run a batch script (containing among others “setup.exe /download file.xml”) each Wednesday at 1 AM local time to download the sources from Microsoft in a shared folder in which computers have read only rights.Ģnd – Using Apps Admin Center Microsoft 365 once again, I generated 6 xml files in which I specified where the clients can find the sources (the local shared folders used above), where they can find the updates (same local shared folders) and what kind of components they have to install (with or without Outlook/Access). Then via this site (Apps Admin Center Microsoft 365), I generated an unique xml file to specify which version I wanted to download (32 or 64 bits, latest build or a specific one, etc.).
#CONFIGURATION FILE FOR OFFICE 2019 STANDARD UPDATE#
That bummed me big time…Ģ – manage the two different types of installation on each site, update the clients, and lastlyġst – I downloaded the setup.exe via the MVLS center. This has been going on as such since Office 2003, and went through Office 2010, 2013, 2016 and now 2019 (only 2007 was skipped).Ĭame the latest version, Microsoft decided to “spice up” things regarding Office 2019 : I could no longer get an iso file to install and Wsus would not download updates. In the school I work for, we have 3 sites with 2 types of MS Office installations : offices (with Outook and without Access) and classrooms (with Access and without Outlook). Hello and thank you for all the work, testing and sharing you do on this website that saved me some headaches a few times. Matched exit code 0 to a Success entry in exit codes table Looking for exit code 0 in exit codes table. Post install behavior is BasedOnExitCode AppEnforce Working directory C:\Windows\ccmcache\6 AppEnforce Prepared command line: "C:\Windows\ccmcache\6\Setup.exe" /configure config.xmlĮxecuting Command line: "C:\Windows\ccmcache\6\Setup.exe" /configure config.xml
The exit code 0 means the application installed successfully. Using CMTrace tool, open the AppEnforce.log file to monitor Office installation process. Select Microsoft Office Professional Plus 2019 and click Install.
#CONFIGURATION FILE FOR OFFICE 2019 STANDARD SOFTWARE#
Login to one of the client machine and launch Software Center. You may either deploy to a user collection or a device collection. Once the content is ready with DP, right click the Office 2019 application and click Deploy.
#CONFIGURATION FILE FOR OFFICE 2019 STANDARD WINDOWS 10#
Now that we have packaged the office 2019 application in ConfigMgr, it’s time to deploy the app to Windows 10 devices.įirst of all, distribute the Office 2019 on-premises application to distributions points.
What we need is a configuration.xml file that defines the entire setup.Ĭreate Office 2019 Application in Configuration Manager Office 2019 Deployment Using ConfigMgr I have got Office 2019 on-premise version which has got all the data downloaded. You can view the pricing page for more details.Ĭreate Office 2019 Configuration.xml File
#CONFIGURATION FILE FOR OFFICE 2019 STANDARD UPGRADE#
This means if you plan to upgrade to the next major release, you’ll have to buy it at full price.