Office 365 Proofing Tools Download

Missing Proofing Tools Office 365
Microsoft Office 365 Proofing Tools Download
Office 365 Arabic Proofing Tools
Office 365 Proofing Tools Download Full
Office 365 Proofing Tools Download Windows 7

Issues with Office 365 This worked fine in OneNote 2010 and OneNote 2013 MSI installations. However most users now get Office through online channels and download it using the Click-2-Run technology. Office 365 works this way for most users. Unfortunately the proofing tools are MSI based and does not work well with Click-2-Run. Language packs (proofing tools) for Office Pro Plus 2019 x64 - How to Solve?

May 20, 2019 Added the ability to install individual C2R proofing tools packages with or after initial install. This means that we are able to install extra proofing tools together with Office 365 ProPlus by customizing the configuration file. Unfortunately we cannot use the Office Customization Tool to create the configuration file, because this feature is.

-->

The Office Deployment Tool (ODT) is a command-line tool that you can use to download and deploy Office 365 ProPlus to your client computers. The ODT gives you more control over an Office installation: you can define which products and languages are installed, how those products should be updated, and whether or not to display the install experience to your users.

If you're not an enterprise administrator and are looking to install Office 365 in your home or business, see Install Office with Office 365.

Download the Office Deployment Tool

Download the Office Deployment Tool from the Microsoft Download Center.

After downloading the file, run the self-extracting executable file, which contains the Office Deployment Tool executable (setup.exe) and a sample configuration file (configuration.xml).

Before using the ODT to download or install Office, we recommend making sure you have the latest version.

Get started with the Office Deployment Tool

The ODT consists of two files: setup.exe and configuration.xml. To work with the tool, you edit the configuration file to define what options you want, and then run setup.exe from the command line. For example, you can edit the configuration file to download the 64-bit English edition of Office, or you can edit the file to install the 64-bit English edition of Office with the EULA automatically accepted and without Publisher. For the full set of options, see Configuration options for the Office Deployment Tool.

Note

Best practice: This article shows the XML elements and attributes in the configuration file for the Office Deployment Tool. You can continue to create the configuration file in a text editor, but we recommend using the Office Customization Tool instead. With the Office Customization Tool, you can easily create and modify configuration files in a web-based interface. For more details, see Overview of the Office Customization Tool.

When running the ODT, you provide the location of the configuration file and define which mode the ODT should run in:

To download Office 365 ProPlus products and languages, use download mode. Example: setup.exe /download downloadconfig.xml. Note that when you download Office to a folder that already contains that version of Office, the ODT will conserve your network bandwidth by downloading only the missing files. For example, if you use the ODT to download Office in English and German to a folder that already contains Office in English, only the German language pack will be downloaded.
To install the downloaded Office 365 ProPlus products and languages on a client computer, use configure mode. You also use configure mode to remove and update Office products and languages. Example: setup.exe /configure installconfig.xml
To apply new application settings to client computers that already have Office 365 ProPlus installed, use customize mode. This mode will apply only application settings, without changing any other deployment settings. Example: setup.exe /customize appsettingsconfig.xml
To create an App-V package from the downloaded Office 365 ProPlus products and languages, use packager mode. Example: setup.exe /packager packageconfig.xml

You can also use help mode to read command-line help for the tool.

Download the installation files for Office 365 ProPlus

Follow these steps to download installation files for Office 365 ProPlus from the Office Content Delivery Network (CDN).

Step 1: Create the configuration file

When creating the configuration file, we recommend starting with an example file and updating it with the appropriate options for your environment. You can start by copying and pasting the example below into a text file, saving it with a name of your choosing, and then editing the XML elements and attributes to define the options you want.

In this example, the configuration file downloads the installation files for a 32 bit English edition of Office 365 ProPlus and Visio Online Plan 2 (previously named Visio Pro for Office 365) to servershare on your network:

For more information about the configuration options and more examples, see Configuration options for the Office Deployment Tool.

Step 2: Run the ODT executable in download mode

From a command prompt, run the ODT executable in download mode and with a reference to the configuration file you just saved. In this example, the configuration file is named downloadconfig.xml:

