it

Office 2019 Volume Licensing Setup Guide

Deploying productivity suites across an organization requires a structured approach. Standard retail installations fall short when you're managing dozens or hundreds of workstations. Office 2019 volum

Office 2019 Volume Licensing Setup Guide
In this story

Deploying productivity suites across an organization requires a structured approach. Standard retail installations fall short when you're managing dozens or hundreds of workstations. Office 2019 volume licensing shifts control back to IT administrators, allowing bulk deployments and centralized license management via the Office Deployment Tool (ODT) and Key Management Service (KMS) or Multiple Activation Keys (MAK).

Unlike consumer versions tied to individual Microsoft accounts, volume licenses rely on Click-to-Run infrastructure combined with configuration XML files. You don't need physical installation media or manual logins on every desktop.


Prerequisites and Preparation

Before deploying Office 2019 Professional Plus or Standard across your network, gather the required tools and verify environment compatibility.

  • Operating System: Office 2019 requires Windows 10 or later. It won't install on older operating systems.
  • Administrative Access: You need domain admin or local administrator rights on target machines.
  • Microsoft Admin Center Access: Retrieve your GVLK or MAK keys from the Microsoft 365 Admin Center.
  • Network Share: Set up a shared directory if you plan to cache installation files locally to save internet bandwidth.

Clean up legacy software before starting. Run scripts or policies to remove older Windows Installer (MSI) versions of Office to prevent installation conflicts.


Step 1: Download and Extract the Office Deployment Tool

Microsoft uses the Office Deployment Tool (ODT) to manage downloads and installations for volume channels.

  1. Download the latest official Office Deployment Tool from Microsoft's download center.
  2. Run the executable file on your administrative workstation and extract the contents to a dedicated working folder (for example, C:\ODT).
  3. Inside the folder, you'll find setup.exe along with several sample XML configuration templates. Delete the sample XML files to keep your workspace clean.

Step 2: Configure the XML Deployment File

The configuration XML file dictates what gets installed, which architecture (32-bit or 64-bit) is used, and how activation happens. Create a new text file named configuration.xml in your ODT folder and populate it using a clean text editor like Notepad.

Here is a standard production configuration for Office Professional Plus 2019 using a MAK key:

<Configuration>
  <Add OfficeClientEdition="64" Channel="Perpetual2019">
    <Product ID="ProPlus2019Volume">
      <Language ID="en-us" />
      <ExcludeApp ID="Lync" />
    </Product>
  </Add>
  <Property Name="AUTOACTIVATE" Value="1" />
  <Updates Enabled="TRUE" />
  <Display Level="None" AcceptEULA="TRUE" />
  <AppSettings>
    <User键 Name="preventFirstRunExperience" Value="1" />
  </AppSettings>
</Configuration>

If your organization uses a local KMS server for activation instead of a MAK key, replace the product section with your Generic Volume License Key (GVLK) or configure automatic activation through your KMS host.


Step 3: Download Installation Files Locally

Instead of pulling installation files live across every client machine, download the core package to your local network repository first.

🔗 Read more: this guide
  1. Open an elevated Command Prompt and navigate to your working directory:
    cd /d C:\ODT
    
  2. Run the download command using your configuration file:
    setup.exe /download configuration.xml
    
  3. Wait for the process to complete. A folder named Office will appear in your directory containing the cab files and source data.

Step 4: Execute the Network Deployment

With the installation files cached locally, you can push the deployment to client endpoints. You can run this via script, group policy, or enterprise management tools like Microsoft Configuration Manager.

  1. Copy your ODT folder (setup.exe, configuration.xml, and the Office source folder) to a shared network path accessible by client machines, or distribute it locally.
  2. Open an elevated Command Prompt on the target machine.
  3. Run the installation command:
    setup.exe /configure configuration.xml
    
  4. Monitor Task Manager or the local logs in C:\Program Files\Microsoft Office\Office16\Logs if troubleshooting silent installations.

Step 5: Verify Activation Status

Once installation completes, verify that the licensing handshake succeeded.

  1. Open an elevated Command Prompt on the client workstation.
  2. Navigate to the Office directory:
    cd /d "%ProgramFiles%\Microsoft Office\Office16"
    
  3. Run the Office Software Protection Platform script to check status:
    cscript ospp.vbs /dstatus
    

Look for LICENSE STATUS: Licensed in the output text. If it shows an unlicensed state, you can manually apply a MAK key using:

cscript ospp.vbs /inpkey:YOUR-KEY-HERE
cscript ospp.vbs /act

Common Deployment Mistakes

Advisors often overlook minor configuration details that break enterprise rollouts. Avoid these frequent errors:

  • Mixing MSI and Click-to-Run: Leaving remnants of Office 2016 MSI builds on the machine will cause error codes during ODT installation. Always purge old office suites first.
  • Incorrect Architecture Matching: Trying to install 64-bit Office on legacy 32-bit Windows builds fails instantly. Match the OfficeClientEdition attribute to your OS architecture.
  • Firewall Blocks for KMS: If you use KMS activation, ensure TCP port 1688 is open on your firewall so clients can reach the internal activation host.

Frequently Asked Questions

Can I deploy Office 2019 volume licenses over Wi-Fi?

While possible, wireless drops during large source downloads can corrupt cab files. Always run initial source downloads and bulk deployments over a wired Ethernet connection.

✨ Don't miss: this story

How do I update Office 2019 if it's a one-time purchase?

Office 2019 doesn't receive feature updates like subscription models do, but it receives critical monthly security patches automatically through the Click-to-Run update channel defined in your XML.

What is the difference between MAK and KMS activation?

Multiple Activation Keys (MAK) connect directly to Microsoft's hosted servers each time a machine activates up to a set limit. Key Management Service (KMS) sets up a local activation server inside your corporate network, handling offline activations for internal clients.

Does Office 2019 volume licensing include Access and Publisher?

Yes, Office Professional Plus 2019 includes Word, Excel, PowerPoint, Outlook, OneNote, Publisher, and Access. Office Standard 2019 includes the core suite and Publisher, but excludes Access.

CR

Written by

Chloe Ramirez

Chloe Ramirez excels at making complicated information accessible, turning dense research into clear narratives that engage diverse audiences.

More from it