Windows SM Agent - Feature Support

KFoster
Getting noticed

Windows SM Agent - Feature Support

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

5 Replies 5
BlakeRichardson
Kind of a big deal
Kind of a big deal

@KFoster 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. 

If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.
KFoster
Getting noticed

Hi Blake!

 

It was mentioned to the assigned engineer. It appears to be an "unpublished" bug/issue.

 

KFoster_0-1762779850200.png

 

PhilipDAth
Kind of a big deal
Kind of a big deal

On the whole, Meraki Systems Manager support for Windows is poor.

nbv
Getting noticed

@PhilipDAth 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.

KFoster
Getting noticed

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.

Get notified when there are additional replies to this discussion.