Fix Office Deployment Tool Error 30088-1021 with Project and Visio
Question details
The user needs to resolve an installation failure when deploying Microsoft Office alongside Project and Visio on an RDS server.

- Product
- Microsoft Office, Project, Visio
- Device & OS
- not provided
- Scenario
- Deploying Microsoft Office with Project and Visio concurrently using the Office Deployment Tool (ODT) in a Remote Desktop Services (RDS) environment.
- Observed behavior
- The standard Office installation succeeds, but adding Project and Visio causes the deployment process to fail with error code 30088-1021.
Ensure you have administrative privileges on the target server and that you have backed up your current configuration.xml file before making any modifications.
Modify the ODT Configuration.xml File
Resolve the error by adjusting conflicting properties within the XML configuration file, such as AUTOACTIVATE and excluded applications.
Error 30088-1021 often triggers due to conflicting flags or incompatible channels in the configuration file when combining multiple Office products. Adjusting specific XML properties ensures a seamless deployment.
Open your `configuration.xml` file in a text editor. Unless you are providing a unique PIDKEY for Office, Project, and Visio individually, remove the `AUTOACTIVATE` attribute to prevent automatic activation conflicts during the deployment.
If Skype for Business is not required, explicitly exclude it by adding `<ExcludeApp ID="Lync" />` under your primary `<Product>` element. This reduces the risk of deployment overlaps.
Since this is an RDS server deployment, confirm that the shared computer licensing property is active. Ensure your file includes the line `<Property Name="SharedComputerLicensing" Value="1" />`.
Review your configuration file to ensure that the Update Channel, architecture (32-bit or 64-bit), and Windows version match exactly across the Office, Project, and Visio product blocks.

Skip Deployment Complexities with WPS Office
Configuring the Office Deployment Tool and troubleshooting XML errors can be tedious and time-consuming. WPS Office provides a hassle-free, highly compatible alternative for your document, spreadsheet, and presentation needs without complex server deployments.
- 1. Download the installer: Visit the official WPS Office website and click on the 'Free Download' button to get the setup file.
- 2. Run the setup: Double-click the downloaded executable file to launch the straightforward installation wizard.
- 3. Start using WPS Office: Once installed, open the application and immediately start creating or editing your existing Microsoft Office documents.

Frequently Asked Questions
Why does ODT error 30088-1021 only happen when adding Project or Visio?
This typically occurs because the configuration file contains conflicting update channels, mixes different installation technologies (MSI vs. Click-to-Run), or applies an AUTOACTIVATE command without the necessary individual product keys for the added software.
How do I configure my XML file for a Remote Desktop Services environment?
For RDS deployments, you must enable Shared Computer Licensing. You do this by inserting `<Property Name="SharedComputerLicensing" Value="1" />` into the configuration.xml file so that multiple users can access the software on the same server.
Can I install 32-bit Visio with 64-bit Microsoft Office?
No, Microsoft explicitly blocks mixing 32-bit and 64-bit architectures for Office products on the same machine. You must select either 32-bit or 64-bit for Office, Project, and Visio, and keep it consistent across all products.
Where can I find the Office Deployment Tool installation logs?
The ODT generates log files that provide more details on installation failures. You can find these logs in your temporary folder by pressing Win + R, typing `%temp%`, and looking for text files that start with your computer's name and include 'Office'.




