Skip to Content

Afaria Package Server Issue

Dear Mobility Experts,

We are in process of Afaria Implementation for one of our customer. We have successfully installed Afaria server (Afaria 7 SP05 HF6) and it’s components and able to do the Enrollment but unable to push the policies from Afaria Server to Device (Android Devices).

Also after successful enrollment Package Server Details are not being populated on the Afaria client whereas Afaria & Enrollment Server details are available on Afaria Client.


We have following pots open 80 & 443 (Bi directional), 8081 (Uni directional : External to Afaria Server)


I quick on this issue will be appreciated.

Midhun VP - SCN Member of the Month May 2014 @Jitendra Kansal Former Member  Former Member Former Member Former Member



Best Regards,

Vishal Jain


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

8 Answers

  • May 06, 2015 at 11:52 AM

    Vishal,

    Make sure in your server configuration, that under component, the package server directory is defined correctly.  If you cannot push policies to android it sounds as if your device communication is not configured correctly as the android connects directly to the Afaria server as well as enrollment server.  Check the device communication page, and verify that the communication address is reachable by the device.  If that is not the correct address correct it and regenerate an new enrollment.

    Tracy

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 06, 2015 at 12:00 PM

    And ensure that GCM Project ID is populated to client with Enrollment policy

    Add comment
    10|10000 characters needed characters exceeded

    • Yes GCM Project ID is populated to client with enrollment policy.

      But GCM diagnostics are showing in Red. Below is the error.

      Note: Outbound connection from the Afaria server to the Google Cloud Messaging(GCM) server allows for sending security actions and for initiating Android device connections to the server to apply policies. Last Update: 5/6/2015 5:40:07 PM Estimated Next Update: 5/6/2015 5:45:07 PM Diagnosis: Failed. The Afaria server could not connect to the GCM server. Possible Problem: Project ID from Google Developers project website required for server configuration
      Google Cloud Messaging service status from Google Developers project website
      Server configuration
      Proxy server blocking required address and port traffic
      Server firewall blocking required address and port traffic
      Enterprise firewall blocking required address and port traffic
  • avatar image
    Former Member
    May 06, 2015 at 10:03 AM

    pls port logs here..

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 06, 2015 at 12:07 PM

    Hi Vishal,

    Check the GCM key and connection from Afria Admin console and also check if you have enabled the "collect s/w and h/w" inventory for Android devices> under Android enrollment policy.

    Also share the logs from Afaria server. Further you can do additional debugging on Android if not resolved.

    Regards

    Rahul

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 06, 2015 at 12:43 PM

    Which port are you using for Package server. I would say use http method for communicaton.

    Add comment
    10|10000 characters needed characters exceeded

    • We are using http communication on port 80 for connecting to package server.

      but somehow it's not reflecting on Afaria Client whereas we are able to see the details for Afaria Server aand Enrollment Server.

  • avatar image
    Former Member
    May 06, 2015 at 12:55 PM

    In my case,  I checked Enterprise firewall rules.

    Ensure that Afaria server can reach GCM addresses

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 06, 2015 at 12:58 PM

    which android OS version you are using? Is your GCM connection coming successful when tested from Afaia console?

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 06, 2015 at 01:14 PM

    Vishal,

    Under the device communication settings cross check the communications port for devices. also open port 81(in disabled) for http device coomunication. also make sure that device communication address is correct on both Afaria and Device.

    I ahve experienced that some time a FQDN name in device coomunication settings doesnot work but a valid public ip works at the same time. you can test this workaround.

    Regards

    rahul

    Add comment
    10|10000 characters needed characters exceeded