Office Tool

About Office Tool

Office Tool is a front end for the deployment machinery the office suites already use, wrapped in an interface that a person can actually operate. Rather than hand writing a configuration file and driving a command line utility, the whole thing becomes a set of dropdowns: which generation, which channel, which architecture, which language, which applications.

The component picker is the reason most people reach for it. A deployment can include only the applications that are wanted and leave everything else off the disk, so a machine that needs a word processor and a spreadsheet does not end up carrying a database, a publishing tool and a communications client it will never open.

It handles the awkward states as well as the clean ones. A partially removed suite, a mismatched architecture, a leftover licence state or a machine carrying two generations at once can all be cleaned up from the tool before a fresh deployment runs, which saves the reinstall that these situations usually turn into.

Activation and channel management sit in the same window. The tool reports the current licence state, applies the appropriate one for the deployed generation, and can pin a machine to a servicing channel so it stops jumping to a newer feature build without warning. It is portable, so nothing is installed to run it.

What is included in this build

• Component picker choosing exactly which applications get deployed
• Support for the current and previous office suite generations
• Architecture, language and update channel selected before deployment
• Cleanup pass for partial removals, mismatched installs and leftover states
• Licence status readout with activation applied from the same window
• Channel pinning so a machine stays on a chosen servicing build
• Offline deployment from a previously downloaded package set
• Fully portable, nothing installed to run the tool itself

Changed in version 16.4.0

• Support added for the newest suite build numbers
• Improved cleanup of installs left in a partially removed state
• Faster package downloads through parallel connections
• Additional interface languages
• Clearer reporting when a deployment fails partway through

Installation walkthrough

These steps assume a clean machine. If a previous release of the same application is present, deal with that first, since an overlapping install is the most common cause of a setup that stops halfway.

1. Disable real-time protection before extracting, since deployment tooling is flagged on category.
2. Extract the archive to any folder, including one on a removable stick.
3. Run the executable as administrator.
4. Run the cleanup pass first if the machine already carries a suite install.
5. Pick the generation, architecture, language and applications, then start the deployment.

System requirements and file details

Frequently asked about this title