Hello community! Currently evaluating Meraki SM with out Meraki networking. Trying out simple things. One of them is to create WiFi profile for EAP-TLS using Meraki Local Auth. No matter what I try, not able to connect to Meraki AP with the pushed profile. If I recreate the same connection manually using same settings, it works flawlessly.
While investigating - noticed that Windows WiFi profile that Meraki pushes - lacks the information, specifically Trusted CA, that prevents the connection. So...
In SM the profile looks like this:
When the profile is pushed to Windows 11 machine - it is missing all of the above:
If the same profile created manually on the machine using same guidelines - it works as expected and the XML looks like this:
If I manually add those missing lines into XML, then it works. So, what gives?
Is this a known bug? Or am I missing a step or two?
Appreciate your pointers and insight! Thanks!
