To configure and perform deployments of volume licensed versions of Office 2019, including Project and Visio, for users in your organization, you use the Office Deployment Tool (ODT). The Office Customization Tool (OCT) that you previously used for Windows Installer (MSI) is no longer used.
- Microsoft office open xml converter free download - Microsoft Open XML Converter, Office Open XML Cruncher, Open XML SDK 2.0 for Microsoft Office, and many more programs.
- Microsoft Office Open XML File Format Converter for Mac OS v.1.1.6 Advertisement Converts files that were created in Office 2008 for Mac or 2007 Microsoft Office system so that you can open and edit the files in Office 2004 version 11.4 or later and Office v.
Standard ECMA-376 Office Open XML File Formats 1 st edition (December 2006), 2 nd edition (December 2008), 3 rd edition (June 2011), 4 th edition (December 2012) and 5 th edition (Part 3, December 2015; and Parts 1 & 4, December 2016). This Standard defines Office Open XML's vocabularies and document representation and packaging. Jul 10, 2014 The open XML file cannot be opened because there are problems with the contents or the file name might contain invalid characters. Original Title: 'PROBLEM OPENING UP MICROSOFT WORD FOR OFFICE:MAC 2011'. Download Original png (64.48 K) This png file is about Office, XML, Microsoft, Formats, Mac, Open. You can use it in your daily design, your own artwork and your team project.
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.
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 not have connectivity to the internet or you may have limited bandwidth to the internet.
Download the Office Deployment Tool from the Microsoft Download Center
The Office Deployment Tool is a free download from the Microsoft Download Center. We recommend that you always download and use the most current version of the ODT.
After you download the Office Deployment Tool, double-click on the officedeploymenttool executable (.exe) file to extract the ODT files. When you are 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.
Create the configuration.xml
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, you would create a configuration.xml file to download and install the 64-bit version of Office Professional Plus 2019 in English and a different configuration.xml file to install the 32-bit version of Visio Professional 2019 in French. When you run the ODT from an elevated command prompt, you specify which configuration.xml file to use.
Tip
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.
Download Office Open Xml
Configuration | configuration.xml setting | Additional information |
---|---|---|
Where to download the Office installation files to and where to install Office from For example, servershare (a shared folder on your local network) |
SourcePath | If you don’t specify a SourcePath when using the ODT to install Office, the ODT looks for the installation files in the folder it’s located in. If it doesn’t find the Office installation files there, it goes to the Office CDN to get the installation files. We recommend that you install Office directly from the Office CDN, if internet connectivity and network bandwidth make that possible. |
Which products to download or install For example, Office Professional Plus 2019 |
Product ID | Valid values for volume licensed versions of Office 2019 include the following: - ProPlus2019Volume - Standard2019Volume - ProjectPro2019Volume - ProjectStd2019Volume - VisioPro2019Volume - VisioStd2019Volume For a list of Product IDs for other volume licensed versions of Office 2019, such as Access 2019, see Product IDs that are supported by the Office Deployment Tool for Click-to-Run. |
Use Key Management Service (KMS) to activate Office 2019 | PIDKEY | Enter the Generic Volume License Key (GVLK) for KMS activation. |
Use Multiple Activation (MAK) to activate Office 2019 | PIDKEY | Enter the product key for MAK activation. |
Which languages to download or install For example, English (en-us) and French (fr-fr). |
Language ID | You can install multiple languages at the same time you’re Installing Office 2019, or you can install them later. For more information, see Deploy languages for Office 2019. |
Which proofing tools to install | Product ID | The Product ID is 'ProofingTools' and is used in combination with the Language ID. For more information, see Deploy languages for Office 2019. |
Which edition of Office 2019 to download or install. For example, the 64-bit version. |
OfficeClientEdition | Valid xml values are '32' and '64.' All Office products on the computer must be of the same architecture. You can’t have both 32-bit and 64-bit Office products installed on the same computer. We recommend 64-bit on computers that have 4 gb or more of memory. But you should assess application compatibility and other factors that might require you to use the 32-bit version. For more information, see Choose between the 64-bit or 32-bit version of Office. |
Which apps to install For example, all apps except Publisher. |
ExcludeApp | By default, all apps included in Office Professional Plus 2019 are installed. For example, to not install Publisher, you can include the following line in your configuration.xml: <ExcludeApp /> For more information, see ExcludeApp element. |
Where to get security and quality updates from. For example, directly from the Office CDN on the internet. |
UpdatePath | The default is to get updates directly from the Office CDN on the internet. This is recommended and requires the least amount of administrative effort. But if you need to update computers that don’t have connectivity to the internet, you can specify that Office gets updates, for example, from a shared folder on your local network. But this means that you must download the updates from the Office CDN and copy them to the shared folder. For more information, see Update Office 2019 (for IT Pros). |
Which update channel to install from and get updates from | Channel | Office uses the concept of update channels to determine which updates an installed version of Office receives. For more information, see Update channel for Office 2019. |
Whether to remove previous Windows Installer (MSI) versions of Office before installing Office 2019 | RemoveMSI | This is recommended. For more information, see Remove existing versions of Office before installing Office 2019. |
Tip
More information about these configuration.xml settings is available here: Configuration options for the Office Deployment Tool. Keep in mind that not all the information in that article applies to Office 2019. For example, the settings related to shared computer activation, such as SharedComputerLicensing and SCLCacheOverride, don’t apply to Office 2019.
Sample configuration.xml file to use with the Office Deployment Tool
The following is a sample configuration.xml file that can be used to either download or install the 64-bit version of Office Professional Plus 2019 in English using a shared folder on your local network and activate by using MAK. If you’re using this configuration.xml to install Office 2019, previous Windows Installer (MSI) versions of Office are removed as part of the installation process. Also, even though it’s not specified in the configuration.xml file, updates are automatically enabled and are configured to come directly from the Office CDN, because those are the default settings.
For the PIDKEY, replace #####-#####-#####-#####-##### with your MAK client activation key.
Remove existing versions of Office before installing Office 2019
We recommend that you uninstall any previous versions of Office before installing volume licensed versions of Office 2019. To help you uninstall versions of Office that use Windows Installer (MSI) as the installation technology, you can use the Office Deployment Tool and specify the RemoveMSI element in your configuration.xml file.
There are several ways that you can use the RemoveMSI element when installing volume licensed versions of Office 2019.
- Uninstall all Office products on the computer.
- Identify any existing language resources, like language packs, and install the same languages.
- Keep some Office products and uninstall all other Office products on the computer.
RemoveMSI can be used to uninstall 2010, 2013, or 2016 versions of Office, Visio, or Project that were installed using Windows Installer (MSI).
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.
Download the Office 2019 installation files
Once you have a copy of the ODT and have 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 have saved the configuration.xml file with a different name, use that name in the command.
It will look as if nothing is happening, but the download is happening in the background. Once the download is complete, you are returned to a command prompt.
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.” There will also be 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 are downloading the 32-bit or 64-bit version of Office and which languages you are downloading.
Here some additional details about downloading Office 2019 installation files:
- You must download the 32-bit and 64-bit versions separately.
- All volume licensed versions of Office 2019 – such as Office Professional Plus 2019, Visio Professional 2019, and Project Professional 2019 – are included in the same download, regardless of which products you specify in the configuration.xml file. This helps you save disk space on your local network. The core files for the Office 2019 products are in the stream.x86.x-none.dat or stream.x64.x-none-dat file, depending if it’s the 32-bit or 64-bit version of Office.
Install Office 2019 by using the Office Deployment Tool
Once you have a copy of the ODT and have created your configuration.xml file (and downloaded the Office 2019 installation files to your local network, if necessary), you can install Office 2019. 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:
If you have saved the configuration.xml file with a different name, use that name in the command.
Once the installation is complete, you are returned to a command prompt and you can go open Office 2019 programs you’ve installed.
Install Office 2019 by using Microsoft Endpoint Configuration Manager
You can also use Microsoft Endpoint Configuration Manager to deploy volume licensed versions of Office 2019. Configuration Manager (current branch) has a wizard that steps you through the process and builds the configuration.xml file for you. Earlier versions of Configuration Manager require you to download the ODT and create your own configuration.xml file.
-
Configuration Manager (current branch): If you’re using Configuration Manager (current branch), you can use the Office 365 Client Installation wizard to deploy Office 2019. You must be using at least version 1710, but version 1806 is recommended. You’ll see an entry for Office Professional Plus 2019 in the Office 365 Client Installation wizard. On that same page, you can also select to install Project and Visio.
-
System Center 2012 R2 Configuration Manager: If you’re using System Center 2012 R2 Configuration Manager, the steps are different and much more manual. First you need to get a copy of the ODT from the Microsoft Download Center and create the appropriate configuration.xml file for your deployment. Then, in Configuration Manager, you create an application and a deployment type. After that you distribute the application and then deploy it.
Deploy languages for Office 2019
You can use the ODT and the configuration.xml file to install volume licensed versions of Office 2019, including Project and Visio, in multiple languages. For more details, see Language element.
You can also just install proofing tools by specifying the Product ID as 'ProofingTools' in your configuration.xml file along with the appropriate Language IDs. Proofing tools packages, which are a new capability for Office 2019, are much smaller than full language packs. Consider deploying proofing tools in cases where users work with documents in multiple languages but don’t need the Office product UI in all those languages. The proofing tools can be installed at the same time you’re installing Office 2019, or you can install them later. They can also be installed whether or not the language pack for a given language is installed.
If you're upgrading from a Windows Installer (MSI) version of Office, you can get Click-to-Run versions of the same language resources – for example, language packs, language interface packs, or proofing tools – installed when you deploy Office 2019. For more information, 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.
Related topics
Overview
This guide is written with the expectation that you have installed CrossOver and are ready to install Office. If not, go to the CrossOver overview page for Microsoft Office 2016 and follow the steps described there to get ready to install Office.
- Read through the tips & tricks pages as well as current forum threads.
- Choose an installation method from below and obtain the necessary installation files described for each method.
- Using the CrossOver Software Installer, Select Microsoft Office 2016 as the application, choose your installation file, select the bottle, install & finish.
Note: If using the ODT installation method, Office will not install as part of the CrossOver Software Installer wizard. Use the 'Run Command' inside the newly created bottle to navigate to and launch your batch file. During a download you will not receive progress updates, however the Office 2016 Pro Plus and Visio is approx. 1.8GB so you can monitor the download directory size or the log file to monitor progress. During install you will receive visual progress updates.
We also recommend using the 32-bit offline installer, as the 64-bit generally will fail to install.
Don't use an ISO
Based on the reports in the forums (as well as our own experience), installing from an ISO image does not appear to work (at least in version 17.0.0 of CrossOver). Microsoft discontinued the ISO version of Office 2016 in quarter 3 of 2017, with the Click-to-run installer being the default supported method of installation from that point on for end users.
Click-to-Run (C2R) - Default installation method
The standard installation method is to use the click-to-run installer from Microsoft which downloads the files and installs the software into the bottle.
Where to get it
You can download the installer if you have an active or trial Microsoft Office 365 subscription from https://www.office.com.
The following page provides in depth guidance from Microsoft of how to install the software, however for the purpose of installing using CrossOver, you can refer to this for the purpose of how to obtain the installer file and save it to disk so that you can execute it within CrossOver.
https://support.office.com/en-us/article/Download-and-install-or-reinstall-Office-365-or-Office-2016-on-a-PC-or-Mac-4414EAAF-0478-48BE-9C42-23ADC4716658?ui=en-US&rs=en-US&ad=US
Office Deployment Tool (ODT) for Click-to-Run (C2R) - Alternative installation method
The ODT is a useful alternative to the C2R tool as it enables Office products to be downloaded and deployed from local disk, is available publicly from Microsoft regardless of whether you have a Office subscription or license so enables you to test Office on CrossOver easily and repeatedly.
There are many other features to the ODT, however for the purposes of installing Office in CrossOver, these are the most valuable.
The ODT is a Microsoft command line executable you download and run inside a bottle to perform a Office download or installation.
Where to get it
The ODT can be obtained from Microsoft at the below link or by searching for 'Microsoft Office 2016 Deployment Tool' in Google.
https://www.microsoft.com/en-au/download/details.aspx?id=49117
Further information on the ODT
Using it
The ODT uses a configuration.xml file to automate the installation. A simple DOS batch file can be created to execute the download or installation.
Refer to the previous link for information on the options available in the configuration.xml file. Below is an example of an ODT installation setup:
Organise the following all in the same folder (anywhere in your Linux install):
- o365proplusretail-installation.bat (This batch file is used to perform the office installation, directly from the internet if you've not downloaded it locally or locally if you have executed the o365proplusretail-download.bat file beforehand)
- o365proplusretail-download.bat (This batch file is used to download the office installation files to the same folder as 'setup.exe')
- setup.exe (This is the ODT downloaded previously)
- o365proplusretail-configuration.xml (This is the ODT configuration file)
- Office/ directory (This is the downloaded copy of Office which is created by the tool after executing the download batch file)
o365proplusretail-installation.bat:
setup.exe /configure o365proplusretail-configuration.xml
o365proplusretail-download.bat:
setup.exe /download o365proplusretail-configuration.xml
o365proplusretail-configuration.xml:
<Configuration>
Office Open Xml Download Mac Pirate Bay
<Add OfficeClientEdition='32' >
<Product >
<Language />
</Product>
<Product >
<Language />
</Product>
</Add>
<Updates Enabled='TRUE' />
<Display Level='Full' AcceptEULA='TRUE' />
<Property Name='AUTOACTIVATE' Value='1' />
<Logging Level='Standard' Path='Y: />
</Configuration>
<Product >
<Language />
</Product>
<Product >
<Language />
</Product>
</Add>
<Updates Enabled='TRUE' />
<Display Level='Full' AcceptEULA='TRUE' />
<Property Name='AUTOACTIVATE' Value='1' />
<Logging Level='Standard' Path='Y: />
</Configuration>
Notes on the above example
- The Product ID must be correct for the license/subscription. Refer to 'How to select the correct Office software for your license/subscription' for further information.
- The ODT will save/use the Office software in the location of the ODT by default.
- The logging parameter will ensure the installation log file is saved to your linux home drive as Y: is mapped to your home drive by default in CrossOver on Linux. Z: is mapped to the root of Linux (/) by default. The log is useful for understanding why an installation failed.
- See the ODT reference guide for details on how to save the software elsewhere, choose alternative languages, display levels, updates, logging etc.
How to select the correct Office software for your license/subscription
Microsoft Office comes in a variety of plans and software packages so it is important to ensure you install the option that is suitable for your license or subscription or you will need to install again.
The following link from Microsoft advises which Product ID's (Software packages) are associated with each plan:
Note: The above Microsoft article does not include the Product ID for Microsoft Office 2016 Standalone which is typically associated with licenses purchased through the Microsoft Home Use Program (HUP). The product ID for this is ProPlusRetail (Source: https://answers.microsoft.com/...). These installations are licensed by a Product Key rather than a subscription.
Download Office Xml
Additional Information
If you have issues downloading the C2R installer file, try changing your browser agent, or downloading it from a Windows machine and transferring it to your computer.