Afaria Package Server Issue

[former_member234218]

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.

 

Best Regards,

Vishal Jain

[former_member196814]

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

[tracy_barkley]

Rahul,

Good suggestions, and android needs to connect to the Afaria server not just the enrollment so the device comm address is very important.  if using HTTP and as Rahul suggested, port 81,

You should have the address on the device communication line like this.

HTTP://IPaddress:81

Then recreate the enrollment policy/enrollment code.  Re-enroll the device.

Tracy

Sr. Tech Support Engineer

SAP Active Global Support

[former_member234218]

Currently we are using http://<Server Name>:8081 for device communication.

Is that ok ?

[tracy_barkley]

As long as the http checked on the same screen above is set to 8081.  Yes.

Tracy

[Former Member]

This message was moderated.

[former_member196814]

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

[former_member196814]

Check if all relay server detail page in Afaia console is empty

[former_member686053]

In my case,  I checked Enterprise firewall rules.

Ensure that Afaria server can reach GCM addresses

[former_member196814]

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

[former_member234218]

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.

[former_member196814]

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

[former_member234218]

Dear Rahul,

Thanks for your reply. We have checked Collect S/w and H/W Inventory is enabled in configuration policy. I've posted the Afaria Server & Client logs while replying to Tevfik.

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

There might be some issue with GCM. Below is the diagnostic of GCM Connectivity.

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

[former_member196814]

Are you using a relay server also?

[former_member234218]

No there is no realy server. Only corporate firewall is there in between.

[former_member686053]

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

[former_member234218]

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

[tracy_barkley]

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

[former_member234218]

Yes packge server virtual directory is defined correctly which is "ps".

[former_member686053]

pls port logs here..

[former_member234218]

Dear Tevfik,

Please find attached Server and client logs.

BR,

Vishal Jain

Afaria_server_log.txt.zip