Office LTSC Standard 2024 Review: The Cheaper Volume Licence, Tested

Fix it now

Office LTSC Standard 2024 is Word, Excel, PowerPoint, Outlook and OneNote, volume licensed, feature-frozen and installed on one PC. Microsoft’s own suite comparison shows the difference from Professional Plus 2024 as a single application: Access. For most locked-down desktops that makes Standard the correct buy and the Professional Plus premium avoidable.

1. Buy it for devices that need the everyday applications and nothing more specialised, in an estate that has to stay unchanged.
2. Buy it where the machines are offline or regulated, since activation is by KMS, Active Directory-based activation or MAK rather than by sign-in.
3. Buy it alongside Professional Plus rather than instead of it: mixing the two SKUs in one estate is normal and both deploy from the same source.
4. Skip it for any device whose user designs Access databases. That machine needs Professional Plus 2024, and probably only that machine.
5. Skip both LTSC suites for staff who need collaboration, cloud storage or Copilot, because neither has them by design.
6. Check who merely opens an Access database rather than designing one. Those people need the free Access Runtime, not a suite upgrade.

Publisher is not in this release. Teams is not preinstalled. Support ends on 9 October 2029 with no extended phase.

If that settles the SKU mix you can stop here. The rest covers how to prove which machines need Access, and the deployment and activation detail for a mixed rollout.

Why it happens

Standard is not a cut-down build of the applications people actually use. Microsoft’s volume licensing suite comparison lists Office LTSC Standard 2024 as Word, Excel, PowerPoint, Outlook and OneNote installed on one PC, and Office LTSC Professional Plus 2024 as the same suite plus Access on PC. Word in Standard is Word in Professional Plus: same features, same monthly security updates, same fixed feature set for the life of the release.

That makes the choice between the two suites an inventory question rather than a judgement call, and it is worth an hour of somebody’s time because the difference multiplied across an estate is real money. Search the file shares and user profiles for .accdb and .mdb files, find out who owns them, and ask the departments most likely to have built something quietly: finance, quality, laboratory teams, anyone who maintains a register or a log.

Then split that list in two. People who design and maintain a database need Professional Plus. People who only open somebody else’s Access application need the Access Runtime, which Microsoft publishes as a free download with all design interface removed or disabled, and which requires no Office licence of its own. That distinction routinely reduces a department’s Professional Plus count to one or two named machines.

Everything else about the suite is identical to its bigger sibling, and that is the point. The Office Deployment Tool installs it from a configuration XML on the PerpetualVL2024 channel with the product ID Standard2024Volume; one downloaded source and two configuration files run a mixed estate. Activation is volume activation: Active Directory-based activation for domain-joined machines, a KMS host once five Office clients have checked in, or MAK keys for isolated devices, with cscript ospp.vbs /dstatus on a client to prove which SKU actually landed.

The limits are the same too, and they are the reason to buy deliberately. Microsoft states that Office LTSC 2024 does not include the cloud-backed features of Microsoft 365 Apps, so there is no co-authoring, no Copilot and no AutoSave to OneDrive; Teams is a separate download; Publisher is gone before its October 2026 end of life; and support finishes on 9 October 2029, which is also the last date this generation is supported for connecting to Microsoft 365 services. A frozen feature set protects a validated workstation and gradually isolates a knowledge worker.

Full reference

What separates the two volume suites

Running a mixed estate from one source

1. Download the source once with the Office Deployment Tool in download mode, on the PerpetualVL2024 channel.
2. Keep two configuration files: one naming Standard2024Volume, one naming ProPlus2024Volume.
3. Deploy Standard everywhere by default, and Professional Plus to the named machines that came out of the Access inventory.
4. Install the free Access Runtime on machines that only run a database rather than design one.
5. Prove the result across the estate by scripting cscript ospp.vbs /dstatus and collecting the licence name each machine reports.

Where the device-based licence bites

These licences are assigned to devices rather than to people, which suits shared machines, kiosks and equipment nobody signs into personally. Two situations change the arithmetic. On a session host, the number that matters is how many devices reach the server, and the supported subscription route there is shared computer activation, which comes with any plan including Microsoft 365 Apps for enterprise, any plan including the desktop Visio or Project applications, and Microsoft 365 Business Premium – but not with Microsoft 365 Apps for business or Business Standard. And in a virtual desktop estate the same logic applies: perpetual licences and non-persistent desktops are an awkward pairing.

When Standard is the wrong answer entirely

• Staff who co-author documents with people outside the estate. LTSC has no co-authoring, and that shows up within days.
• Anyone who needs Copilot or the cloud-backed features, which no perpetual licence provides at any price.
• Machines that will be replaced within two or three years, where a five-year perpetual licence does not get its value out.
• Session hosts and non-persistent virtual desktops, where the subscription licensing model exists precisely for this.
• Users who need Access. That is Professional Plus, and buying Standard for them creates a support ticket rather than a saving.

Before the rollout

• Remove earlier Office installations in the deployment configuration rather than layering the new suite over them.
• Confirm no target machine is meant to keep Microsoft 365 Apps: the two cannot coexist, though Visio LTSC 2024 and Project 2024 can sit alongside Microsoft 365 Apps version 2408 or later.
• Decide the activation method before you build the image, because Active Directory-based activation needs nothing on the client while MAK needs a key on each one.
• Put 9 October 2029 in the asset register against every device you deploy to, and note that Office LTSC 2021 loses supported Microsoft 365 connectivity much sooner, on 13 October 2026.

Questions people ask about this