• Microsoft Office Proplus 2019
• Office Proplus 2019 Retail Product Key Free

Sep 24, 2019 The recommended settings correspond with the Office 365 ProPlus administrative templates version 4909 released on September 5, 2019 that can be downloaded here. Componentization of GPOs Most organizations can implement most of the baseline’s recommended settings without any problems. Microsoft Office 2019 Pro Plus is an incredible office suite with a bunch of office work management tools and features. It also has lot of features for handling almost all types of documents and files most commonly used in routine business or office use. Moreover, Microsoft Office 2019 includes a lot of advance tools and features which includes.

Office 2019 is the latest version of Microsoft's productivity software that's available as a one-time purchase from a retail store or through a volume licensing agreement.

Important

Office 2019 is separate from Office that's available through Office 365 (or Microsoft 365) plans. For example, if you've deployed Microsoft 365 Apps for enterprise (previously named Office 365 ProPlus) to the users in your organization, you don't need Office 2019. You already have all the features, and many more, that are included in Office 2019.

Volume licensed versions of Office 2019 are available for enterprise admins to download and deploy to the users in their organization. The following Office products are available for devices running Windows:

• Office Professional Plus 2019
• Office Standard 2019
• Project Professional 2019
• Project Standard 2019
• Visio Professional 2019
• Visio Standard 2019

These Office products now use Click-to-Run, instead of Windows Installer (MSI), as the installation technology. But, how you activate these Office products – for example, by using Key Management Service (KMS) – remains the same.

For devices running macOS, Office Standard 2019 for Mac is available for volume licensed customers. For more information, see Deployment guide for Office for Mac.

For more information about these Office 2019 products, see Compare suites available through volume licensing.

What's changed in Office 2019?

The biggest change since Office 2016 is that the installation technology used by the new volume licensed versions of Office is Click-to-Run, instead of Windows Installer (MSI). Click-to-Run has been the installation technology for most Office products since the release of Office 2013.

In addition to Click-to-Run, the following are some other changes that you need to be aware of:

• Office 2019 is supported on Windows 10 but isn’t supported on Windows 7 or Windows 8.1. For more information, review the system requirements.
• To configure and perform installations, you use the Office Deployment Tool, which is a free download from the Microsoft Download Center. The Office Customization Tool that you previously used for Windows Installer (MSI) is no longer used.
• Instead of downloading the installation files from the Volume Licensing Service Center (VLSC), you use the Office Deployment Tool to download the installation files directly from the Office Content Delivery Network (CDN) on the internet.
• When you install Office Professional Plus 2019, all apps are installed by default. But, you can configure the Office Deployment Tool to exclude certain apps from being installed.
• Office 2019 is installed on the system drive, which is usually the C: drive. The installation location can’t be changed.
• You can configure updates to Office 2019, such as security updates and bug fixes, to be automatically downloaded and installed from the Office CDN. Individual downloads for each security update or bug fix aren’t available.

What's stayed the same in Office 2019?

Even though there is a different installation technology, you can still use the same software distribution tools, such as Microsoft Endpoint Configuration Manager, that you currently use to deploy Office. Also, how you activate volume licensed versions of Office – for example, by using Key Management Service (KMS) – remains the same.

The major version of Office 2019 is staying at 16.0, so some additional things are staying the same if you're upgrading from Office 2016, including the following:

• Existing Group Policy settings will continue to work, because the registry location for those settings will still be located in HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftOffice16.0 and HKEY_CURRENT_USERSOFTWAREPoliciesMicrosoftOffice16.0.
• Other registry locations and settings information that reference 16.0 will still apply.
• Add-ins and other extensibility solutions that are compatible with Office 2016 will most likely be compatible with Office 2019 or will require only minimal testing.

What are the new features in Office 2019?

