logo
search
Office Installation Errors

How to Silently Deploy Office LTSC 2021 with Office Deployment Tool

Chanuka GeekiyanageChanuka Geekiyanage Oct 23, 2026 868 views

Question details

The user needs to troubleshoot silent installations of Office LTSC Professional Plus 2021 through deployment wrappers like BigFix and understand the visibility of the Click-to-Run process.

How to Silently Deploy Office LTSC 2021 with the Office Deployment Tool
Product
Microsoft Office LTSC 2021
Device & OS
not provided
Scenario
Silently deploying Office LTSC 2021 across multiple endpoints using a configuration XML and deployment tools like BigFix.
Observed behavior
During deployment, the installation fails or hangs, and the Click-to-Run process does not appear as an individual visible process, unlike during a manual installation.
Before you start

Ensure you have the latest version of the Office Deployment Tool downloaded from Microsoft, and verify you have administrative privileges on the target machines for testing deployment scripts.

Solution 1Recommended

Validate XML Configuration and Test the Deployment Locally

Verify your configuration XML file for accuracy and test the installation outside of your deployment wrapper to isolate the issue.

During a managed or silent installation using the Office Deployment Tool, the primary visible process will often be setup.exe. The Click-to-Run technology may run differently, operate hidden in the background, or finish extremely quickly. Not seeing the Click-to-Run process during a BigFix deployment is expected behavior.

To troubleshoot failures, you must rule out issues caused by the deployment wrapper by testing the setup command locally on a machine.

1
Generate a valid XML configuration

Navigate to the Office Customization Tool at config.office.com. Configure your deployment settings for Office LTSC Professional Plus 2021, ensuring the correct update channel is selected, and export the validated XML file.

2
Run the ODT command locally

Copy the downloaded Office Deployment Tool (setup.exe) and your new XML file to a local folder on a test machine (e.g., C:\ODT).

3
Execute the installation

Open an elevated Command Prompt as Administrator, navigate to your ODT folder, and run the command 'setup.exe /configure yourconfig.xml' manually without using BigFix.

4
Review installation logs

If the installation still fails, navigate to the %temp% directory (or the system temp directory, depending on the context) and review the generated Office setup log files for specific error codes.

Deployment wrapper isolation: If the manual local installation succeeds but fails via BigFix, the issue lies within the BigFix deployment configuration, system context execution, or network share permissions.
Free Microsoft Office alternative

Try WPS Office for Easier Enterprise Deployment

Avoid complex XML configurations and Office Deployment Tool troubleshooting. WPS Office provides a lightweight, highly compatible, and easy-to-deploy alternative to Microsoft Office, ensuring seamless migration for enterprise environments.

  1. 1. Download the enterprise installer: Obtain the standard WPS Office installer package suitable for mass deployment.
  2. 2. Apply standard silent switches: Use standard command-line parameters (like /S for silent install) without needing dedicated customization tools.
  3. 3. Deploy via your preferred wrapper: Push the lightweight package effortlessly through BigFix, SCCM, or Microsoft Intune to all endpoint devices.
No complex XML configuration or Office Deployment Tool requiredFully compatible with Microsoft Word, Excel, and PowerPoint formatsLightweight installation package that deploys silently with simple command line switchesCost-effective and familiar user interface for immediate user adoption
microsoft office alternative - wps office

Frequently Asked Questions

Why doesn't the Click-to-Run process show during silent Office deployment?

In silent or managed deployments, the Office Deployment Tool executes via setup.exe under system context. The Click-to-Run service often operates in the background or completes its initialization rapidly, leaving only setup.exe visible in the Task Manager.

Where can I find the Office Deployment Tool log files?

By default, the ODT generates log files in the executing user's %temp% directory. If deployed via a system account wrapper like BigFix, check the system temporary directory (e.g., C:\Windows\Temp) for the setup logs.

How do I correctly generate a configuration XML file for Office LTSC?

It is highly recommended to use the web-based Office Customization Tool at config.office.com. This graphical interface ensures your XML syntax is accurate, includes the correct Product IDs, and specifies the PerpetualVL2021 update channel required for LTSC.

Can I deploy Office LTSC 2021 using Microsoft 365 deployment XML files?

No. While both utilize the Office Deployment Tool, Office LTSC 2021 has distinct configuration requirements, including a different update channel and licensing token structure. Using Microsoft 365 XML files will cause the deployment to fail or install the wrong product.