🚀 Overview: Deploying Office LTSC 2021 Outside of VLSC

For IT Administrators, the transition to Office LTSC (Long-Term Servicing Channel) 2021 marks a shift in how volume-licensed software is acquired and deployed. Unlike previous versions where installers were readily available as ISO files in the Volume Licensing Service Center (VLSC), Office LTSC 2021 utilizes the Click-to-Run (C2R) installation technology. Consequently, installation files must be pulled directly from the Office Content Delivery Network (CDN) using the Office Deployment Tool (ODT).

This guide provides a comprehensive walkthrough for environment preparation, configuration file generation, and execution of the deployment via the Command Line Interface (CLI).

---

⚙️ Key Technical Details

Before beginning, ensure you are targeting the correct products and utilizing the required version of the deployment utility.

📦 Supported Products

• Office LTSC Professional Plus 2021
• Office LTSC Standard 2021
• Visio LTSC Professional 2021
• Visio LTSC Standard 2021
• Project Professional 2021
• Project Standard 2021

🛠️ Phase 1: Preparing the Office Deployment Tool (ODT)

1. Download the Utility: Navigate to the Microsoft Download Center and acquire the Office Deployment Tool.

Note: You must use version 16.0.14326.20404 or later (released Sept 17, 2021) to support LTSC 2021.

2. Extraction: Launch the downloaded executable, accept the license terms, and extract the contents to a dedicated folder on your local machine (e.g., a folder on your Desktop).

📄 Phase 2: Generating the Configuration XML

Admins can either use the pre-defined configuration-Office2021Enterprise.xml included in the ODT or create a custom profile using the Office Customization Tool (OCT).

• Architecture: 64-bit is generally recommended unless specific 32-bit legacy add-ins are required.
• Update Channel: This must remain set to Office LTSC 2021 Perpetual Enterprise.
• Application Selection: Use the toggles to exclude specific apps (e.g., Publisher or Access) from the deployment bundle.
• Licensing & Activation:
  • MAK: Enter your specific Multiple Activation Key and toggle Autoactivate to On.
  • KMS: If your infrastructure uses the Key Management Service, select the KMS Client Key option.
• Export: Once configured, export the file as Configuration.xml and place it in the same folder as the ODT (setup.exe).

💻 Phase 3: Command Line Execution

To initiate the installation, you must use an elevated Command Prompt (Run as Administrator).

1. Navigate to Source: Use the Change Directory command to point to your extraction folder:

cd <file path>

2. Deployment Command: Execute the following command to begin the local installation:

Setup /configure configuration.xml

3. Pre-downloading (Optional): If you are deploying to machines with restricted or slow internet access, use the following command first to download the source files to your local directory before distributing them:

Setup /download configuration.xml

🔑 Phase 4: Manual Activation (Fallback)

If automatic activation fails during deployment, manual intervention may be required on the client machine:

1. Open any Office application (Word, Excel, etc.).
2. Navigate to File > Account.
3. Select Change Product Key and enter your 25-character volume license key.

---

⚠️ Impact

🛡️ Administrative Workload: Admins must shift from traditional MSI-based deployments to XML-based configuration management. This requires a deeper understanding of ODT switches and the CDN-based delivery model.

🌐 Network Traffic: Because files are pulled from the CDN, simultaneous deployments across a large number of endpoints can impact network bandwidth unless a local network share or Setup /download strategy is implemented.

📅 Lifecycle Management: Since this is LTSC, the “Perpetual Enterprise” channel ensures the version remains stable without receiving new features, providing the “set-and-forget” environment required for regulated or offline workstations.

Official Source: Read the full article on Microsoft.com