For information about the new features in Office 2019, see the “what’s new” articles for Access, Excel, Outlook, PowerPoint, Project, Visio, and Word. Office 2019 includes some, but not all, features that are available in versions of Office that come with an Office 365 (or Microsoft 365) plan.

Office 2019 won’t receive additional new features now that it has been released. If you want to get new Office features on an on-going basis, you should consider moving to an Office 365 plan (or Microsoft 365) plan that includes Office. Most of these enterprise plans include Microsoft 365 Apps for enterprise (previously named Office 365 ProPlus), which includes the same Office apps as Office Professional Plus 2019. For more information about available plans, see Office 365 plans for enterprises and Microsoft 365 plans for enterprises. For more information about new features, see What’s new in Microsoft 365.

How do I upgrade to Office 2019?

We recommend that you uninstall existing versions of Office before you deploy Office 2019. If you’re uninstalling previous versions of Office products that were installed with Windows Installer (MSI), the Office Deployment Tool can remove most of those products for you as part of the installation of Office 2019. For more information, see Remove existing versions of Office before installing Office 2019.

Additional information

• Office Professional Plus 2019 includes Access, Excel, OneNote, Outlook, PowerPoint, Publisher, Word, and Skype for Business.
• Access and Publisher aren't available for devices running macOS.
• There isn’t a new 2019 version of OneNote, but a version of OneNote is installed with Office 2019. For more information, see Deployment guide for OneNote.
• All products in the Office 2019 are available in both 32-bit and 64-bit versions. 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.
• After downloading the installation files, internet access isn’t required to install, activate, or use Office 2019.
• There isn’t a 2019 version of SharePoint Designer or InfoPath. The last version for both products is 2013.
• Volume licensed versions of Office 2019 aren't supported on Windows 10 in S mode or when using Windows Defender Application Control (WDAC).

Related articles

With the Office Deployment Tool (ODT), you can download and deploy Microsoft 365 Apps 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. This article covers all the available options in the tool. To learn how to use the tool itself, see Overview of the Office Deployment Tool.

Note

Best practice: The options in this article show the XML elements and attributes in the configuration file. 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 information, see Overview of the Office Customization Tool.

Example of a standard configuration file

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 32-bit English edition of Office, or you can edit the file to install the 32-bit English edition of Office with the EULA automatically accepted and without Publisher.

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 and saving it with a name of your choosing. Use the file to modify the XML elements and attributes and use the rest of this article to learn more details about each of the elements and attributes.

This configuration file includes the most-commonly used elements and attributes, and can be used to download and install Office on a client computer

Note

The Logging element is no longer supported as a configuration option for the Office Deployment Tool. Log files can be found in the %temp% folder.

Add element

Defines the products and languages to download or install

Example

SourcePath attribute (part of Add element)

Optional.

Defines the location of the Office installation files. If the ODT is run in download mode, defines where to save the files. If not included, the ODT will look for installation files in the same folder as the tool, and then use the Office Content Delivery Network (CDN). If not included and the ODT is run in download mode, the Office installation files are downloaded to the same folder as the tool.

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.

Example values:

• SourcePath='servershare'
• SourcePath='c:preloadoffice'

Version attribute (part of Add element)

Optional. Defaults to the latest version available if not specified.

When you use the Version attribute, we recommend including the Channel attribute as well. If you don't include the Channel attribute, the default channel will be used, which might not match the specified version.

If Microsoft 365 Apps is already installed on a device, you can use Version='MatchInstalled' to install the same version of Office, even if a newer version is available. This setting can make it easier to add language packs or Visio and Project without updating Office to a newer version.

Example values:

• Version='16.0.8201.2193'
• Version='MatchInstalled'

OfficeClientEdition attribute (part of Add element)

Optional.

