Ignore the latter, you won’t need them if you follow the next step. This will result in one 32-bit executable, setup.exe (the actual ODT, ~5MB), and several sample XML configuration files. Step 1: Download the latest Office Deployment Tool ( ODT) self-extracting archive from here, then run the downloaded officedeploymenttool_xxxxx-xxxxx.exe to extract its contents to the location of your choice. “Click-to-Run”, whatever its internal details and its claimed benefits over MSI in terms of speed and maintainability, is a “traditional” installation technology that places the program’s files and shortcuts in central locations accessible to all users.

NET abomination that performs a private runtime “installation” of an app to a location under the launching user’s %LocalAppData% before execution starts. *** Note: Don’t confuse “ Click-to-Run” with “ ClickOnce”, the. You could drive yourself insane looking up the syntax and multiple options available to populate the XML configuration file, or you could follow the following 4 easy steps to perform your desired Office 2019 or 365 installation (on one or several machines), soup-to-nuts: Not quite! It actually involves a single command line executable (the Office Deployment Tool) and a custom XML configuration file to drive the download and installation of a selected Office version with selected installation options. But however it works under the covers, you may still have expected that some sort of setup executable and installation GUI would be involved. You will no doubt have already read somewhere that all flavors of Office 2019 & 365 are delivered using so-called “ Click-to-Run” *** installation technology rather than Windows Installer (MSI) packages, fine. etc.) and you’re now just looking to get the damned Office bits of your choice installed on one or more machines. I start instead from the assumption that, after reading the necessary volumes of Talmudic debate and Rabbinical commentary, you’ve settled on the appropriate product for your particular situation (Windows 10 “standard”, LTSB 2016, or LTSC 2019, Windows Server 2016 or 2019, RDSH/ Citrix or not, older Windows, etc. subscription, or the myriad rules & regulations pertaining to the OS platforms on which each one may or may not be installed.

This awesome post from Jacques Bensimon is for all the Admins out there! Have a great 2019!įirst off, this quick hit article is NOT about the differences between Microsoft Office 2019 and Office 365, perpetual license vs.

Error installing office 2019