setup.exe /download downloadconfig.xml

Step 3: Validate that the files have been downloaded

After running the command, go to the download location you defined in the configuration file and look for an Office folder with the appropriate files in it. If you run into problems, make sure you have the newest version of the ODT. You can also troubleshoot issues by reviewing the log file in the %temp% directory.

Download the installation files for Office 365 ProPlus from a local source

You can use the Office Deployment Tool to download the installation files for Office 365 ProPlus from a local source on your network instead of from the Office Content Delivery Network (CDN). By doing so, you can store a central copy of multiple languages and products for Office and distribute just the languages and products that you need to other locations on your network.

To download from a local source, follow the steps for downloading Office with the ODT, but include in your configuration file the download path, which defines where the installation files are downloaded from. For example, this configuration file downloads a 32 bit English edition of Office 365 ProPlus from serverashare (the DownloadPath) to serverbshare (the SourcePath):

Note that you must specify a Version when using DownloadPath.

Install Office 365 ProPlus

After you download Office 365 ProPlus installation files, follow these steps to install Office on a client computer. As part of that installation, you can choose which products to install.

Step 1: Create the configuration file

In this example, the configuration file installs a 32 bit English edition of Office 365 ProPlus without Publisher:

The location of the Office installation files is servershare. The display level is set to None, which means the user will not see any user interface during the install, and the AcceptEULA is set to TRUE, which means your users will not have to click to accept the EULA during the installation.

For more information about the configuration options, see Configuration options for the Office Deployment Tool.

Step 2: Run the ODT executable in configure mode

From a command prompt, run the ODT executable in configure mode with a reference to the configuration file you just saved. In the following example, the configuration file is named installconfig.xml:

setup.exe /configure installconfig.xml

You must run the executable from the client computer on which you want to install Office and you must have local administrator permissions on that computer.

Step 3: Verify that installation was successful

After running the command, you should see the Office installation start (unless you set display level to none). After installation is complete, the command prompt will display 'Products configured successfully.' If you run into problems, make sure you have the newest version of the ODT. You can also troubleshoot issues by reviewing the log files in the %temp% and %windir%temp directories.

Update Office 365 ProPlus

You can use the Office Deployment Tool to make updates to your client computers after installing Office 365 ProPlus. There are two ways to do this:

Use the ODT to install Office 365 ProPlus again, which will update Office to the newest version. Only the files that have changed in the new version will be updated.
Use the ODT to download the Office installation files and then point your client computers to that location to receive their updates. (By default, clients are updated directly from the Office Content Delivery Network (CDN).)

To change where your client computers receive their updates, run the ODT in configure mode and specify an update path in the configuration file. For example, to have Office 365 ProPlus get updates automatically from a network share called serverupdates, include the following line in your configuration.xml file:

<Updates Enabled='TRUE' UpdatePath='serverupdates' />

This article does not cover all the issues related to managing updates for Office in your organization. For more information on that end-to-end scenario, including using Group Policy, see Choose how to manage updates to Office 365 ProPlus.

Exclude or remove Office 365 ProPlus applications from client computers

Missing Proofing Tools Office 365

When installing Office 365 ProPlus, you can exclude specific applications. To do so, follow the steps for installing Office with the ODT, but include the ExcludeApp element in your configuration file. For example, this configuration file installs all the Office 365 ProPlus applications except Publisher:

If you've already installed Office 365 ProPlus, you can also use the ExcludeApp element to remove an application that you've previously installed. For example, the configuration file above removes Publisher from the previous installation of Office.

You can also remove an entire language version of Office 365 ProPlus. To do so, follow the steps for excluding products for installing Office with the ODT, but replace the configuration file with one that uses the Remove element. For example, this configuration file removes the Spanish language version of Office 365 ProPlus:

For more information about the options for excluding or removing apps, see Configuration options for the Office Deployment Tool.

Exclude OneDrive when installing Office 365 ProPlus or other applications

