Volume-licensed Version Of Microsoft Office Professional Plus 2019 Download

0 views

Skip to first unread message

Tamsyn

unread,

Jul 24, 2024, 11:32:30 PM7/24/24

to dragsimischtrod

To set up and deploy volume licensed versions of Office 2019, including Project and Visio, within your organization, utilize the Office Deployment Tool (ODT). The Office Customization Tool (OCT) that you previously used for Windows Installer (MSI) is no longer used.

The installation files for Office 2019 are available on the Office Content Delivery Network (CDN) on the internet instead of on the Volume Licensing Service Center (VLSC). You can install Office 2019 directly from the Office CDN. Or, you can download the installation files from the Office CDN to a location on your local network, such as a shared folder, and install Office 2019 from that location. You can use different methods for different sets of computers in your organization. Whichever method you choose, you use the ODT.

volume-licensed version of microsoft office professional plus 2019 download

DOWNLOAD ✯ https://cinurl.com/2zMsk2

Installing directly from the Office CDN requires the least amount of administrative effort and is recommended. But you might have constraints that prevent you from installing directly from the internet. For example, some computers might lack internet connectivity, or you could have limited bandwidth to the internet.

After you download the Office Deployment Tool, double-click on the officedeploymenttool executable (.exe) file to extract the ODT files. When you're finished, you should have several files: setup.exe and some sample configuration.xml files. For an Office 2019-specific sample, see Sample configuration.xml file to use with the Office Deployment Tool.

The setup.exe file is the ODT and is a command-line tool that supports downloading and installing Office 2019. The configuration.xml files are sample files to get you started. You use the configuration.xml file to provide settings for the ODT to use when downloading or installing Office 2019. The configuration.xml is a simple xml file that can be created and edited in any text editor, such as Notepad. You can name the file anything that you want, as long as it retains the xml file extension.

Once you have a copy of the ODT, you need to create a configuration.xml file. You can create multiple configuration.xml files to be used with the ODT. For example, to download and install the 64-bit version of Office Professional Plus 2019 in English, you need to create one configuration.xml file. For the 32-bit version of Visio Professional 2019 in French, you create a different configuration.xml file. When you run the ODT from an elevated command prompt, you specify which configuration.xml file to use.

Instead of using a text editor to create your configuration.xml, we recommend that you use the Office Customization Tool (OCT). The OCT provides a web-based interface for making your selections and creating your configuration.xml file to be used with the Office Deployment Tool. For more information, see Overview of the Office Customization Tool. Please note that this is different than the Office Customization Tool that you might have used in the past to install volume licensed versions of Office that used Windows Installer (MSI) as the installation technology.

There are a series of settings in the configuration.xml file that you configure to customize the Office 2019 download or installation. The following table lists the most common settings to configure in the configuration.xml file.

Uninstall any previous versions of Office before installing volume-licensed versions of Office 2019. To uninstall Office versions that use Windows Installer (MSI) as the installation technology, use the Office Deployment Tool and include the RemoveMSI element in your configuration.xml file.

For more information about using RemoveMSI, see Remove existing MSI versions of Office when upgrading to Microsoft 365 Apps. Even though this article is about Microsoft 365 Apps, most of the information also applies to volume licensed versions of Office 2019.

Once you have a copy of the ODT and created your configuration.xml file, you can download the Office 2019 installation files to your local network. To do that, open an elevated command prompt, go to the folder where you saved the ODT and the configuration.xml file, and type this command:

If you want to check that the files are downloading, go to the location you specified for your SourcePath in the configuration.xml file. You should see a folder named "Office" with a subfolder named "Data." Also, there's a folder named with the version number of the download. For example, 16.0.10336.20044. Which files you see and the names of the files depend on whether you're downloading the 32-bit or 64-bit version of Office and which languages you're downloading.

After obtaining the ODT and preparing your configuration.xml file, and once the Office 2019 installation files are downloaded to your local network (if needed), you can proceed with the Office 2019 installation. To do that, open an elevated command prompt, go to the folder where you saved the ODT and the configuration.xml file, and type the following command:

You can also use Microsoft Configuration Manager (current branch) to deploy volume licensed versions of Office 2019. The Office 365 Client Installation wizard steps you through the process and builds the configuration.xml file for you. You see an entry for Office Professional Plus 2019 in the wizard. On that same page, you can also select to deploy Project and Visio. To get to the wizard, in the Configuration Manager console, navigate to Software Library > Overview > Office 365 Client Management.

To determine if your 2007 Office suite installation is a volume licensed version, check the 2007 Office suite installation disk to see if it contains a folder named Admin. If the Admin folder exists, this disk is a volume license edition. If the Admin folder does not exist, this disk is a retail edition. For more information, see Microsoft Knowledge Base article 93141: How to determine whether you have a retail edition or a volume license edition of a 2007 Microsoft Office suite ( =149830).

Setup looks for a copy of Config.xml in the same folder as Setup.exe. If a copy is not found there, Setup uses the Config.xml file that resides in the core product folder for the product that you are installing. If there are multiple products available in the installation source, Setup waits until you specify which product to install before it looks for the copy of Config.xml. Because of this design, the Logging element is only used by Setup when the Config.xml file resides in the same folder as Setup.exe, or if you specify the Config.xml file by using the Setup /config command-line option. If Setup uses the Config.xml file in the product folder, the default standard logging options are used.

Sidenote: If you only have one .MSP file then you can place it in the Updates folder under the root folder and just run the "setup.exe" without switches. "Setup.exe" will automatic apply the saved .msp file from the updates folder.

Sidenote: If your config.xml is in another directory then (besides the root folder and the OMUI.NL-NL folder then you have to give the full path in the command line).

Then i updated existing setup customized file (.msp) file in a way to completionNotice=yes to let me know the status of the application installation process for testing purpose. but it displays this error message "set up was aborted. setup customization files are not supported on this microsoft office product type. Run setup again without usig a setup customization file. This customization file may be located in the updates folder of the installation image"

I've tried deploying Office 07 Enterprise a few times now and I keep getting the same result. The program begins to install but the initial dialog appears asking which product I wish to install. I used OCT to create my MSP package and it is placed in the Updates folder. I still see this dialog. I tried using the config.xml file as well to cache the install then a TS to execute the install from the local media. This also produced the same dialog. Any ideas as to what I am doign wrong? If I simply select Enterprise from this first dialog, the install continues and works fine.

Can anyone tell me what happens if a users is working in office 03 and sccm tries to install office 07. Will the user get a notification, or will it just close out the application they are working in and install 07? I have tested that my package work, but it has never completed the install while I was actually in the office. I am ready to push this out to about 100 users but my boss would like to know this before we start so we can let the users know what will take place.