Troubleshooting SM Clients that Fail to Check-in to Dashboard
This article provides some basic troubleshooting steps for SM-enrolled devices that fail to check into Dashboard.
For all platforms, please verify that you've already configured your firewall per this knowledge base article: Configuring your Firewall for Meraki devices to communicate with the Meraki cloud
Devices cannot communicate with Dashboard when a proxy server is in use.
Windows
Devices Enrolled via Agent
- Does the device have an Internet connection?
- Open up your task manager and see if m_agent_service.exe is currently running. If it has stopped responding, you can restart it by doing the following:
- Open up the Run window and type in services.msc
- Look for a service called "Meraki Systems Manager Agent" and start/restart it.
- Ensure that the service is set to "Startup Type: Automatic".
- Check the agent log file (for Agent ≤ 3.6.0, logging is saved to C:\Windows\Temp, for agent ≥ 3.7.0 logging is saved to: C:\ProgramData\Meraki\Systems Manager Agent\Logs). There should be several log files in that directory that start with m_agent_service. This log file may provide context for why the agent cannot check in. For more information see Windows Logging and Troubleshooting.
Devices Enrolled via an MDM Profile
-
Does the device have an Internet connection?
-
Is the device online and unlocked from any passcodes?
-
Does the MDM profile show up under Settings > Accounts > Access work or school'? You can also search 'Connect to work or school' in your Windows menu to find the below page.
Mac OS X
Devices Enrolled via Agent
- Does the device have an Internet connection?
- Open up a terminal interface and run "ps aux". Verify that the following is an entry "/usr/sbin/m_agent --verbose --log /var/log/m_agent.log --pid-file /var/run/m_agent.pid". If this does not exist, then you may need to re-install the Systems Manager agent.
- You can use the terminal to cat /var/log/m_agent.log. This log file may provide context for why the agent cannot check in.
Devices Enrolled via an MDM Profile
-
Does the device have an Internet connection?
-
Is the device online and unlocked from any passcodes?
-
Do you see a Meraki MDM profile installed locally on the device? This can be found under the macOS Settings > Privacy and Security > Profiles. If you don't see any Meraki MDM profiles than this device will need to be re-enrolled into the Meraki Systems Manager MDM solution.
iOS
- Is your device connected to a stable internet connection?
- Is the device online and unlocked from any passcodes during 'force check-in'?
- Look in Settings > General > Device Management. Are the Meraki Management and any additional configured profiles listed there? If so, does the Meraki Management profile description accurately reflect that of your Systems Manager dashboard network name?
- Install Apple Configurator to a workstation, plug in the iOS device via USB, and look at the console output of the device. You should see events in the output that start with "mdm".
Android
- Does your device have an Internet connection?
- Is it online and unlocked from any passcodes?
- You can clear the cache of the Systems Manager Android app by going to Settings > Application manager > Systems Manager and then select "Clear cache".
- If you've downloaded the Android Developer Tools, you can check the console output of your Android device in real time (while running a Systems Manager agent) if you go to the android-sdk\platform-tools\ directory and run "adb logcat".