-->
The Office Deployment Tool (ODT) is a command-line tool that you can use to 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.
Office 365 one click only installs 32 bit version issue. Archived Forums Office 2016, Office 2019, and Office 365 ProPlus - Planning, Deployment, and Compatibility. On the other hand, the 32-bit edition of Office is limited to 2 GB of virtual address space, and this space is shared by Excel, the workbook, and add-ins that run in the same process. (Worksheets smaller than 2 GB on disk might still contain enough data to occupy 2 GB or more of addressable memory.). We all know Microsoft Office available in the flavor of 32-bit and 64-bit. The difference between them is the data processing capability where 64-bit is superior compared to 32-bit. It is important to know which Office version that we have to make sure it fits the work requirement that we need to do or compatibility with plug-ins that we want.
If you're not an enterprise administrator and are looking to install Office 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.
Tip
For more information about what changes are in the latest version of the ODT, see Release history for Office Deployment Tool.
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 install the 64-bit English edition of Office with the EULA automatically accepted. 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 information, 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 Microsoft 365 Apps products and languages, use download mode. Example:
setup.exe /download downloadconfig.xml. 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 Microsoft 365 Apps 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.xmlTo apply new application preferences to client computers that already have Microsoft 365 Apps installed, use customize mode. This mode will apply only application preferences, without changing any other deployment settings. Example:
setup.exe /customize preferencesconfig.xmlTo create an App-V package from the downloaded Microsoft 365 Apps 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 Microsoft 365 Apps
Follow these steps to download installation files for Microsoft 365 Apps 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 Microsoft 365 Apps for enterprise and the subscription version of the Visio desktop app 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 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% folder.
Download the installation files for Microsoft 365 Apps from a local source
You can use the Office Deployment Tool to download the installation files for Microsoft 365 Apps from a local source on your network. 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 Microsoft 365 Apps for enterprise from serverashare (the DownloadPath) to serverbshare (the SourcePath):
When using DownloadPath, you must specify a Version.
Install Microsoft 365 Apps
After you download Microsoft 365 Apps 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
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 installs a 32-bit English edition of Microsoft 365 Apps for enterprise 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. 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 saved. In the following example, the configuration file is named installconfig.xml:
setup.exe /configure installconfig.xml
You must have local administrator permissions on the client computer. You can run the executable from the client computer on which you want to install Office or you can put the ODT and the configuration file on a network share and run it from there. If you use a network share, make sure to pass the full network path for both the setup.exe and the configuration file to the command.
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% folder.
Update Microsoft 365 Apps
You can use the Office Deployment Tool to make updates to your client computers after installing Microsoft 365 Apps. There are two ways to make the updates:
Use the ODT to install Microsoft 365 Apps 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 Microsoft 365 Apps 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 scenario, including using Group Policy, see Choose how to manage updates to Microsoft 365 Apps.
Exclude or remove Microsoft 365 Apps applications from client computers
When installing Microsoft 365 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 365 Apps for enterprise applications except Publisher:
If you've already installed Microsoft 365 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 365 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 365 Apps for enterprise:
For more information about the options for excluding or removing apps, see Configuration options for the Office Deployment Tool.
Exclude OneDrive when installing Microsoft 365 Apps or other applications
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, as shown in the example.
Deploy multiple or matching languages
For details on deploying languages, see Overview of deploying languages for Microsoft 365 Apps.
Apply application preferences to Microsoft 365 Apps
As part of your deployment, you can define application preferences for Microsoft 365 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 365 Apps, but you include application preferences as part of your configuration file.
Office 365 32 Bit Installer Download
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 preferences alongside the standard deployment settings.
- Export the file.
- Follow the steps in Install Microsoft 365 Apps to deploy Office with the newly created configuration file.
In this example, the configuration file installs the 32-bit version of Microsoft 365 Apps for enterprise 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 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.
Apply application preferences to an existing installation of Microsoft 365 Apps
You can apply new application preferences to client computers that already have Microsoft 365 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.
- 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 created. In the following example, the configuration file is named installapppreferences.xml:
setup.exe /customize installapppreferences.xml
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.
Create an App-V package for Microsoft 365 Apps
In addition to downloading and deploying Microsoft 365 Apps, 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 that has 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 scenario, see Deploying Microsoft Office 2016 by Using App-V.
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 creates an App-V package from a 32-bit English edition of Microsoft 365 Apps for enterprise 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 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% folder.
Related articles
FINAL UPDATE: AUGUST 23, 2019.
Choose the bit-version that's best for you, but be careful about thinking one is always better than the other. If this doesn't make sense, then please read-on...
UPDATE: MARCH 5, 2019.
Office 365 32 Bit Outlook
Microsoft flipped the switch right back. 'The 32-bit version of Office is automatically installed unless you explicitly select the 64-bit version before beginning the installation process.' Again, we'll reiterate 32-bit Office is more seasoned than 64-bit Office. Link.
UPDATE: MARCH 1, 2019.
Microsoft recently/quietly flipped the switch. 'The 64-bit version of Office is automatically installed unless you explicitly select the 32-bit version before beginning the installation process.' Be that as it may, the other content herein remains valid. We've enhanced our software to support 64-bit Office editions, but we still recommend 32-bit Office for multiple reasons. 32-bit Office is unquestionably more broadly-compatible and more seasoned (and thus, less buggy) than 64-bit Office.
POSTED: JANUARY 21, 2019.
It is not uncommon to be puzzled by the differences and tradeoffs between 32-bit and 64-bit Office. We hope this page helps to lessen potential confusion and to rationalize the best-bit Office for you. Oh, and Office 2019 has an interesting twist in a world seemingly going cloud and perpetually changing.
Microsoft Windows permits one XX-bit Office to be installed at one moment in time on one computer. Either-bit Office may be installed on 64-bit Windows. They behave similarly, but 32-bit Office and 64-bit Office are literally different computer programs by appearance and under the hood.
Ms Office 365 Download
Here are pertinent characteristics:
64-bit Office can use more virtual address space ('memory') if needed, than can 32-bit Office.
64-bit Office and Office apps do not automatically run faster or slower than on 32-bit Office but slightly speed-wise they can differ. Multiple factors and dependencies are at play. Memory packet sizes (in bits...often among megabytes) change, memory needs for functions/subs/objects change, and Windows processing itself differs, but raw 'memory speed' doesn't change.
64-bit Office is not an upgrade to the 32-bit edition of the same version.
Except for .accde, Office app file formats (.xlsx, .docx, .accdb, .mdb, ...) are compatible with either-bit Office.
Office 2019, 365, 2016, 2013, and 2010 are available in 32-bit and 64-bit editions.
32-bit Office is the Default install for all Office versions that support a 64-bit edition.
Max memory use for a 32-bit Office app may be 2 gigabytes (GB), including the space needed by the app, any running add-ins, and the document file(s) being accessed. There are exceptions when running modern 32-bit Office on 64-bit Windows and when considering file size limitations in general:
32-bit Outlook .pst/.ost files are not limited to 2 GB. They are default limited to 50 GB according to Microsoft, and the limit can be increased or decreased.
32-bit Excel files are not limited to 2 GB. They are limited to 4 GB, according to Microsoft.
Whether running 64-bit Access or 32-bit Access, accdb and mdb database files are limited to 2 GB, according to Microsoft. Database design can somewhat work-around the 2 GB limit by linking to tables in other Access databases because each single table (of potentially dozens, hundreds, ...) can effectively push the 2 GB limit.
Whether running 64-bit Word or 32-bit Word, the maximum file size is limited to 32 MB for the total document text only. If the file contains graphics, the maximum file size can be larger than 32 MB, according to Microsoft.
Typically, 2 gigabytes (GB), which is 2048 megabytes (MB), is not a restrictive file size.
Starting in the 1990s Microsoft Windows operating system evolved from 16-bit (Windows 3.x / Windows 95) to 32-bit (Windows NT 3.1), and then later to 64-bit...for some with Windows XP but for most with Vista or Windows 7. Each new bit step permitted Windows to access and use more memory to manage running apps. Another step-up to 128-bit may not occur in our lifetimes.
Windows and Office are fully integrated. Each Office app has capabilities to extend its core functions. Sometimes called Add-ins, Macros, Controls, Automation Servers, Objects, or References (hereinafter, simply 'Tools'), each Office app can use a plethora of Microsoft and 3rd-party Tools to perform tasks.
As an external resource file, a Tool might be in the file form of .ocx, .dll, .exe, .xlam, .xla, .xll, or others, and multiple Tools (when bit-compatible) can be used by multiple Office apps in multiple Office app files.
Usually, a single 3rd-party Tool file is compatible with either 32-bit Office or 64-bit Office, but not both. For most 3rd-party Tools to work with both-bit Office, they must be developed and exist in two different bit version files (like Office). Furthermore:
There are more than 1000 free and commercial 32-bit Office Tools.
There are fewer 64-bit Office Tools, and nearly all such Tools exist in a 32-bit edition.
Most Tools are unhindered by a 2 GB memory limit to function for their purpose. As a result, the time to produce 64-bit editions are not necessarily pursued first, if at all. XX-bit Office isn't seamlessly 'backwards/forwards compatible' with respect to 3rd-party Tools.
Office 365 32 Bit
After three+ decades of development it appears that ever-expanding Office functionality is sunsetting. Microsoft Office 2019 is a PERPETUAL LICENSE version of Office and is available in 32-bit and 64-bit editions. That's right...a static, non-expiring, more-private, cloud-free, licensed version of Office is back from yesteryear 199X.
Whether you're on a remote drilling rig or performing any mission critical operation, reducing the potential for computer problems has value and a stable Office is less likely prone to glitches. Going forward, a fixed version of Office should be considered an option in the mix.
And as mentioned above, 32-bit is the Default Office edition install...
Their are potential tradeoffs between 64-bit and 32-bit Office. However, one is not necessarily better-at-all-things than the other by virtue of its existence.
The potential limitation of 64-bit Office is compatibility with a universe of resources.
The potential limitation of 32-bit Office is the inability to process atypically large files.
Office 365 32-bit Versus 64-bit
Microsoft licensing usually makes it easy to switch to the other-bit Office at any time.
Office 365 32 Bit To 64 Bit
Entities that prefer both-bit Office availability sometimes do so with Windows and either-bit Office running on a virtual machine server.
Here's the link to the above snip.