Overview
This is the tool that anyone who deploys Office more than twice ends up using. It puts a proper interface on the deployment mechanism that Microsoft ships as a command line utility, so choosing the release, the channel, the architecture, the applications and the languages becomes a set of checkboxes instead of a hand written configuration file.
The application list is the headline feature. A default suite install drops eight or nine applications on a machine whether they are wanted or not, and this lets a deployment be exactly Word, Excel and Outlook, or the full set, or anything in between. Add a language, remove one, switch a channel, or repair an existing install, all against a suite that is already on the machine without reinstalling it.
It also manages the state of what is installed. Current release, channel, installed applications and licensing state are all read from the machine and shown on one panel, and the same panel handles cleanup of leftover components from a previous suite. Everything can be exported as a configuration file for silent reuse, which is why it turns up in so many small deployment scripts.
What it does well
Per-application deployment
Choose exactly which applications install rather than accepting the full suite, and change the selection later without a reinstall.
Every release and channel
Perpetual and subscription lines, all supported channels, both architectures, selected from one panel.
Language management
Interface and proofing languages added or removed against an existing install, without pulling the whole suite again.
State and repair
Reads the current release, channel, applications and licensing state, and runs quick or full repairs from the same view.
Configuration export
Every choice exports to a configuration file for silent, repeatable deployment on other machines.
Changes in this build
- Deployment panel reorganised with search across applications and languages.
- Cleanup routine extended for leftover store based installs.
- Download resume added so an interrupted transfer continues.
- Configuration export now records channel, architecture and exclusions together.
- Interface language files updated across the supported set.
What is in the package
- Office Tool Plus, portable build and installer
- Deployment and channel selection panel
- Language management module
- Cleanup and repair routines
- Multilingual interface files, 12 languages
System requirements
| Processor | 1 GHz or faster, x86 or x64 |
| Memory | 2 GB minimum |
| Graphics | Not applicable |
| Storage | 150 MB free plus space for the Office payload |
| Display | 1280 x 720 minimum |
| Network | A working connection, the Office payload is fetched during deployment |
Installation
- Extract the portable build, or run the installer if you want it in the start menu.
- Run it as an administrator so it can read and change the install state.
- Use the cleanup panel first if a broken suite is already present.
- Pick the release, channel, architecture, applications and languages in the deployment view.
- Start the deployment and export the configuration before closing the panel.
Before you start
It needs a connection during deployment, the payload is downloaded rather than bundled.
Mixing architectures across applications is not supported by the underlying mechanism.
Keep the exported configuration, it turns a twenty minute job into a one line command next time.
Questions about this title
Does it install Office itself?
It drives the official deployment mechanism, so the files are the same ones a normal install produces.
Can I add a language later?
Yes, languages are managed against the existing install without reinstalling the suite.
Is there a portable build?
Yes, both a portable build and a normal installer are in the package.
Can it repair a broken install?
Yes, quick and full repair are both available from the state panel.
About this listing
This entry was checked on a clean install of Windows 7 / 8 / 10 / 11 before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.