What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Office 365 ProPlus is serviced on a recurring cadence, and Microsoft ends support for older client builds. SCCM admins can’t rely on “installed/not installed” alone—you need a repeatable way to identify which devices are still running builds that are past your support window.
CMPivot is a fast way to pull Office build and Click-to-Run configuration details directly from managed clients. This guide gives you production-ready CMPivot queries and a support-cutoff approach you can operationalize into a collection and remediation workflow.
As an Amazon Associate I earn from qualifying purchases.
Target outcome: a CMPivot-driven method to produce an “out-of-support Office 365 ProPlus / Microsoft 365 Apps” list you can act on.
Why this matters: Office build support windows and what you can measure in SCCM
Office for enterprise (Microsoft 365 Apps / formerly Office 365 ProPlus) is updated on channels (Current Channel, Monthly Enterprise Channel, Semi-Annual Enterprise Channel, etc.). Older builds can become unsupported while the product remains installed, so devices need build-level verification.
#1 Best Overall
In SCCM, the actionable signal you can collect quickly is the Click-to-Run “reported version” (commonly VersionToReport) and channel/branch configuration from the client. Those values let you compare a device’s current Office build to a cutoff you define based on Microsoft’s support guidance.
Prerequisites and prerequisites checks (CMPivot + Office detection)
Minimum SCCM requirements
- SCCM (Current Branch) with CMPivot enabled and working on your target collection.
- Permissions to run CMPivot queries against devices (role-based access in SCCM).
- Endpoints must be online and healthy so CMPivot can query the local registry and installed software inventory.
Operational readiness checks
- Confirm you can run a simple CMPivot query like
select * from SMS_G_System_INSTALLED_SOFTWAREon one known-good device with Office installed. - Verify your clients support inventory of software/registry access paths. If a device is heavily locked down, registry-based queries may fail.
- Decide up front whether you’re targeting Microsoft 365 Apps, Office 365 ProPlus, or both (the product naming varies in the field).
What CMPivot can and can’t detect
- Can: pull installed application entries from
SMS_G_System_INSTALLED_SOFTWAREand read Click-to-Run configuration values from the registry via CMPivot’s registry provider. - Can: filter and sort results by name/version and capture the build identifier for each endpoint.
- Can’t (directly): magically convert build numbers to support status without you applying a cutoff rule (cutoff comes from Microsoft guidance and your servicing policy).
Strategy overview: detect Office 365 ProPlus and compare the build to your support threshold
Use CMPivot in two phases:
- Inventory: identify that the device has Microsoft 365 Apps / Office 365 ProPlus and collect reported version plus update channel/branch from Click-to-Run registry values.
- Evaluate: compare the retrieved version/build against a cutoff build you maintain (per channel or per environment). Devices below the cutoff are “out-of-support.”
This avoids brittle name-matching only, and it gives you stable, build-level evidence.
CMPivot queries to inventory Office 365 ProPlus/Microsoft 365 Apps
Run these queries against a pilot collection containing a handful of devices you know are on different Office channels/builds. Once results look right, widen the collection.
Free tools Windows power users keep installed
One-click scans. No signup required.
Query 1: Find Office ProPlus / Microsoft 365 Apps installed software
This query finds Office product entries that commonly appear across tenants and languages. It’s the quickest “sanity check” that CMPivot can see Office in installed software inventory.
select Name, Version from SMS_G_System_INSTALLED_SOFTWARE
where Name like '%Office 365 ProPlus%' or Name like '%Microsoft 365 Apps%' or Name like '%ProPlus%' or Name like '%Microsoft Office Professional Plus%'
Interpretation: If you see multiple Office entries, you may have language packs or older remnants. Treat this as a detection aid; use Click-to-Run registry for the build truth.
Query 2: Get Click-to-Run reported version and channel/branch
Click-to-Run configuration is one of the most consistent places to retrieve the build value you can compare to a cutoff. On many clients, VersionToReport looks like 16.0.xxxxx.xxxxx.
Recommended Free Tools
Rank #2
select ValueName, Value from RegistryValue
where KeyName = 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' and (ValueName like '%VersionToReport%' or ValueName like '%UpdateChannel%' or ValueName like '%UpdateBranch%' or ValueName like '%CDNBaseUrl%' or ValueName like '%Platform%')
If registry querying works, you should see at least VersionToReport and one of the channel/branch fields. If you don’t, check the troubleshooting section.
Query 3: Pull the Office update branch and platform signals
Sometimes the first registry query returns many values; this one intentionally narrows down to the fields that usually matter for support planning.
select ValueName, Value from RegistryValue
where KeyName = 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' and (ValueName = 'UpdateChannel' or ValueName = 'UpdateBranch' or ValueName = 'Platform' or ValueName = 'PlatformTarget')
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteSpecial offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
order by ValueName
Interpretation: The combination of channel/branch and the version/build is what you map to your “supported vs. out-of-support” cutoff rule.
Query 4: Normalize and filter only Microsoft 365 Apps family
To reduce noise, filter installed software entries to the Office 365 ProPlus / Microsoft 365 Apps family. You still won’t get the Click-to-Run build from this query, but it helps you confirm product family and scope.
select Name, Version from SMS_G_System_INSTALLED_SOFTWARE
where (Name like '%Microsoft 365 Apps%' or Name like '%Office 365 ProPlus%' or Name like '%ProPlus%')
order by Name
Gotcha: Product names vary by OS language and tenant rollout. Always treat the registry query as the primary evidence for build/version.
Turn build numbers into an out-of-support list
CMPivot can’t automatically know which Office builds are unsupported in your environment. The practical approach is to maintain a cutoff build (or cutoff release date/build) per update channel, then compare devices to that cutoff.
Option A (recommended): Maintain a small “supported build cutoff” mapping
Create a simple internal mapping table (in a spreadsheet, wiki, or CMDB) keyed by your channel/branch. Example schema:
| Channel/Branch (registry) | Supported cutoff | Decision rule |
|---|---|---|
| Current Channel | Min supported VersionToReport = 16.0.17628.20128 | If device VersionToReport < cutoff => out-of-support |
| Monthly Enterprise Channel | Min supported VersionToReport = 16.0.17425.20190 | If device VersionToReport < cutoff => out-of-support |
| Semi-Annual Enterprise Channel | Min supported VersionToReport = 16.0.16327.20480 | If device VersionToReport < cutoff => out-of-support |
How to apply: export CMPivot results (CSV) for the pilot, then evaluate the comparison with your cutoff. If you want a fully automated SCCM compliance rule, you’ll typically move this logic into a script (PowerShell) or a detection rule that you can run as a client script/CI. CMPivot remains your fast discovery tool.
Option B: Use a single global cutoff (faster, less accurate)
If you can’t manage per-channel cutoffs, you can define one global minimum supported VersionToReport and flag anything below it. It’s simple, but it’s more likely to misclassify devices that are on a slower channel cadence.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Example decision rule:
- If
VersionToReportis less than your chosen minimum, mark as out-of-support. - Document the tradeoff and confirm with a small sample across channels.
How to pick the cutoff date/build from Microsoft guidance
Microsoft publishes support lifecycle guidance for Office update channels (and how long builds remain supported). Your cutoff should reflect your channel’s supported window according to that guidance, plus your own change-management window.
Practical workflow that works: pick the minimum supported build for each channel from Microsoft’s current documentation, then update your cutoff mapping on a predictable cadence (for example, monthly when you check for new servicing guidance or quarterly if your environment is stable).
Because exact cutoff build numbers change over time, treat your cutoff as configuration, not as a hardcoded constant in CMPivot.
Collections and actions: what to do after you detect out-of-support clients
CMPivot gives you evidence; SCCM collections and remediation give you outcomes. A solid workflow keeps the number of “unknowns” low and the number of “unintended updates” even lower.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Build a “Needs Office update” collection
Common pattern:
- Run CMPivot queries on a broad collection (or a pilot ring) and export results.
- Evaluate devices against your cutoff mapping.
- Create an SCCM collection for devices that fail the cutoff rule.
- Target servicing actions only at that collection.
If you already have a software update/servicing mechanism, use the collection as the target audience.
Remediate with a targeted update / servicing plan
Typical remediation options include:
- Use your established Microsoft 365 Apps deployment mechanism (for example, your existing servicing scripts or update schedules).
- Trigger a client-side update cycle through the supported enterprise method for your environment.
- For devices that can’t update normally (policy issues), assign them to a separate remediation queue and investigate.
Keep channel policies consistent: mixing channels or CDN sources can delay the build you expect to arrive.
Validate before/after using CMPivot
After remediation, rerun Query 2 on the same “needs update” collection. You’re looking for:
VersionToReportmoving above your cutoff.- Channel/branch fields matching the expected configuration.
- Absence of stale registry values (see troubleshooting).
Troubleshooting and edge cases
Office installed but CMPivot shows nothing
- Try the pilot scope: run the queries against a single known device first.
- Switch your installed-software filter: product naming varies. Use broader patterns like
%Microsoft Office%and then refine. - Check CMPivot permissions/network: if registry access is restricted, registry queries may return no values even if installed software is present.
Click-to-Run registry values are missing or stale
- Some endpoints may have damaged Click-to-Run configuration. Reinstalling/repairing Click-to-Run can restore the registry state.
- Stale values can persist if the app can’t reach the configured CDN. Confirm CDN base URL and update channel/branch values.
- If you see
VersionToReportbut it doesn’t match expected app UI, compare against actual app build on a sample device to calibrate.
Different product names by language
Installed software entries depend on the Office language pack and sometimes on how you originally deployed. That’s why the registry-based VersionToReport approach is usually more reliable than the installed software name string.
Devices on shared computers or with multiple Office installs
You may see multiple Office-related entries. Treat VersionToReport from the Click-to-Run configuration as the source of truth for the Click-to-Run-serviced installation. If multiple installations exist, you’ll need a deeper inventory approach outside CMPivot (for example, file-based or licensing-based validation).
Best Value
VersionToReport doesn’t match the product you expected
- Verify channel/branch fields from the same registry location. If those don’t match your intended servicing channel, you may be evaluating against the wrong cutoff.
- Confirm whether the device has “Microsoft 365 Apps for enterprise” vs older “ProPlus” naming in installed software inventory. Again: trust the Click-to-Run values for build.
Common mistakes that produce false out-of-support results
- Using installed software version as the build truth. Those versions can lag, reflect remnants, or represent language packaging rather than the servicing build.
- Hardcoding cutoffs forever. Support windows change; your cutoff mapping should be maintained.
- Ignoring update channel. A single global cutoff can misclassify slower channels as out-of-support.
- Not validating with a pilot ring. Always sanity-check on at least 5–10 endpoints across channels.
FAQ
Can CMPivot directly label devices as out-of-support without my cutoff mapping?
No. CMPivot can retrieve the Office build/channels, but it can’t determine your support policy decision automatically. You provide the cutoff rule based on Microsoft’s support guidance.
Which registry value should I treat as the build number?
For Click-to-Run Microsoft 365 Apps, VersionToReport from HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration is the most common practical value to compare against a minimum supported build.
What if some devices return null for VersionToReport?
Use troubleshooting steps: confirm Click-to-Run configuration access, validate registry query permissions, and verify whether the device can reach the configured CDN for updates. In some cases, repair/reinstall of Click-to-Run is required.
Does this work for both 32-bit and 64-bit Office?
Yes, the Click-to-Run configuration is the same location to pull build information in most cases. You can also query Platform and PlatformTarget to confirm what’s installed.
Bottom Line
To find out-of-support Office 365 ProPlus devices with SCCM, use CMPivot to collect Click-to-Run VersionToReport and channel/branch values, then compare them to a cutoff mapping you maintain from Microsoft’s support guidance. This gives you build-level evidence instead of unreliable “installed software” name/version checks.
Run the queries on a pilot ring, validate the detection accuracy, then turn the results into a focused SCCM collection for remediation. Repeat the validation after servicing so your “out-of-support” list stays trustworthy.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