OneDrive is automatically installed when you install Office 365 ProPlus, Word, Excel, PowerPoint, Publisher, Visio, and Skype. If you don't want OneDrive installed with those applications, use the ExcludeApp element to remove it, as shown in the example.

Deploy multiple or matching languages

For details on deploying languages, see Overview of deploying languages in Office 365 ProPlus.

Apply application settings to Office 365 ProPlus

As part of your deployment, you can define application settings for Office 365 ProPlus, including VBA Macro notifications, default file locations, and default file formats. To do so, you deploy Office using the standard steps in Install Office 365 ProPlus, but you include application settings as part of your configuration file.

To create the configuration file, we recommend you use the Office Customization Tool for Click-to-Run, a web application with a full user interface.

In your web browser, open the Office Customization Tool for Click-to-Run and follow the steps to create a configuration file, including defining application settings alongside the standard deployment settings.
Export the file.
Follow the steps in Install Office 365 ProPlus to deploy Office with the newly created configuration file.

In this example, the configuration file installs the 32-bit version of Office 365 ProPlus in English and displays the Trust Bar for all VBA macros in Excel.

This file was created with the Office Customization Tool for Click-to-Run. For more details on the app settings, we recommend browsing the options in the tool itself.

Note: When Office is installed, the app settings defined in the configuration file are applied to all existing users of the device and any new users added to the device in the future.

Apply application settings to an existing installation of Office 365 ProPlus

You can apply new application settings to client computers that already have Office 365 ProPlus installed without changing any other deployment setting. To do so, create a configuration file that contains application settings and then run the ODT in customize mode. Customize mode ignores all other settings in the configuration file except application settings.

Use the steps in define application preferences to create the configuration file.
From a command prompt, run the ODT executable in customize mode with a reference to the configuration file you just created. In the following example, the configuration file is named installappsettings.xml:

setup.exe /customize installappsettings.xml

You must run the executable from the client computer on which you want to apply the app settings and you must have local administrator permissions on that computer. Note that when using customize mode, the app settings defined in the configuration file are applied to all existing users of the device and any new users added to the device in the future. If you apply application settings when Office apps are running, the settings will be applied when Office is next restarted.

Create an App-V package for Office 365 ProPlus

In addition to downloading and deploying Office 365 ProPlus, you can use the Office Deployment Tool to create App-V packages. To do so, update the configuration file and then run the ODT in packager mode. You must create App-V packages on a computer with a clean install of the operating system.

This article does not cover all the issues related to deploying App-V packages. For more information on that end-to-end scenario, see Deploying Microsoft Office 2016 by Using App-V.

Step 1: Create the configuration file

In this example, the configuration file creates an App-V package from a 32-bit English edition of Office 365 ProPlus without Publisher:

The location of the Office installation files is servershare. For your configuration file, substitute the example values with the appropriate option for your environment. For more information about the options, see Configuration options for the Office Deployment Tool,

Step 2: Run the ODT executable in packager mode

From a command prompt, run the ODT executable in packager mode with a reference to the configuration file you just saved and to the location where you want to save the App-V package. In the following example, the configuration file is named packageconfig.xml and the App-V package will be saved to servershareappv:

setup.exe /packager packageconfig.xml servershareappv

Step 3: Verify that the package was created

After running the command, the package location should have an App-V Packages folder and a WorkingDir folder. You can troubleshoot issues by reviewing the log file in the %temp% directory.

Best practices for deploying languages

When deploying multiple languages in a large organization, we recommend these best practices:

Automatically install the same languages as the operating system.
If you deploy Office from a local source on your network, use the Office Content Delivery Network (CDN) as a backup source for language packs that might not be available at that local source.
When adding languages to an existing deployment of Office, you can deploy just the language packs, rather than the full version of Office.
If you upgrade from a Windows Installer (MSI) version of Office, you can automatically install the same languages as a previous MSI installation.
When building Office packages to deploy, include all the language packs you plan to deploy in each package. Creating separate packages for different language sets can make the Office deployment difficult to manage.
If you deploy a subscription version of Project or Visio to a device that already has Office installed, you can automatically deploy them in the same languages as the installed version of Office.
If you use some languages only as editing tools, you can deploy just the proofing tools instead of full language packs to conserve network bandwidth.

