For more information on that scenario, including using Group Policy, see Choose how to manage updates to Microsoft Apps. When installing Microsoft Apps, 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 Microsoft Apps for enterprise applications except Publisher:.
If you've already installed Microsoft Apps, 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 Microsoft Apps. 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 Microsoft Apps for enterprise:. For more information about the options for excluding or removing apps, see Configuration options for the Office Deployment Tool.
If you don't want OneDrive installed with those applications, use the ExcludeApp element to remove it, as shown in the example. For details on deploying languages, see Overview of deploying languages for Microsoft Apps.
As part of your deployment, you can define application preferences for Microsoft Apps, including VBA Macro notifications, default file locations, and default file formats. To do so, you deploy Office using the standard steps in Install Microsoft Apps , but you include application preferences 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 this example, the configuration file installs the bit version of Microsoft Apps for enterprise in English and displays the Trust Bar for all VBA macros in Excel.
For more information on the app preferences, we recommend browsing the options in the tool itself. Note: When Office is installed, the app preferences 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. You can apply new application preferences to client computers that already have Microsoft Apps installed without changing any other deployment setting.
To do so, create a configuration file that contains application preferences and then run the ODT in customize mode. Customize mode ignores all other settings in the configuration file except application preferences.
You must run the executable from the client computer on which you want to apply the app preferences and you must have local administrator permissions on that computer. When using customize mode, the app preferences 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 preferences when Office apps are running, the preferences will be applied when Office is next restarted. To do so, update the configuration file and then run the ODT in packager mode. You must create App-V packages on a computer that has a clean install of the operating system. This article does not cover all the issues related to deploying App-V packages. In this example, the configuration file creates an App-V package from a bit English edition of Microsoft Apps for enterprise without Publisher:.
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 ,.
From a command prompt, run the ODT executable in packager mode with a reference to the configuration file you saved and to the location where you want to save the App-V package. You can customize these options to match the requirements for your organization, including deploying to more than two groups, changing update channels, and deploying Visio and Project. For more details, see Customize your deployment. Because you're deploying Microsoft Apps from a local source, you have to create folders to store the Office installation files.
You'll create one parent folder and two child folders, one for the pilot group, with the version of Office from Semi-Annual Enterprise Channel Preview , and one for the broad group, with version of Office from Semi-Annual Enterprise Channel. In this article, we have just one shared folder on the network, but many organizations make the Office installation files available from multiple locations. Using multiple locations can help improve availability and minimize the effect on network bandwidth.
For example, if some of your users are located in a branch office, you can create a shared folder in the branch office. Those users can then install Office from the local network. For more information, see DFS Management.
If you've already downloaded the ODT, make sure you have the latest version. After downloading the file, run the self-extracting executable file, which contains the ODT executable setup. To download and deploy Microsoft Apps to the pilot group, you use a configuration file with the ODT.
To create the configuration file, we recommend using the Office Customization Tool. For more information about the configuration options, see Configuration options for the Office Deployment Tool.
For more details on the most recent version of Office based on the different update channels, see Release information for updates to Microsoft Apps. Using the Office Customization Tool , create the configuration file for the broad group. This configuration file is used to download Office installation files and then deploy them to the broad group. The settings are exactly the same as the first configuration file, except the source path points to a different folder SAC , and the update channel is set to Semi-Annual Enterprise Channel.
From a command prompt, run the ODT executable in download mode and with a reference to the configuration file for the pilot group:. The files should begin downloading immediately. 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. If you run into problems, make sure you have the newest version of the ODT and make sure your configuration file and command reference the correct location.
From a command prompt, run the ODT executable in download mode and with a reference to the configuration file for the broad group:. Instead of using a text editor to create your configuration.
The OCT provides a web-based interface for making your selections and creating your configuration. 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. The following table lists the most common settings to configure in the configuration. More information about these configuration. Keep in mind that not all the information in that article applies to Office The following is a sample configuration.
We recommend that you uninstall any previous versions of Office before installing volume licensed versions of Office There are several ways that you can use the RemoveMSI element when installing volume licensed versions of Office Even though this article is about Microsoft Apps, most of the information also applies to volume licensed versions of Office Once you have a copy of the ODT and have created your configuration.
To do that, open an elevated command prompt, go to the folder where you saved the ODT and the configuration. If you have saved the configuration.
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. For example, Which files you see and the names of the files depend on whether you are downloading the bit or bit version of Office and which languages you are downloading. You can also use Microsoft Endpoint Configuration Manager to deploy volume licensed versions of Office Configuration Manager current branch has a wizard that steps you through the process and builds the configuration.
Earlier versions of Configuration Manager require you to download the ODT and create your own configuration. You must be using at least version , but version is recommended. On that same page, you can also select to install Project and Visio. Then, in Configuration Manager, you create an application and a deployment type. After that you distribute the application and then deploy it.
You can use the ODT and the configuration.
0コメント