Android device enrollment and reporting delays

If you are experiencing significant delays in Android devices reporting to the BigFix WebUI MCM portal or during enrollment/unenrolling, consider the following troubleshooting steps:

  1. Upgrade Components: Ensure BigFix MDM and plugin components are up to date with the latest versions.
  2. Check Firewall Rules: Ensure that all required Google API URLs (listed in the BigFix documentation for Android, specifically `oauth2.googleapis.com`, `accounts.google.com`, `cloudresourcemanager.googleapis.com`, `androidmanagement.googleapis.com`, `iam.googleapis.com`, `pubsub.googleapis.com`, `www.googleapis.com`) are whitelisted and accessible on TCP port 443 from the Android MDM server.
  3. Verify DNS Resolution:
    • Execute sudo docker exec -it androidmdm nslookup oauth2.googleapis.com`on the MDM server (or Podman if applicable).
    • If DNS resolution fails, ensure the MDM server is configured to use a DNS server accessible from its network (especially if in a DMZ).
  4. Test Connectivity to Google APIs:
    • Execute sudo docker exec -it androidmdm nc -zv oauth2.googleapis.com 443 on the MDM server (or Podman if applicable).
    • Confirm that the connection shows as "open".
  5. Review MDM and Plugin Logs: Check `android_mdm.log` and `MDMPlugin.log` for specific error messages related to Google API connectivity, as these logs provide more detailed information than `android-mdm_opstate.json`.
  6. Reinstall Android Plugin: If the `plugin opstate.json` shows errors, consider reinstalling the Android plugin.