Defines whether the 32-bit or 64-bit edition of Microsoft 365 Apps is downloaded or installed. If Office is not installed on the device and OfficeClientEdition is not specified, the ODT will default to the 64-bit edition, unless the device is running a 32-bit edition of Windows or has less than 4 GB RAM. If Office is installed and OfficeClientEdition not specified, the ODT will match the architecture of the existing installation of Office. If Office is installed and OfficeClientEdition is specified, then it must match the already installed architecture. If it doesn't, the installation will fail, since mixed architectures are not supported.

Allowed values:

• OfficeClientEdition='64'
• OfficeClientEdition='32'

Channel attribute (part of Add element)

Optional.

Defines which channel to use for installing Office. If Office is not installed on the device, the default setting for the Channel attribute is Current. If Office is installed on the device and the channel attribute is not specified, the ODT will match the channel of the existing installation.

This value determines the channel to be installed, regardless of an optionally specified update channel in the Updates element or via Group Policy Setting. If there is such setting with a different update channel, the channel switch is performed after the installation during the next update cycle. For more information, see Change the Microsoft 365 Apps update channel.

For more information about update channels, see Overview of update channels for Microsoft 365 Apps.

Allowed values:

• Channel='BetaChannel'
• Channel='CurrentPreview'
• Channel='Current'
• Channel='MonthlyEnterprise'
• Channel='SemiAnnualPreview'
• Channel='SemiAnnual'

Note

• To use these attribute values, you need to be using at least version 16.0.12827.20268 of the Office Deployment Tool, which was released on Tuesday June 9, 2020.
• Previous allowed values for each update channel can still be used, which means you don't have to update your older configuration XML files.
• Beta Channel (sometimes referred to as Insider Fast) is not a supported build so should only be used in test environments and by a small group of select users, such as IT staff or application developers.

If you're deploying Office Professional Plus 2019, which is a volume licensed version of Office, there is a different update channel you need to use: PerpetualVL2019. For more information, see Update channel for Office 2019.

DownloadPath attribute (part of Add element)

Optional. Defaults to the CDN if not specified.

Defines where the installation files are downloaded from when running ODT in download mode. Most commonly used to distribute specific languages and products for Office from a central location on your network to another location. Note that you must specify a version when using DownloadPath, as shown in the example.

Example values:

• DownloadPath='serverashare'

Example

AllowCdnFallback attribute (part of Add element)

Optional. Defaults to False if not specified.

To use the Office CDN as a backup source for language packs, include the 'AllowCdnFallback' attribute in the configuration file, as shown in the example.

When installing languages, the ODT looks first for source files in the location specified in the SourcePath attribute. If the language pack isn't available at that location and the AllowCdnFallback setting is set to True, then the ODT will use source files from the Office CDN.

Allowed values:

• AllowCdnFallback='True'
• AllowCdnFallback='False'

Example

MigrateArch attribute (part of Add element)

Optional. Defaults to False if not specified.

If set to TRUE, then your existing installation of Microsoft 365 Apps will be changed to the architecture (sometimes referred to as the bitness) that is specified in the OfficeClientEdition attribute. For example, you can use this to change a 32-bit installation of Microsoft 365 Apps to a 64-bit installation.

For more information about using MigrateArch, see Change a Microsoft 365 Apps installation from 32-bit to 64-bit.

OfficeMgmtCOM attribute (part of Add element)

Optional. Defaults to False if not specified.

For Configuration Manager to be able to manage Microsoft 365 Apps updates, an Office COM object needs to be enabled on the computer where Office is installed. If set to TRUE, the Office COM object takes commands from Configuration Manager to download and install client updates. When the Office COM object is enabled, the Update Now option on the Account page for Microsoft 365 Apps is automatically disabled for client devices.

For more information, see Manage updates to Microsoft 365 Apps with Microsoft Endpoint Configuration Manager.

Allowed values:

• OfficeMgmtCOM='True'
• OfficeMgmtCOM='False'

Example

Product element

Defines which products to download or install. If you define multiple products, the products are installed in the order in the configuration file. The first product determines the context for the Microsoft Office First Run Experience.

