Overview
Office deployment is normally driven by a configuration file that nobody wants to write by hand. This tool is a window over that mechanism. You tick the applications, pick the channel, choose the architecture and the languages, and it builds the configuration and runs the deployment for you, pulling the payload from the official servers rather than from a repack.
The second half of the tool is licence management. It can install a product key, point a machine at a key management service, switch a licence between routes, and show exactly what licences are currently installed and which one is active. On a machine with a confused licence state left behind by something else, that inspection view is often the whole fix.
Deployment: choosing what actually installs
The application list is per component and independent, so a machine that needs a word processor and nothing else installs a word processor and nothing else. Architecture, update channel, interface languages and proofing tools are all chosen before anything downloads, and the resulting configuration can be saved as a file to reuse on other machines.
It can also modify an existing installation rather than replacing it. Adding an application, adding a language or moving between update channels all happen in place, with only the missing pieces downloaded. That is considerably faster than the usual approach of removing everything and starting again.
Licence management and inspection
The licence panel lists every product licence installed on the machine, which version it belongs to, which is active, and how it was licensed. That is information the Office interface itself will not show you plainly, and it is what tells you whether a machine has two conflicting licences fighting each other.
From there, keys can be installed or removed, a key management service address can be set with its port and renewal interval, and a licence can be converted between the retail and volume routes where the product supports it. Every action reports its result, and nothing is done silently.
Cleanup and troubleshooting
The cleanup tools remove a previous Office installation completely, including the registration leftovers that a normal uninstall leaves behind and that cause the next install to behave strangely. There is a scrub option for the cases where the normal removal will not complete, which is common on machines that have had several Office generations over the years.
For a failed deployment, the tool keeps a readable log of what the deployment engine reported rather than showing a numeric code, which usually points straight at the cause: a proxy blocking the download, a conflicting architecture already installed, or a channel that does not carry the product being requested.
What you get
- Per component selection for the whole Office application list
- Payload downloaded from the official servers rather than from a repack
- Architecture, update channel, interface and proofing language selection
- Configuration saved as a file for reuse across machines
- In place modification of an existing install without a full reinstall
- Licence inspection panel showing every installed licence and which is active
- Key install and removal, key management service configuration and route conversion
- Complete removal and scrub tools for previous Office installations
- Readable deployment log instead of numeric error codes
Inside the archive
- Office Tool Plus, both as a portable build and as an installer
- Deployment configuration presets for common setups
- Office removal and scrub utilities
- Language packs for the interface list shown above
- Notes on channel choice and licence routes
System requirements
| Operating system | Windows 7 or newer |
|---|---|
| Processor | Any x86 or x64 processor |
| Memory | 2 GB |
| Storage | 100 MB for the tool, plus space for the Office payload |
| Network | Required for deployment, optional for licence work |
| Privileges | Administrator |
Installing it
- Unpack the portable build or run the installer, whichever you prefer. Both behave identically.
- Add the folder as an antivirus exclusion, since the licence functions get flagged by category.
- Run it as administrator.
- Use the licence panel to look at the current state before changing anything.
- For a fresh deployment, run the removal tool on any previous Office first, then build your configuration.
Mirrors
| Route | Region | Note | State |
|---|---|---|---|
| Direct, primary | Europe | No wait, resumable | Online |
| Direct, secondary | Asia Pacific | No wait, resumable | Online |
| Torrent magnet | Global | Not needed at this size | Online |
Release history
- Product catalogue refreshed for the current server listing
- Licence panel now shows which of several licences is active
- Fixed the scrub tool leaving registration keys on very old installations
- In place modification no longer re downloads components already present
- Deployment log made readable instead of code based
- Proofing tool selection separated from interface language selection
- Configuration files made portable between machines
Questions about this release
Does it include Office itself?
No. It downloads the payload from the official servers based on the configuration you build, so what installs is the current official build.
Can it fix a machine with a confused licence state?
Usually. Look at the licence panel first, remove the licences that should not be there, then apply the one you want.
Is the portable build the same as the installer?
Yes, identical functionality. The portable build simply leaves nothing behind.
Why did my deployment fail?
Read the log rather than the code. It is nearly always a proxy blocking the download or an existing install with the other architecture.
Comments
Built a config with just Word, Excel and Outlook, saved it, used it on four machines. Exactly what I needed.
Scrub tool cleared out an Office 2013 mess that nothing else would remove. Then deployed clean.
Comments are read before they appear. If a build stops working, say so here and it gets rebuilt rather than quietly left up.
Licence panel showed two conflicting licences from an old install. Removed one and everything settled.