11-07-2025 09:15 AM
We've recently attempted enrolling a few Windows devices into Meraki, where the endpoint has cellular connectivity. Some items I have noticed, is IMEI, Phone Number, and Location are all missing or inaccurate.
Does anyone know if there is a feature matrix that shows what limitations may exist for Windows devices and/or a roadmap for future enhancements? Anyone else seeing similar or different behavior?
Also, it was uncovered there is an undocumented issue where Windows devices need at LEAST two spare SM licenses to fully enroll, but will merge to consume only one post-enrollment.
EDIT: Windows 11 25H2, SM Agent 4.2.2
11-09-2025 11:13 AM
@ktfoster I am not aware of any documentation that lists supported MDM features for the different operating systems.
Also if you have found a bug please report it via support so that it can get reviewed.
11-10-2025 05:04 AM
Hi Blake!
It was mentioned to the assigned engineer. It appears to be an "unpublished" bug/issue.
11-09-2025 03:28 PM
On the whole, Meraki Systems Manager support for Windows is poor.
12-09-2025 09:40 AM
...and now we know why.
11-10-2025 09:32 AM
@Philip D'Ath is correct about windows support. An anecdotal experience we are having that seems potentially related to your issue:
We discovered an issue when adding a new device to SM using the same NIC. SM will often overwrite most data from the first enrolled device rather than generating a new record for the second one. That causes a whole other set of problems with devices not checking in and such. Got a ticket in on that one and a Dev is looking at it, just wanted to throw that in here in case you might notice that's related.
11-10-2025 09:38 AM
Indeed. That was the identical problem we faced when I created the ticket. We hit it because our helpdesk was using a single docking station to build each Surface tablet we were deploying.
03-16-2026 11:17 PM
Interesting topic! From what I understand, the Windows SM Agent (System Management Agent) plays a key role in enabling certain hardware and system-level features, especially on enterprise or OEM devices. Its feature support can vary depending on the manufacturer and installed drivers, so keeping everything updated is important. Sometimes, when testing different system functions like color printer test pages, small compatibility issues can also show up. If something isn’t working as expected, checking BIOS settings and driver versions can often help resolve compatibility issues.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide