Download office 2016 iso customization tool

This will launch the tool and ask you if you want to create a new setup file or open an existing one. Create a new one for your Office product. Go through each section listed in the left pane and configure the settings on the right to your specifications such as organization name, product key, trusted locations, shortcuts, and much more.

When you are all done, save the configuration to a. The properties seem to be the same as Office or at least newer documentation has not been produced yet. You must enter your product key in the Licensing and user interface section without any hyphens for this to succeed. If you use Microsoft Endpoint Configuration Manager current branch to deploy Office, we recommend using the Office Installer wizard in the Configuration Manager console. That wizard includes a customized version of the Office Customization Tool.

Follow these steps to create a configuration file that can be used by the Office Deployment Tool or another software distribution solution to install Office. We recommend saving and managing your configuration files in the cloud. To do so, sign in to the Microsoft Apps admin center before you create your configuration file. For more information, see Save and manage configuration files in the cloud. You can now use the Office Customization Tool to create, save, and manage your deployment configuration files in the cloud.

You can also refer to these cloud-based files directly when running the Office Deployment Tool. To work with configuration files in the cloud, sign in to the Microsoft Apps admin center and go to the Device Configuration page under Customization. From that page, you can do the following actions:. When running the Office Deployment Tool, you refer to the cloud-based configuration file by including the link in quotes.

To deploy with the ODT, for example, use setup. You can also copy, upload, or download configuration files from the Device Configuration page. For example, you can create a baseline configuration file and then create copies of that baseline for custom configurations.

For more information, see Plan setup of Office multilanguage deployment. When a user starts an Office application for the first time, setup applies default settings that match the language that is installed on the computer and the language that is specified by the Windows user locale setting. For more information about these three methods, see Plan language customizations for Office. For instructions on configuring language settings by using these methods, see Customize language settings in this article.

If users have to edit in a language or a companion proofing language that is not installed, you can customize and install the Office proofing tools. For more information, see Plan for Office proofing tools.

To determine which of the following procedures to use for your deployment and which customizations you might have to make, see Plan for multilanguage deployment of Office In the list of products, select the product for which you want to download packages. For example, select Office Professional Plus Specify the download method you want to use and the language for which you want to download packages.

The list of files contains all available language packs, language interface packs, and proofing tools for the language and edition that you specified.

For example, for Office Professional Plus , the results will look similar to the following figure. Select the appropriate package from the list and then, under Download , select the down arrow to download the ISO image to your computer or to a shared folder on your network. Download the edition that matches your version of Office. For example, if you are running bit Office Professional Plus on bit Windows, download the bit edition of the language pack, language interface pack, or proofing tools package.

If you are running bit Office Professional Plus on bit Windows, download the bit edition of the language pack, language interface pack, or proofing tools package. If users in your organization work with Office files that are in the same language, or in a language that matches the language of their operating system, you can deploy a default language version of Office.

The following steps are the same as the standard steps for deploying Office They are included for testing. The only difference in the steps is that you must copy the language packs to the same network location as the installation files.

Create a network installation point for the primary Office product by copying all the files and folders from the source media to a shared network location. Copy all the files and folders from the source media for each language pack to the same network location. When you are prompted to overwrite duplicate files, choose No. Because most of the customizations apply to the core product, you do not typically have to customize each language separately.

Setup applies your customizations during the installation regardless of the language that you are installing. For information about how to customize language settings, see Customize language settings. Language packs that are obtained through a volume license agreement do not require a unique product key.

Only one volume license key is required for the installation. On the setup command line, specify the Config. Setup installs only the language-specific elements that are needed for the Office product that you are installing. Setup does not install the complete language pack unless you deploy the language pack as a separate product. If users in your organization work with Office files in more than one language, or if they want an Office language that does not match the language of their operating system, you can install all the languages they want at the same time.

The only difference in the steps is that you must copy the language packs to the same network location as your installation files and edit the Config. Create a network installation point for your primary Office product by copying all the files and folders from source media to a shared network location.

For example, if you are adding languages to an installation of Office Professional Plus , find the Config. WW folder. Set the value of the Id attribute to the language tag that corresponds to the language that you want to install.

For example, to specify that setup install both English and French, with English as the default installation language, add the following elements:. If you want the default installation language and the Shell UI to match the operating system language, and you also want every user to have Office in both English and French, the code in the Config. Skipping this step causes the installation to fail. To specify that setup also match the language of the user's Windows user locale, add another line in the Config.

When you do this, setup installs all specified languages plus the language that matches the user locale, if that language is different. You must use a fully-qualified path. You can give different groups of users different sets of Office languages. For example, a subsidiary that is based in Tokyo might have to work with Office documents in English and Japanese, whereas users in the European subsidiary need English, French, and German. In this scenario, create a unique Config. The following steps are the same as the standard steps to deploy the Office The only differences in the steps is that you must copy the language packs to the same network location as the installation files, create and edit the Config.

For example, if you are installing Office Professional Plus , find the Config. Deploy Office to each group of users separately, and in each case specify the correct Config.