Office LTSC 2024: Setup, Policies, and Admin Configuration Guide 2026
Why Office LTSC 2024 Setup Goes Wrong
I've seen this exact situation on dozens of enterprise deployments: an IT admin downloads Office LTSC 2024, kicks off the install, and then hits a wall. Maybe activation fails silently. Maybe the Office Deployment Tool throws a cryptic exit code. Maybe Group Policy settings that worked perfectly on Office LTSC 2021 seem to do absolutely nothing. I know this is frustrating , especially when your users are waiting and your manager is asking for a status update every 30 minutes.
Here's the core thing you need to understand about Office LTSC 2024 before you touch a single configuration file: this is not a traditional MSI install. If you're coming from Office 2016 or even Office 2019 MSI builds, the shift to Click-to-Run changes almost everything about how deployment, patching, and activation work. The technology under the hood is fundamentally different, even though the major version number, 16.0, is exactly the same as every Office release going back to 2016.
That shared major version (16.0) is actually intentional and helpful once you know it's there. Your existing Group Policy objects still write to the same registry hives they always have. Your Configuration Manager task sequences largely carry over. But the installer is Click-to-Run, which means you must use the Office Deployment Tool (ODT) and a proper configuration XML. Running a direct setup.exe the old way will either fail outright or produce a broken install that activates but behaves strangely.
The second big source of confusion is product scope. Office LTSC 2024 covers six distinct volume-licensed products for Windows: Office LTSC Professional Plus 2024, Office LTSC Standard 2024, Project Professional 2024, Project Standard 2024, Visio LTSC Professional 2024, and Visio LTSC Standard 2024. Each has its own product ID in your configuration XML. Mix them up and your activation will fail even if your KMS keys are perfectly valid.
Then there's the question of what's missing. Microsoft Publisher is gone entirely, not just delisted, it's not included at all due to the planned retirement coming in October 2026. Microsoft Teams is no longer bundled either; it's a separate download. ActiveX controls are disabled by default. If your organization has line-of-business applications or Excel workbooks that depend on any of these, those dependencies will break on day one unless you plan for them in advance.
Finally, Office LTSC 2024 is targeted squarely at organizations in highly regulated or restricted environments that cannot take ongoing feature updates. If your environment doesn't actually have those constraints, you may be deploying the wrong product entirely, Microsoft 365 Apps for Enterprise includes every feature in Office LTSC 2024 plus a continuous stream of new capabilities. That distinction matters and we'll address it in the FAQ below.
The Quick Fix, Try This First
If activation is broken and nothing else has changed recently, start here before touching anything else. The single most common activation failure I see is a KMS client that can't reach the KMS host, either because the host's DNS SRV record is missing or because a firewall rule was updated. This one check clears about 60% of the tickets I see on fresh Office LTSC 2024 deployments.
Open an elevated Command Prompt on the affected machine and run the Office Software Protection Platform script:
cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /dstatusLook at the output carefully. You want to see LICENSE STATUS: ---LICENSED--- next to the correct product key. If you see OOB_GRACE, the machine activated once but hasn't been able to renew, your KMS host is likely unreachable. If you see NON_GENUINE or UNLICENSED, the product ID in your configuration XML may not match the license key you're trying to activate against.
To manually point the client at your KMS host and force an activation attempt:
cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /sethst:your-kms-server.domain.local
cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /setprt:1688
cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /actReplace your-kms-server.domain.local with your actual KMS host FQDN. If that command succeeds, your KMS host is reachable but auto-discovery via DNS is broken. You'll need to either add the _vlmcs._tcp SRV record back to DNS or push the /sethst setting via Group Policy so every machine knows where to look.
If you're using MAK activation instead of KMS, the quick check is simpler. Run ospp.vbs /dstatus and confirm your MAK key ends in the correct last five characters. If the machine was imaged from a template that had a KMS key baked in, MAK activation will fail until you explicitly remove the KMS key with /unpkey and install the MAK key with /inpkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX.
ospp.vbs /dstatus output shows the last five characters of every installed product key. Cross-reference these against your volume licensing portal before calling Microsoft Support, nine times out of ten the wrong key SKU was deployed and you can fix it in under five minutes without opening a ticket.
The Office Deployment Tool (ODT) is the only supported method for deploying Office LTSC 2024 in a volume-licensed environment. You download it from the Microsoft Download Center, search for "Office Deployment Tool" and grab the current release. It's a self-extracting executable that drops setup.exe and a sample configuration.xml into whatever folder you specify.
Before you write a single line of XML, decide on your source: are you deploying directly from the Content Delivery Network (CDN) or from a local network share? For air-gapped or bandwidth-constrained environments, you'll want to run a download pass first using a SourcePath-less configuration to pull the installation files to a UNC path, then reference that path in your deployment configuration.
A minimal but correct configuration XML for Office LTSC Professional Plus 2024 looks like this:
<Configuration>
<Add OfficeClientEdition="64" Channel="PerpetualVL2024">
<Product ID="ProPlus2024Volume"
PIDKEY="XXXX-XXXX-XXXX-XXXX-XXXX">
<Language ID="en-us" />
<ExcludeApp ID="Teams" />
<ExcludeApp ID="Publisher" />
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>A few things to call out here. Channel="PerpetualVL2024" is mandatory, using any other channel value (like Current or MonthlyEnterprise) will deploy Microsoft 365 Apps, not Office LTSC 2024. The ExcludeApp lines for Teams and Publisher are recommended since neither is included with the product anyway; leaving them out doesn't break anything, but it's cleaner. Once your XML is saved, run the deployment with:
setup.exe /configure configuration.xmlIf it works, you'll see Office apps appear in the Start menu within 10–20 minutes depending on your network speed. If setup exits immediately with no visible feedback, check %temp%\ODT*.log, the ODT writes detailed logs there.
The activation model for Office LTSC 2024 hasn't changed from prior volume-licensed versions, you still choose between Key Management Service (KMS), Multiple Activation Key (MAK), or Active Directory-based activation. The process is the same as Office LTSC 2021. If you already have a working activation infrastructure, Office LTSC 2024 slots right in.
For KMS activation, your KMS host needs to be running a version that supports Office LTSC 2024. If your KMS host is on an older OS, you may need to install an updated KMS host key. Once the host is ready, configure the host key:
slmgr.vbs /ipk <KMSHostKey>
slmgr.vbs /atoThen verify the host is listening on port 1688 and that your DNS zone has a valid _vlmcs._tcp SRV record pointing to it. KMS requires at least 5 Office clients to activate (the activation threshold). Until that threshold is met, clients will sit in grace mode for 30 days before going unlicensed.
For MAK activation in an internet-connected environment, Office LTSC 2024 can self-activate after you embed the MAK key in your configuration XML via the PIDKEY attribute and set AUTOACTIVATE=1. For offline MAK activation, use Phone Activation through the Microsoft licensing portal.
Active Directory-based activation (ADBA) is the third option and often the smoothest for domain-joined environments. It requires your Active Directory forest to be at Windows Server 2012 functional level or higher, and you install an activation object using the Volume Activation Management Tool (VAMT). Once the activation object is in AD, any domain-joined machine with Office LTSC 2024 installed will activate automatically without touching KMS or MAK directly.
After activation completes, verify the status again with ospp.vbs /dstatus. You should see a clean LICENSED status with a remaining license time of roughly 180 days (KMS) or permanent (MAK/ADBA). Write that date down, KMS clients renew every 7 days by default, but if something blocks renewal for 180 days straight, they go unlicensed.
This is where IT admins who are upgrading from Office 2016 often get a pleasant surprise: your existing Office GPO settings almost certainly still work. Because Office LTSC 2024 shares the same major version (16.0) as every Office release since 2016, Group Policy writes to the same registry locations it always has:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Office\16.0
HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0To manage Office LTSC 2024 through Group Policy, download the latest Office ADMX templates from the Microsoft Download Center (search "Office 2024 Administrative Template files"). Copy the .admx files to your Group Policy Central Store at \\domain\SYSVOL\domain\Policies\PolicyDefinitions\ and the corresponding .adml language files to the appropriate language subfolder (e.g., en-US).
Once loaded, you'll find Office LTSC 2024 settings under User Configuration > Administrative Templates > Microsoft Office 2024 and Computer Configuration > Administrative Templates > Microsoft Office 2024 in the Group Policy Management Editor.
Three GPO settings you'll almost certainly want to configure immediately:
# Block users from changing update source
Computer Config > Office 2024 > Updates > Update path
# Disable ActiveX controls globally (already off by default,
# but lock it via GPO to prevent user override)
User Config > Office 2024 > Security Settings > ActiveX
# Set ODF 1.4 as default save format (new in Office LTSC 2024)
User Config > Office 2024 > Word/Excel/PowerPoint > SaveAfter applying a new GPO, always run gpupdate /force on a test machine and confirm with gpresult /h gpresult.html that your Office policies appear in the Applied section. If they show as filtered or not applied, check WMI filtering and security group membership first.
How updates work in Office LTSC 2024 is one of the areas where admins trip up most often, especially if they're coming from Microsoft 365 Apps, where updates flow continuously. Office LTSC 2024 does receive security updates and bug fixes, but it will never receive new features after launch. That's the whole deal with LTSC.
By default, Office LTSC 2024 checks Microsoft's CDN for updates. In most enterprise environments, you'll want to redirect this to an internal share or Configuration Manager/WSUS. You do this either in your ODT configuration XML at deploy time or via Group Policy after deployment.
In the ODT XML, the update source looks like:
<Updates Enabled="TRUE"
UpdatePath="\\fileserver\OfficeUpdates\LTSC2024"
TargetVersion="16.0.18027.20116" />Leave out TargetVersion unless you're pinning to a specific build, which you generally should do in regulated environments where change management requires testing before any patch goes to production.
Via Group Policy, navigate to Computer Configuration > Administrative Templates > Microsoft Office 2024 > Updates and set the Update path policy to your UNC path. You can also set Enable Automatic Updates to Disabled if you want full manual control and push updates through Configuration Manager instead.
To check what build is currently installed on a machine, open any Office app, go to File > Office Account > About [App Name]. The version string shows as something like Version 2408 (Build 16.0.17928.20114). You can also query this from the registry:
Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration" |
Select-Object VersionToReportIf the value doesn't appear or reads as empty, the Click-to-Run service may be stopped. Run Get-Service -Name ClickToRunSvc and start it if it shows as stopped.
Three things will catch your users off guard on the first day if you don't address them proactively. I always walk through each of these with clients before the deployment goes to production, because the support tickets that come from ignored warnings here are 100% predictable.
ActiveX controls disabled by default. In Office LTSC 2024, ActiveX controls are turned off out of the box. This is a security improvement, but it will break any Excel workbook or Word document that embeds ActiveX forms or controls, think legacy data entry tools, dated financial models with spinner buttons, or old HR forms. If you have business-critical workbooks that use ActiveX, you can re-enable ActiveX via Group Policy. Go to User Configuration > Administrative Templates > Microsoft Office 2024 > Security Settings > Trust Center and configure the ActiveX control initialization policy. Alternatively, you can re-enable it per-document by adding the file location to the Trusted Locations list. If only specific users need it, scoping the GPO by security group is cleaner than re-enabling it fleet-wide.
Microsoft Publisher is not included. Publisher was removed entirely from Office LTSC 2024 as part of its planned retirement (official end of support: October 2026). If anyone in your organization uses Publisher for newsletters, flyers, or print layouts, you need to identify those users before cutover. Options: keep them on Office LTSC 2021 until October 2026 hits, migrate their files to Word (which handles many Publisher layouts), or move them to a Microsoft 365 plan where Publisher still exists for now.
Microsoft Teams is a separate download. Teams doesn't ship in the Office LTSC 2024 package at all. You deploy it independently. Use the Teams MSI installer for machine-wide installation in enterprise environments:
msiexec /i Teams_windows_x64.msi ALLUSERS=1 ALLUSER=1The ALLUSER=1 flag (note: single R) is what triggers machine-wide install mode. Without it, Teams installs per-user and shows up in %LOCALAPPDATA%, which creates a mess with roaming profiles and VDI environments. Once Teams is installed machine-wide, it shows up for all users on that device and receives updates through its own update channel independently of Office.
Advanced Troubleshooting for Office LTSC 2024
When the standard steps don't solve it, here's where I go next. These techniques apply to domain-joined enterprise environments where simple reinstalls aren't practical.
Event Viewer analysis. Office LTSC 2024 logs activation events to the Application log under source Microsoft Office 16. Open Event Viewer, navigate to Windows Logs > Application, and filter by Source. Error event IDs in the 1000–1015 range typically indicate Click-to-Run service failures. Event ID 1001 with an application crash report for OfficeC2RClient.exe almost always points to a corrupted installation that needs a repair or reinstall via ODT.
For activation-specific logging, the Software Protection Platform logs under Applications and Services Logs > Microsoft > Windows > Security-SPP > Operational. Filter for Warning and Error level events. Event ID 12288 means activation started; 12289 means it failed. The failure code in the event data maps to specific errors, 0xC004F074 means no KMS host could be reached; 0xC004F038 means the KMS count threshold hasn't been met yet.
Registry verification for Group Policy. If you suspect a GPO isn't applying, confirm directly in the registry. For a computer-scoped Office policy, check:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Office\16.0\Common\GeneralFor a user-scoped policy, check:
HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0\Common\GeneralValues written here by Group Policy appear as standard REG_DWORD or REG_SZ entries. If the values are missing after a gpupdate /force, the GPO is either not targeting that machine/user or the ADMX templates aren't loaded in the Central Store correctly.
Repairing a broken Click-to-Run installation. If Office apps crash on launch or show activation errors even though ospp.vbs /dstatus reports LICENSED, the installation itself may be corrupt. Run an online repair through the ODT:
setup.exe /repair ProPlus2024VolumeThis re-downloads and replaces any corrupt files without removing user data or settings. It's much safer than a full uninstall/reinstall on a production machine. The repair typically takes 10–20 minutes and Office apps will be unavailable while it runs.
Conflict with existing Office installations. Running Office LTSC 2024 alongside an older Office MSI installation (Office 2016 MSI, for example) is not supported. The ODT will attempt to remove conflicting versions if you set RemoveMSI in your configuration XML:
<RemoveMSI />Add this element inside your <Configuration> block to automatically uninstall detected MSI Office products during deployment. Without it, you may end up in a broken state where both installs exist but neither works properly.
%temp%, the output of ospp.vbs /dstatus, your Event Viewer exports from the SPP Operational log, and the output of gpresult /h. Having all of this ready before you call cuts your support call time in half. Reach Microsoft Support through the admin center if you have a volume licensing agreement, those cases get routed to engineers who actually know Click-to-Run internals.
Prevention & Best Practices
Most Office LTSC 2024 deployment headaches are preventable. After working through enough of these rollouts, I've built up a short list of things that separate smooth deployments from week-long firefights.
First: test your configuration XML in a lab before touching production. The ODT is unforgiving about typos in product IDs and channel names. A test deployment to two or three VMs takes maybe an hour and will surface 90% of configuration problems before anyone's workday is disrupted. Make sure your lab machines match your production OS versions, Office LTSC 2024 supports Windows 11, Windows 11 LTSC 2024, Windows 10 LTSC 2021, Windows 10 LTSC 2019, Windows Server 2025, and Windows Server 2022. If you're deploying to Arm-based devices, Windows 11 is the minimum, Windows 10 Arm is not supported.
Second: audit your existing add-ins and integrations before cutover. Because Office LTSC 2024 shares the 16.0 major version with Office LTSC 2021 and Office 2019, most COM add-ins and VSTO solutions that work on those versions will work on 2024 with minimal or no changes. But "most" isn't "all." Run your add-in inventory through the Office Compatibility Toolkit or test each one manually in your lab environment. Pay particular attention to anything that relies on ActiveX (now disabled by default) or that connects to Publisher (now gone).
Third: establish a clear update cadence before deployment. Office LTSC 2024 receives security updates monthly. In regulated environments, those updates need to go through a change management process before being pushed to end-user machines. Build that process now, configure the UpdatePath to point at a staging share, test monthly patches in your lab, and promote them to production on a defined schedule. Scrambling to build this process after a zero-day patch lands is not a good time.
Fourth: document your activation method and keep your keys accessible. Whether you're on KMS, MAK, or Active Directory-based activation, write down exactly how you activated, where the keys are stored, and what the renewal schedule looks like. Three years from now when someone has to rebuild a KMS host, that documentation is worth its weight in gold.
- Add
RemoveMSIto your ODT config XML to automatically clear old Office MSI installs during deployment, prevents silent conflicts - Pin a specific Office build in your
UpdatePathduring initial rollout so you're not deploying a moving target - Load the Office 2024 ADMX templates into your Group Policy Central Store on Day 1, even if you don't need new policies yet, it avoids scrambling later
- Set a calendar reminder 4 years and 9 months from your deployment date, that's your Office LTSC 2024 Mainstream Support warning window, since there is no Extended Support period after the 5-year term ends
Frequently Asked Questions
What actually changed in Office LTSC 2024 compared to Office LTSC 2021?
The most significant change is support for OpenDocument Format 1.4, Word, Excel, and PowerPoint now save ODF files in ODF 1.4 by default, which brings new capabilities like tables within shapes and improved accessibility attributes. The Office Add-ins JavaScript API surface expanded substantially: Excel now supports requirement sets up to 1.17, Outlook up to 1.14, and PowerPoint up to 1.5. On the removal side, Microsoft Publisher is gone (retiring October 2026), the Publish to Power BI feature was removed from Excel, Teams is no longer bundled, and ActiveX controls are disabled by default. The installation technology also shifted from Windows Installer (MSI) to Click-to-Run if you were coming from Office 2016 MSI builds, that's the biggest operational change for IT admins.
What stayed the same in Office LTSC 2024, will my existing Group Policy settings still work?
Yes, your existing Group Policy settings will almost certainly carry over without modification. Office LTSC 2024 keeps the same major version number (16.0) as Office LTSC 2021, Office 2019, and Office 2016, so GPOs continue writing to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Office\16.0 and HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0 exactly as before. The activation process is also unchanged, KMS, MAK, and Active Directory-based activation all work the same way they did for prior versions. You can continue using the same software distribution tools (like Microsoft Configuration Manager) that you used for Office LTSC 2021.
What are the new features in Office LTSC 2024 for end users?
Office LTSC 2024 brings feature updates relative to Office LTSC 2021 across all core apps, Word, Excel, PowerPoint, Outlook, Access, and OneNote all have dedicated "What's New" pages in Microsoft's documentation. The headline additions include ODF 1.4 file format support, expanded JavaScript API sets for Office Add-ins, and various app-specific improvements documented per product. That said, it's important to set expectations correctly: these are the features available at launch, and Office LTSC 2024 will not receive any new features after that. It never will, that's the nature of the LTSC channel. If your users need continuous new features like AI-driven tools or real-time collaboration, you're looking at the wrong product and should evaluate Microsoft 365 Apps instead.
My KMS activation is failing with error 0xC004F074, how do I fix it?
Error 0xC004F074 means the Software Licensing Service reported that the computer could not be activated because no Key Management Service host could be contacted. Start by confirming your KMS host is reachable from the affected machine: run nslookup -type=SRV _vlmcs._tcp.yourdomain.local and check that it returns a valid SRV record pointing to your KMS host. If DNS resolution fails, manually set the KMS host using cscript ospp.vbs /sethst:kmshost.domain.local and retry activation with cscript ospp.vbs /act. If that works, the fix is to restore the _vlmcs._tcp DNS SRV record. If it still fails after manual configuration, check that port 1688 is open between the client and KMS host, a firewall rule change is a common culprit after network reconfigurations.
Should I deploy Office LTSC 2024 or Microsoft 365 Apps for my organization?
If your organization doesn't have a specific regulatory or compliance requirement that mandates a fixed, non-updating Office installation, you almost certainly want Microsoft 365 Apps instead. Microsoft 365 Apps includes every feature in Office LTSC 2024, plus real-time collaboration, AI-driven tools, advanced security and compliance capabilities, and a continuous stream of new features. Office LTSC 2024 is designed for environments where systems must be locked down and feature changes require formal validation cycles, think defense contractors, healthcare systems with validated software requirements, or heavily air-gapped networks. It also only receives five years of Mainstream Support with no Extended Support period afterward, which is a shorter overall lifecycle than many organizations expect.
How do I re-enable ActiveX controls in Office LTSC 2024 for specific users?
ActiveX controls are disabled by default in Office LTSC 2024, but IT administrators can turn them back on. The most targeted approach is to add specific file locations to the Trusted Locations list in the Office Trust Center, ActiveX will run in documents opened from those locations. For a broader re-enablement, configure the ActiveX initialization policy through Group Policy under User Configuration > Administrative Templates > Microsoft Office 2024 > Security Settings > Trust Center, or push the setting through the registry at HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0\Common\Security. Scope the GPO to a security group containing only the users who genuinely need ActiveX, re-enabling it universally increases your attack surface unnecessarily, and it was disabled by default for good reason.