Troubleshooting IEM Android Device actions

Technote (troubleshooting)

Problem(Abstract)

How to troubleshoot the Android Device actions remaining in open state.

Resolving the problem

There are various reasons to modify a IEM Client site. The most common is that the IEM Server/Relays are not able to send UDP messages to the IEM Clients due to network constraints. IEM uses a polling mechanism which can be configured via the IEM Client settings so this can be done on a client basis manually or by a TASK and does not required agent restart.

4. Check Analysis 181 : "Google Cloud Messaging (GCM)". Since it has a last GCM message field and a last message received time and these values come directly from the agent you can use them to figure
out if messages are being sent and received, or if they are not being sent at all. If the value in that analysis changes but the client doesn't report then we'd be dealing with a complete different problem. You should open Analysis 181, check the value of last GCM message time, then issue a command like a "lock screen" against a problematic device and check if/how long it takes for the value to change.

5. Despite of polling the Android agent will report once every 3 hours, or once every 6 hours, depending on when you set up you deployment. However, this is configurable and you can change it at any time by Fixlet "ID118 :"Android Agent Setting: Enable Command Polling" in the MDM site.

Note : You should also note that enabling command polling or bumping up its frequency is gonna make the agent use more battery :