You can also use the Product element to add language packs to existing installations of Microsoft 365 Apps. For more information, including an example configuration file, see Deploy languages to existing installations of Microsoft 365 Apps.

Example

ID attribute (part of Product element)

Required.

Defines the ID of the product to download or install.

Example values:

• ID='O365ProPlusRetail'
• ID='VisioProRetail'
• ID='ProjectProRetail'

Microsoft Office Proplus 2019

For a list of all supported product IDs, see Product IDs that are supported by the Office Deployment Tool for Click-to-Run

MSICondition attribute (part of Product element)

Optional.

Allows you to control the installation of an Office product, as specified by the ID attribute, based on whether a particular MSI-based Office product is already installed on the device. For example, if an MSI-based version of Project Professional is already installed on the device, then install Project Online Desktop Client.

You can specify any Office product that was installed by Windows Installer (MSI), but MSICondition is most commonly used for Project or Visio installations. 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 2007, 2010, 2013, and 2016 versions of the Office product that you specify. But, you can't specify a particular version. For example, you can't have MSICondition look specifically for Visio Standard 2013. MSICondition will look for all MSI-based installations of Visio Standard, including Visio Standard 2007, Visio Standard 2010, Visio Standard 2013, and Visio Standard 2016.

The value that you specify for the MSICondition attribute is the Setup ID that is found in the Setup.xml file in the {product}.WW folder of the installation files for your existing version of the Office product. For example, the Setup.xml file for Visio Professional 2016 is found in the VisPro.WW folder. You can specify multiple types of an Office product, separated by a comma. For example, you can specify 'PrjStd,PrjStdR,PrjPro,PrjProR' to look for installations of Project Standard or Project Professional, either volume licensed or retail.

Note

• We recommend that you remove the existing MSI-based Office products as part of installing the products specified in your XML file. To remove existing MSI-based products, use the RemoveMSI element.

Example of MSICondition attribute

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. Also, Project Standard will be removed from the device as part of the installation of Project Online Desktop Client.

Language element

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.

Example

ID attribute (part of Language element)

Required.

Defines the ID of the language to download or install.

Example values

• ID='en-us'
• ID='ja-jp'
• ID='MatchOS'
• ID='MatchPreviousMSI'
• ID='MatchInstalled'

For a list of all languages, see Languages, culture codes, and companion proofing languages.

For more information about MatchPreviousMSI, see Remove existing MSI versions of Office when upgrading to Microsoft 365 Apps.

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. To help address this issue, we recommend that you specify a backup language and allow the ODT to use the Office CDN for missing files. To do so, use the Fallback attribute and AllowCdnFallBack attribute.

MatchInstalled can be used only if there is at least one Click-to-Run product already installed. It can't be used with the /download switch for the ODT. For more information about MatchInstalled, see Overview of deploying languages and Build dynamic, lean, and universal packages for Microsoft 365 Apps.

Fallback attribute (part of Language element)

Optional.

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.

Example values:

• Fallback='en-us'
• Fallback='ja-jp'

TargetProduct attribute (part of Language element)

Optional.

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 there is no TargetProduct specified with MatchInstalled, the ODT will attempt to match the same Product ID that the Language tag belongs to in the configuration file. For example, if you are using MatchInstalled while installing 'VisioProRetail' without a TargetProduct, ODT will attempt to match the already installed languages for this product.

Example values:

Display element

Defines what the user sees when Office is installed.

Example

Level attribute (part of Display element)

Optional. Default is set to Full if not specified.

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.

Allowed values:

• Level='None'
• Level='Full'

AcceptEULA attribute (part of Display element)

Optional. Defaults to FALSE if not specified.

If AcceptEULA is set to TRUE, the user does not see a Microsoft Software License Terms dialog box. If this attribute is set to FALSE or is not included, the user may see a Microsoft Software License Terms dialog box. We recommend that administrators set AcceptEULA to TRUE.