This article also includes the list of supported languages and details on how Office conserves network bandwidth when downloading language packs for deployment.

Install languages from the Office 365 portal

If your organization allows it, users can install Office 365 ProPlus languages directly from the Office 365 portal. When users install Office from the Software page, they select a language from the Language drop-down box. If a user needs an additional language, they can just re-run the process for each required language. The setup will add the selected language to the user's device.

Deploy multiple languages as part of deploying Office

To deploy Office 365 ProPlus in multiple languages, you just need to include the additional languages in the Office packages you create. To do so, select the languages you want to deploy in the Language section when creating the configuration file in the Office Customization Tool.

If you deploy Office from a local source on your network, you must download your languages to that source, in the same way that you download the Office package. For more details, see Download the installation files for Office 365 ProPlus. When deploying from a local source, we recommend that you use the Office Content Delivery Network (CDN) as a backup source for language packs.

For more details on standard deployments, see Plan your enterprise deployment of Office 365 ProPlus.

The primary language selected in the Office Customization Tool determines the Shell UI language. The Shell UI is the language that is used to display shortcuts, right-click context menus, and tooltips. If you decide that you want to change the Shell UI language after an initial installation, you must uninstall Office and reinstall it.

Deploy languages to existing installations of Office 365 ProPlus

After deploying Office 365 ProPlus, you can deploy additional languages for Office. To do so, use the same process and tools you used to deploy Office, such as Configuration Manager or the Office Deployment Tool.

If you're deploying languages from a local source, make sure the languages are available at that source. For more details, see Download the installation files for Office 365 ProPlus.
If you use a local source, we recommend that you use the Office Content Delivery Network (CDN) as a backup source for language packs.
When creating the configuration file in the Office Customization Tool, select Language Pack as the Additional Product in the Products section.
In the Language section, select the additional languages you want to install.
Deploy the languages using the same process you use to deploy Office.

When you add to an existing deployment, the ODT can automatically use the same architecture (32 bit or 64 bit) and source location (Office CDN or local source) as the existing installation of Office 365 ProPlus. Because of this, you do not need to specify these values when creating the configuration file, which means you can use a single configuration file to deploy to multiple deployment groups. The Office Customization Tool, however, requires that you specify all these values, so you can only use this feature if you create the configuration file in a text editor.

Deploy proofing tools

Each language version of Office 365 ProPlus includes proofing tools for a set of companion languages. For example, when you deploy the English version of Office, users receive proofing tools for English, Spanish, and French. These proofing tools include spelling and grammar checkers, thesauruses, and hyphenators. They might also include language-specific editing features such as Language AutoDetect, AutoSummarize, and Intelligent AutoCorrect.

If you want to deploy proofing tools in additional languages beyond the companion languages, you can deploy the full language pack for that additional language or you can deploy just the proofing tools for that additional language. Many administrators choose to deploy just the proofing tools to conserve bandwidth on the network and speed up installation on client computers.

To deploy just the proofing tools, use the same tools you used to deploy Office, such as Configuration Manager or the ODT. You can include proofing tools in the initial deployment of Office, or you can add them later to an existing deployment.

Note

To install proofing tools, you must be using at least Version 1803 of Office 365 ProPlus. You must also be using the latest version of the Office Deployment Tool, which you can download from the Microsoft Download Center. In addition, you cannot use the Office Customization Tool to create the configuration file, because this feature is not yet available in that tool. Instead, you must edit the configuration file in a text editor.

Office 365 Arabic Proofing Tools

If you're adding to an existing deployment, the ODT will automatically use the same architecture (32 bit or 64 bit) and source location (Office CDN or local source) as the existing installation of Office 365 ProPlus. Because of this, you do not need to specify these values when creating the configuration file, which means you can use a single configuration file to deploy to multiple deployment groups.

