Windows 11 on MX

Solved
Happiman-v2
Here to help

Windows 11 on MX

Does MX detect Windows 11 as an OS? Even though I have a few of them, I do not see them on my network.

1 Accepted Solution
RaphaelL
Kind of a big deal
Kind of a big deal

I don't think I have ever noticed that all my Win11 PCs are labeled as Win10 or as 'Other'

View solution in original post

5 Replies 5
RaphaelL
Kind of a big deal
Kind of a big deal

I don't think I have ever noticed that all my Win11 PCs are labeled as Win10 or as 'Other'

Happiman-v2
Here to help

Yes, I think  I also got a bunch of "Other" but never Win11. It's interesting that it's not Win10 but Other.

alemabrahao
Kind of a big deal
Kind of a big deal

Meraki uses a bunch of fingerprinting methods, including LLDP, MAC address lookups, and traffic profiling, among other things. It's not an exact science, as you've seen. 

 

Some clients may misidentify themselves when specifying the User-Agent string field of an HTTP GET request. Device type policy enforcement is done on a best-effort basis, dependent upon the information that the client provides. When needing to enforce security-focused policies based on device type, please leverage solutions such as Meraki Systems Manager, or Cisco ISE. 

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
wusene
New here

I'm pretty new to this forum, so forgive me if I'm not entirely up to speed, but I've had some experience with Windows 11 on MX. It should definitely detect Windows 11 as an OS, at least it did for me. But, I did run into a similar issue with not seeing them on my network. It turned out to be a Windows Firewall thing for me. Maybe check your network settings there?

alemabrahao
Kind of a big deal
Kind of a big deal

Meraki uses a bunch of fingerprinting methods, including LLDP, MAC address lookups, and traffic profiling, among other things. It's not an exact science, as you've seen. 

 

 

 

Some clients may misidentify themselves when specifying the User-Agent string field of an HTTP GET request. Device type policy enforcement is done on a best-effort basis, dependent upon the information that the client provides. When needing to enforce security-focused policies based on device type, please leverage solutions such as Meraki Systems Manager, or Cisco ISE. 

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels