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:
![dmitryM_4-1717091927599.png dmitryM_4-1717091927599.png](https://community.meraki.com/t5/image/serverpage/image-id/37631i2745B4B54AD02D0B/image-size/medium?v=v2&px=400)
When the profile is pushed to Windows 11 machine - it is missing all of the above:
![dmitryM_1-1717091485088.png dmitryM_1-1717091485088.png](https://community.meraki.com/t5/image/serverpage/image-id/37628i01BBCE4FBF691B48/image-size/large?v=v2&px=999)
If the same profile created manually on the machine using same guidelines - it works as expected and the XML looks like this:
![dmitryM_3-1717091858583.png dmitryM_3-1717091858583.png](https://community.meraki.com/t5/image/serverpage/image-id/37630i2CAEFB88AEEF357A/image-size/large?v=v2&px=999)
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!