Allowed values:

• AcceptEULA='TRUE'
• AcceptEULA='FALSE'

Note

If you deploy a version of Office before Version 1803, this setting will be applied only if you install with the user's account. Microsoft Endpoint Configuration Manager and other software distribution tools that use the SYSTEM account for installation will not apply the setting.

ExcludeApp element

Defines which Microsoft 365 Apps products should not be installed. OneDrive is automatically installed when you install Microsoft 365 Apps or install individual applications, such as Word, Excel, PowerPoint, Publisher, Visio, or Skype. If you don't want OneDrive installed with those applications, use the ExcludeApp element to remove it. For more information, see Exclude OneDrive when installing Microsoft 365 Apps or other applications.

Example

If a configuration file with ExcludeApp is used to install Office on a device that already has Microsoft 365 Apps installed, the ExcludeApp setting is treated differently based on the list of languages:

• If the list of languages in the configuration file includes all the installed languages, then the ExcludeApp setting in the file replaces any existing ExcludeApp setting on the device. This is also true if the list of languages in the configuration file includes both all the installed languages and additional languages.
• If the list of languages in the configuration file doesn't include all the installed languages, then the ExcludeApp setting in the configuration file will be combined with the ExcludeApp setting on the device.

ID attribute (part of ExcludeApp element)

Required.

Defines the ID of the product that should not be installed.

Allowed values:

• ID='Access'
• ID='Excel'
• ID='Groove'
• ID='Lync'
• ID='OneDrive'
• ID='OneNote'
• ID='Outlook'
• ID='PowerPoint'
• ID='Publisher'
• ID='Teams'
• ID='Word'

For OneDrive for Business, use Groove. For Skype for Business, use Lync.

For more information about Microsoft Teams, see Deploy Microsoft Teams with Microsoft 365 Apps.

Property element

Defines certain Office behaviors and properties.

Example

Name attribute (part of Property element)

Required.

Defines the specific property whose value you want to set.

Value attribute (part of Property element)

Defines the value of the named property.

AUTOACTIVATE property (part of Property element)

Office Proplus 2019 Retail Product Key Free

Optional. Default is 0 if not specified.

Because Microsoft 365 Apps is set to activate automatically, you should not set this property for Microsoft 365 Apps products. For other products, you can set AUTOACTIVATE to 1 to have the product activate automatically.

Allowed values:

• Property Name='AUTOACTIVATE'Value='0'
• Property Name='AUTOACTIVATE'Value='1'

FORCEAPPSHUTDOWN property (part of Property element)

Optional. Default is FALSE if not specified.

When set to TRUE, forces any apps that are blocking the install of Office to shut down. Data loss may occur.

Allowed values:

• Property Name='FORCEAPPSHUTDOWN'Value='FALSE'
• Property Name='FORCEAPPSHUTDOWN'Value='TRUE'

PACKAGEGUID property (part of Property element)

Optional.

By default, App-V packages created by the ODT share the same App-V Package ID. Administrators can use PACKAGEGUID to specify a different Package ID. This allows you to publish multiple App-V packages of Office to an App-V Management Server. But, this doesn't enable you to deploy more than one Office App-V package to a single computer. You can use the ODT to create App-V packages for Microsoft 365 Apps. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported.

The Package ID must follow the format of the example and can only use these characters: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F

If you use any other characters, the App-V package is created with the default Package ID.

Example values:

• Property Name='PACKAGEGUID'Value='12345678-ABCD-1234-ABCD-1234567890AB'

SharedComputerLicensing property (part of Property element)

Optional. Default value is 0 if not specified.

Set SharedComputerLicensing to 1 if you deploy Microsoft 365 Apps to shared computers by using Remote Desktop Services.

For more information, see Overview of shared computer activation for Microsoft 365 Apps.

Allowed values:

• Property Name='SharedComputerLicensing' Value='0'
• Property Name='SharedComputerLicensing' Value='1'

SCLCacheOverride property (part of Property element)

Optional. Default value is 0 if not specified.

Set SCLCacheOverride to 1 if you're using shared computer activation and you want to roam the licensing token. Use in conjunction with SCLCacheOverrideDirectory. This is only needed if you choose to move the licensing token from its default location. For more information, see Overview of shared computer activation for Microsoft 365 Apps.

Allowed values:

• Property Name='SCLCacheOverride' Value='0'
• Property Name='SCLCacheOverride' Value='1'

SCLCacheOverrideDirectory property (part of Property element)

Optional.

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. Use in conjunction with SCLCacheOverride. This is only needed if you choose to move the licensing token from its default location.

For more information, see Overview of shared computer activation for Microsoft 365 Apps.

Example values:

• Property Name='SCLCacheOverrideDirectory' Value='%appdata%Microsoft'
• Property Name='SCLCacheOverrideDirectory' Value='servershare%username%'

DeviceBasedLicensing property (part of Property element)

Optional. Default value is 0 if not specified.

Defines the Office licensing mode for device-based activation. For more information, see Device-based licensing for Microsoft 365 Apps for enterprise.

Allowed values:

• Property Name='DeviceBasedLicensing' Value='1'
• Property Name='DeviceBasedLicensing' Value='0'

PinIconsToTaskBar property (part of Property element)

Optional. The default value is True if not specified.

Defines whether shortcut icons for Office products are added to the Windows taskbar in Windows 7 and 8.1. 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.

Allowed values:

• Property Name='PinIconsToTaskbar'Value='FALSE'
• Property Name='PinIconsToTaskbar'Value='TRUE'

Note

Microsoft 365 Apps is no longer supported on Windows 7. For more information, see Windows 7 end of support and Microsoft 365 Apps.

Remove element

Defines which products and languages to remove from a previous installation of Microsoft 365 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. In that case, the ODT automatically discovers and removes all installed languages for the product.

Minitool partition wizard 7 portable. For more information, see Overview of the Office Deployment Tool.

Example

All attribute (part of Remove element)

Optional. The default value is FALSE if not specified.

If set to TRUE, all Microsoft 365 Apps products and languages will be removed, including Project and Visio.

Allowed values:

• All='FALSE'
• All='TRUE'

Updates element

Defines how Office is updated after it's installed.

Example

Enabled attribute (part of Updates element)

Optional. The default value is TRUE if not specified.

If set to TRUE, Office will check for updates.If set to FALSE, Office won't check for updates, but the user can check for updates by going to File > Account > Update Options > Update Now.

Allowed values:

• Enabled='TRUE'
• Enabled='FALSE'

UpdatePath attribute (part of Updates element)

Optional. Defaults to the CDN if not specified.

Defines where the updates for Office come from. UpdatePath can specify a network, local, or HTTP path of a source for Office installation files. Environment variables can be used for network or local paths.

If you use Group Policy with the Administrative Template files (ADMX/ADML) for Office, you can set UpdatePath by using the Update Path policy setting. You can find this policy setting under Computer ConfigurationPoliciesAdministrative TemplatesMicrosoft Office 2016 (Machine)Updates.

Example values:

• UpdatePath='servershare'
• UpdatePath='C:PreloadOffice'
• UpdatePath='http://internalApps/Office/'

TargetVersion attribute (part of Updates element)

Optional. Defaults to the latest version from the specified update path.

Defines which version Office updates to. If TargetVersion is set to a specific build number, Office attempts to update to that version.

If you use Group Policy with the Administrative Template files (ADMX/ADML) for Office, you can set TargetVersion by using the Target Version policy setting. You can find this policy setting under Computer ConfigurationPoliciesAdministrative TemplatesMicrosoft Office 2016 (Machine)Updates.

Example values:

• TargetVersion='15.1.2.3'
• TargetVersion='

Deadline attribute (part of Updates element)

Optional.

Defines a deadline by which updates must be applied. The deadline is specified in Coordinated Universal Time (UTC). You can use Deadline with Target Version to make sure that Office is updated to a particular version by a particular date. We recommend that you set the deadline at least a week in the future to allow users time to install the updates.

Prior to the deadline, users receive multiple reminders to install the updates. If Office isn't updated by the deadline, users see a notification that the updates will be applied in 15 minutes. This gives users the opportunity to save the Office documents that they are working on and to close any Office programs that are open. If users don't close the Office programs, the programs are closed automatically when the 15 minutes are up, which might result in data loss.

After the Office programs are closed, the updates are applied automatically. The deadline only applies to one set of updates. If you want to use a deadline to make sure that Office is always up to date, you must change the deadline every time a new update for Office is available.

To use this attribute, Office must be running at least Service Pack 1 (version 15.0.4569.1507). If you use Group Policy with the Administrative Template files (ADMX/ADML) for Office, you can set Deadline by using the Update Deadline policy setting. You can find this policy setting under Computer ConfigurationPoliciesAdministrative TemplatesMicrosoft Office 2016 (Machine)Updates.

Example value:

• Deadline='05/16/2014 18:30'

Channel attribute (part of Updates element)

Optional. The default is Current.

Defines which channel to use for updating Office after it is installed. There are two channel attributes: the channel for the Add element is used to specify an update channel while installing Office, and the channel for the Updates element is used to change the channel for an existing installation of Office.

For more information about update channels, see Overview of update channels for Microsoft 365 Apps.

If you use Group Policy with the Administrative Template files (ADMX/ADML) for Office, you can set Channel by using the Update Channel policy setting. You can find this policy setting under Computer ConfigurationPoliciesAdministrative TemplatesMicrosoft Office 2016 (Machine)Updates. If enabled, this Group Policy setting takes precedence over the Channel value set by using the Office Deployment Tool.

Allowed values:

• Channel='BetaChannel'
• Channel='CurrentPreview'
• Channel='Current'
• Channel='MonthlyEnterprise'
• Channel='SemiAnnualPreview'
• Channel='SemiAnnual'

Note

• To use these attribute values, you need to be using at least version 16.0.12827.20268 of the Office Deployment Tool, which was released on Tuesday June 9, 2020.
• Previous allowed values for each update channel can still be used, which means you don't have to update your older configuration XML files.
• Beta Channel (sometimes referred to as Insider Fast) is not a supported build so should only be used in test environments and by a small group of select users, such as IT staff or application developers.

If you're deploying Office Professional Plus 2019, which is a volume licensed version of Office, there is a different update channel you need to use: PerpetualVL2019. For more information, see Update channel for Office 2019.

RemoveMSI element

Optional.

Specifies whether any 2007, 2010, 2013, or 2016 versions of Office, Visio, and Project that were installed using Windows Installer (MSI) are uninstalled from the computer prior to the installation of the specified product, such as Microsoft 365 Apps.

We recommend that you uninstall any previous versions of Office before installing Microsoft 365 Apps. For more information about using RemoveMSI, see Remove existing MSI versions of Office when upgrading to Microsoft 365 Apps.

IgnoreProduct attribute (part of RemoveMSI element)

Optional.

If an ID is specified, that Windows Installer (MSI) product won't be uninstalled from the computer.

Example values:

• IgnoreProduct
• IgnoreProduct

AppSettings element

Optional.

Defines application preferences for Microsoft 365 Apps, including VBA Macro notifications, default file locations, and default file format. To create a configuration file with application preferences, we recommend you use the Office Customization Tool for Click-to-Run, a web application with a full user interface. You can also use the tool to learn more about the available application preferences.

For more information about application preferences, see Apply application preferences and Apply application preferences to an existing installation of Office.

Example

Related articles