Office LTSC Volume Activation with OSPP.VBS: Admin Guide

Organizations that need a fixed, non-subscription version of Office use Office LTSC editions licensed through volume agreements. These editions activate through KMS, Active Directory-Based Activation or a Multiple Activation Key. Administrators manage activation with a built-in script called OSPP.VBS. This guide covers the essential commands and deployment tips.

Where to Find OSPP.VBS

The script lives in the Office installation folder:

• 64-bit Office: C:\Program Files\Microsoft Office\Office16\
• 32-bit Office on 64-bit Windows: C:\Program Files (x86)\Microsoft Office\Office16\

Recent Office LTSC versions still use the Office16 folder. Open an elevated Command Prompt, change to that folder and run commands with cscript ospp.vbs.

Office LTSC vs Microsoft 365 Apps

Office LTSC is a perpetual, volume-licensed version that receives security updates but no new features during its support lifecycle. It suits regulated environments, specialized devices and systems that must stay unchanged for years. Microsoft 365 Apps, by contrast, is licensed per user through a subscription and receives new features continuously. Choosing the right model affects how you activate: LTSC relies on KMS, ADBA or MAK, while Microsoft 365 Apps activates when users sign in.

Essential Commands

Activating with KMS or ADBA

Volume editions of Office LTSC include a GVLK by default. If your organization has a KMS host or an Office activation object in Active Directory, Office activates automatically. To force activation, run /act. Remember that KMS requires at least five Office clients before it starts activating them.

Activating with a MAK

1. Install the MAK: cscript ospp.vbs /inpkey:<MAK key>
2. Activate: cscript ospp.vbs /act
3. Confirm: cscript ospp.vbs /dstatus should show LICENSE STATUS: —LICENSED—.

Deploying with the Office Deployment Tool

The Office Deployment Tool (ODT) installs Office LTSC using an XML configuration file. A simple example:

<Configuration>
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024">
    <Product ID="ProPlus2024Volume">
      <Language ID="en-us" />
    </Product>
  </Add>
  <Display Level="None" AcceptEULA="TRUE" />
</Configuration>

Run setup.exe /configure config.xml. You can add a PIDKEY attribute to the Product element to install a MAK during setup. Use the Office Customization Tool on Microsoft’s website to generate configuration files with the correct product IDs and channels.

Checking Activation Across Many PCs

For a quick audit, run /dstatus remotely against another computer by adding its name, for example cscript ospp.vbs /dstatus pc-042, when you have administrator rights and remote management is enabled. For larger estates, collect the results through your endpoint management tool or use VAMT, which can display Office activation status for every discovered device in one console. Regular audits help you catch devices that have drifted out of activation before users see warnings.

Troubleshooting Tips

• 0xC004F074: the KMS host is unreachable. Check DNS records and port 1688, or set the host with /sethst.
• 0xC004F038: the KMS host hasn’t reached the Office threshold yet.
• Retail and volume conflicts: remove retail Office versions before deploying LTSC.
• Old keys left behind: list keys with /dstatus and remove unwanted ones with /unpkey.

Frequently Asked Questions

Does OSPP.VBS work with Microsoft 365 Apps?

Microsoft 365 Apps use subscription licensing tied to user sign-in. OSPP.VBS is mainly for volume-licensed editions.

How long does Office KMS activation last?

180 days, renewed automatically while the client can reach the KMS host or Active Directory.

Can I script activation across many PCs?

Yes. Run OSPP.VBS through your deployment tool, Group Policy startup scripts or VAMT for MAK proxy activation.

Conclusion

OSPP.VBS gives administrators full control over Office LTSC activation. Combine it with the Office Deployment Tool to install, license and verify Office consistently across your organization.