Download configuration file

This behavior prevents setup from connecting to Microsoft when you start the site install or upgrade. You can use the same local copy of setup files for other site installations or upgrades of the same version. If your organization restricts network communication with the internet using a firewall or proxy device, you need to allow the tool to access internet endpoints.

The device where you'll run the tool requires internet access the same as the service connection point. For more information, see Internet access requirements. On a computer that has internet access, browse to the installation media for the version of Configuration Manager that you want to install. Specify the path for the folder to store the updated installation files, and then select Download. Setup downloader verifies the files that are currently in the download folder.

It downloads only files that are missing or that are newer than existing files. It creates subfolders for downloaded languages, and other required components. Open a command prompt, and change directory to the installation media for the version of Configuration Manager that you want to install. When you use this option, it doesn't download any files. When you use this option, the download path is required.

Download path : To automatically start the verification or download process, specify the path to the download folder. The value that you specify for the MSICondition attribute can be either a volume licensed or a retail version of the product, as long as that version of the product was installed by using MSI. MSICondition will recognize , , , and versions of the Office product that you specify.

But, you can't specify a particular version. WW folder of the installation files for your existing version of the Office product. For example, the Setup. WW folder. You can specify multiple types of an Office product, separated by a comma. In the following example, Project Online Desktop Client will be installed on the device only if an MSI-based version of Project Standard is already installed on the device.

Defines which languages to download or install. If you define multiple languages, the first language in the configuration file determines the Shell UI culture, including shortcuts, right-click context menus, and tooltips.

If you decide that you want to change the Shell UI language after an initial installation, you have to uninstall and reinstall Office. For a list of all languages, see Languages, culture codes, and companion proofing languages. MatchOS and MatchInstalled cannot install the operating system languages if Office doesn't support that language or if the ODT cannot find the correct language pack in the local source files.

MatchInstalled can be used only if there is at least one Click-to-Run product already installed. For more information about MatchInstalled, see Overview of deploying languages and Build dynamic, lean, and universal packages for Microsoft Apps. When using MatchOS, we recommend that you specify a fallback language to install when a matched language isn't supported by Office or can't be found in the local source files.

To do so, use the "Fallback" attribute. For more information, see Install the same languages as the operating system. When using MatchInstalled, you can specify if you want to match the list of already installed languages for a specific product or the combination of all installed products. To target a specific product, you can specify any supported product ID. If you want to match the languages of all already installed products, you specify "All".

ODT will then install the new product with the same set of languages as the one specified in TargetProduct. If Level is set to None , Office is installed with no user interface: no progress bars, completion screens, error messages, or other user interface are displayed. If Level is set to Full , Office is installed with the normal installation experience. If you deploy a version of Office before Version , this setting will be applied only if you install with the user's account.

Defines which Microsoft Apps products should not be installed. If you don't want OneDrive installed with those applications, use the ExcludeApp element to remove it. If a configuration file with ExcludeApp is used to install Office on a device that already has Microsoft Apps installed, the ExcludeApp setting is treated differently based on the list of languages:.

For OneDrive for Business, use Groove. For Skype for Business, use Lync. Because Microsoft Apps is set to activate automatically, you should not set this property for Microsoft Apps products.

Data loss may occur. But, this doesn't enable you to deploy more than one Office App-V package to a single computer. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported. For more information, see Overview of shared computer activation for Microsoft Apps. Set SCLCacheOverride to 1 if you're using shared computer activation and you want to roam the licensing token. This is only needed if you choose to move the licensing token from its default location.

Set SCLCacheOverrideDirectory to specify a folder location for the licensing token if you're using shared computer activation and you want to roam the licensing token. Defines the Office licensing mode for device-based activation. For more information, see Device-based licensing for Microsoft Apps for enterprise.

Defines whether shortcut icons for Office products are added to the Windows taskbar in Windows 7 and 8. If you install Office using a system account, which is common when deploying with Microsoft Endpoint Configuration Manager, the icons will not be pinned even if this property is set to True. Microsoft Apps is no longer supported on Windows 7.

For more information, see Windows 7 end of support and Microsoft Apps. Defines which products and languages to remove from a previous installation of Microsoft Apps. To remove an installed language, you must provide both the product and the language, as in the example.

To remove all the installed languages, do not include the language attribute. Run the command-line AddNode on all the additional nodes that will join the failover cluster, by supplying the same configuration file using the ConfigurationFile parameter.

Advanced install option prepare failover cluster on all failover cluster nodes, then, after preparing all the nodes, run complete on the node that owns the shared disk :. Supply the same ConfigurationFile. After all the nodes have been prepared, run a complete failover cluster operation on the node that owns the shared disk and capture the ConfigurationFile. Run upgrade on the passive node and capture the ConfigurationFile. You can do this either by performing the actual upgrade, or exiting at the end without doing the actual upgrade.

On all the additional nodes to be upgraded, supply the ConfigurationFile. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Note The setup infrastructure writes out all the appropriate parameters for the actions that were run, with the exception of sensitive information such as passwords.

Note If you need to make changes to the configuration file, we recommend that you make a copy and work with the copy.