When creating the configuration file in a text editor, use 'ProofingTools' as the Product ID, along with the appropriate Language IDs, as shown in the example.
If you deploy languages from a local source, you must download the proofing tools to that source first. For more details, see Download the installation files for Office 365 ProPlus.
If you use a local source, we recommend that you use the Office CDN as a backup source for language packs and proofing tools by including the AllowCdnFallback attribute in the configuration file, as shown in the example.

For details on how to edit the configuration file in a text editor, see Configuration options for the Office Deployment Tool.

Example

This configuration file installs proofing tools for German and Italian using the Semi-Annual Channel on a device with Office already installed. If the original installation of Office was from a local source, make sure to download the proofing tools to that source. If the tools aren't found at the local source, the AllowCdnFallback setting installs the tools directly from the Office CDN.

Install the same languages as the operating system

When deploying Office, you can automatically install the same languages that are in use by the operating system. To do so, include the steps below when deploying Office with your standard process and tools:

When creating the configuration file in the Office Customization Tool, select Match Operating System as the primary language.
If you use a local source, we recommend that you use the Office CDN as a backup source for language packs. To do so, select Fallback to the CDN for missing languages in the Installation section.

When Match Operating System is used, the base language of the operating system and all active display languages for user profiles on the device are installed. Match Operating System can be used in combination with a fixed list of languages.

Deploy Visio or Project in the same languages as an existing version of Office 365 ProPlus

You can automatically deploy Visio and Project in the languages that are in use by an existing version of Office 365 ProPlus. To do so, use the same process and tools you used to deploy Office, such as Configuration Manager or the Office Deployment Tool.

Note

You cannot use the Office Customization Tool to create the configuration file, because this feature is not yet available in that tool. Instead, you must edit the configuration file in a text editor.

When creating the configuration file in a text editor, use 'MatchInstalled' as the Language ID, as shown in the example below.
In some cases, using Match Installed can change the Shell UI language. To avoid that, we recommend including 'MatchOS' or a specific language as the first Language ID, as show in the example below.
Optionally, you can include the TargetProduct as an attribute of the Language element, as shown in the example below. By doing so, you can specify which existing Office product should be used to determine which languages to install. For example, if you set TargetProduct = 'O365ProPlusRetail', the Office products you're deploying will be installed in the same languages as Office 365 ProPlus, if that product is installed on the client computer.
If you deploy languages from a local source, you must download any possible matched languages to that source first. For more details, see Download the installation files for Office 365 ProPlus.

You can also use MatchInstalled as the Language ID when adding Office apps to or removing them from an existing installation of Office.

For details on how to edit the configuration file in a text editor, see Configuration options for the Office Deployment Tool.

Example

Install the same languages as a previous MSI installation

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 install Office 365 ProPlus. For more information, see Remove existing MSI versions of Office when upgrading to Office 365 ProPlus.

Remove languages packs or proofing tools

To remove a language pack or proofing tool, you can use the Remove element, just as you would for a product. For product ID, specify LanguagePack or ProofingTools. In the example, the German language pack is removed across all installed products:

Example

Use the Office CDN as a backup source for language packs

If you deploy Office from a local source on your network, you can use the Office CDN as a backup source for language packs that might not be available at that local source. To do so, use the same process and tools you used to deploy Office, such as Configuration Manager or the Office Deployment Tool.

When creating the configuration file in the Office Customization Tool, select Fallback to the CDN for missing languages in the installation settings of the Office Customization Tool.

When installing languages, the ODT looks first for source files in the source path location. If the language pack isn't available at that location and the Fallback setting is selected, then the ODT will use source files from the Office CDN.

Conserve network bandwidth when adding language packs

When you use the Office Deployment Tool (ODT) to download the installation files for Office to a folder that already contains that version of Office, the ODT will conserve your network bandwidth by downloading only the missing files. For example, if you use the ODT to download Office in English and German to a folder that already contains Office in English, only the German language pack will be downloaded.

Languages, culture codes, and companion proofing languages

Language-neutral product resources for Office 365 ProPlus are packaged into a single file that contains all the neutral resources. Language-specific resources are packaged into language-specific files such as en-us for English (United States) resources.

The following table lists all the supported languages for Office 365 ProPlus, along with culture codes and companion proofing languages.