Recently, I faced a challenge while trying to deploy a wireless profile from the Meraki Systems Manager MDM platform as I transitioned to Intune. Unfortunately, the deployment didn’t go as planned. Windows machines were either timing out after several failed attempts or failing to connect altogether when using the WPA (automatic) feature. Although the MDM successfully applied the wireless settings to Android, MacOS, and iOS devices, Windows continued to be problematic. The key challenge was inspecting the settings profile sent to the Windows machines. I noticed that the MDM wireless profile format was similar to the Netsh wlan profile export, but I needed to find a way to access this information on the Windows client. The breakthrough came with the use of SyncML Viewer, a tool designed for monitoring MDM transactions between clients and the MDM. By extracting a functional manual wireless profile configuration using Netsh and comparing it with the MDM’s deployment, I pinpointed the issue. Although SyncML Viewer displayed certain characters differently, a simple find-and-replace adjustment aligned everything accurately. Ultimately, I discovered that the root of the problem was the absence of a trusted certificate thumbprint in the wireless profile, which required me to submit a support ticket to the vendor. If you ever need detailed insights into MDM transactions, I highly recommend using SyncML Viewer.
Leave a Reply