Afaria not able to Enroll - Android

[Former Member]

Hi,

I am trying to Enroll an Android device to Afaria server, generated an enrollment code and installed Afaria application in the device. I created the Enrollment policy and generated the enrollment code but when I try to enroll the device using it, I get a "not authorized to run the channel" error message and a message to enter a valid username and password.

After this, from the afaria administrator ui I see the Android device as approved like in picture1.png. What does this mean? How do I authorize a device to run a channel? Is the device enrolled?

Anyone had the same problem? Do you have any ideas as to how I can solve it?

Thanks,

Lucía Cianelli

Thanks,

[former_member686053]

Really no idea.

[former_member686053]

What about server log?

I think your SSP enrollment code time period too long or too short.

[Former Member]

There are no logs on the server during the enrollment. Is the device connecting to the server.

Regards,

Annuk

[former_member686053]

creating GCM ID is very similar like C2DM.

And in Afaria 7 SP1 I see GCM component, not C2DM.

[Former Member]

Hy,

I have sometimes the same problem maybe my solution helps you.

Have you tried to configure a simple inventory policy (It means a policy with only Inventory enabled) and bind it to the group where the android device should in.

Best regards

Michael

[Former Member]

Yes it did! Thank you!

I was having the following log in the server: "XRS1372: This user  has no matching profiles.  The connection was refused.  EXPLANATION: Only users assigned to a profile are able to run channels.  ACTIONS: Verify that user has a matching profile."

After creating the configuration policy for the group with inventory enabled, it was resolved.

I don't understand why this point is no so clear in the documentation.

Thanks!!

[Former Member]

Hi Lucia,

I am also trying to enroll an Android device with the Afaria server but I am not able to go through. What are the steps for enrolling an android device. We followed the steps given in  the installation guide and the Afaria videos but still not able to enroll. where are we going wrong.

We created an enrollment code and tried enrolling the device using the self service portal. When we install the Afaria client on the device, it asks for an enrollment code. After inserting the enrollment code, it asks for a username and password. Which is this username and password that the client is asking.

We don't have an LDAP configuration.

Regards,

Annuk

[former_member686053]

Lucia,

As workaround, create a dummy comfiguration policy. And link it  "All Devices", which is preconfiguredby afaria.It solves your problem.

By the way, always use static group for enrollment polcies. Not dynamic.

Anwaar,

You can use Local User accounts.

But  I think you should change enrollment/SSP  virtualt Site uthentication settings. If you dont ask any username or password, you should enabled anonymous Auth. And disabled Windows auth.

You can see what i  mean in attachement

[Former Member]

Hi Tevfic,

Thanks for your reply.

Will disable the windows settings and enable anonymous authentication settings.

Regards,

Annuk

[Former Member]

It looks like when you installed the enrollment server the authentication checkbox was ticked.

Try running the install for the enrollment server again and uncheck the box.

[Former Member]

Hi,

Tevfic/Steven Thanks for your reply.

Disabled windows authentication and enabled anonymous authentciation. It got authenticated. But now we are getting the following error:

ONS1018: Could not determine the Client Address for the specified client, "SERVER NAME"
, with Client GUID,{bdsbjdjsd}

Where are we going wrong. Please help.

Regards,

Annuk

[former_member686053]

In, http://frontline.sybase.com/support/resolutionDetails.aspx?KBID=7702

Knowledgebase Article ID #7702

Summary:   When an Outbound Notification is sent to a Android device the logs report ONS1018: Expected to notify the Client 

Resolution ID:     7702 

Create Date:   10/14/2011 

Last Modified:   6/12/2012 

SYMPTOM:

Outbound Notification is sent to an Android device and the logs show:

ONS1018: Expected to notify the Client, "CLIENT1", with Client GUID, "{GUID1}" at Address "IP ADDRESS", but instead found the Client, "CLIENT2", with Client GUID, "{GUID2}" at that address.

CAUSE:

Outbound Notification can not use the IP address when connecting to Android devices

SOLUTION:

Use SMS, SMS over SMTP or C2DM

[Former Member]

This message was moderated.

[Former Member]

Hi Tevfic,

I am using Afaria 7. But it shows me C2DM server  in the server components.

But C2DM has been deprecated and now Google supports GCM.

GCM requires server key and the project id instead of the c2dm account. How do we move forward. Do we require any upgrade for this purpose.

Regards,

Annuk

[former_member686053]

I think only URL changes in GCM.

Shown in atatchement

Additinally, C2DM and GCM have same step

[Former Member]

Hi Tevfic,

Thanks for your reply.

So I would need Afaria 7SP1 for GCM. My Afaria administrator shows C2DM. So  I would need an upgrade for Afaria.

Regards,

Annuk

[former_member686053]

Hmm Afaria7 Sp1 is not enough. You should apply Hotfix 2 too.

Explained:

1. Istall Afaria 7 and load sp1 OR
   install Afaria 7 sp1
2. Install Afaria HotFix 2 http://frontline.sybase.com/support/fileDownload.aspx?ID=2440

Install instructions taken
from release notes:

1. 1. Copy the Package,
   7AfariaFx1.zip, to a temporary directory on the hard drive.
2. 2. Browse to the temporary
   directory and unzip the Package file.
3. 3. Stop Afaria services on
   your server or farm.
4. 4. On the Afaria Server,
   run the server update by running the extracted file, 7AfariaFx1.exe.
5. 5. On the Afaria Admin,
   from the AdminUI folder, created by extracting the 7AfariaFx1.zip file, run the
   setup.exe program.
6. 6. On the Afaria Server
   Host, from the AfariaServiceHost folder, created by extracting the
   7AfariaFx1.zip file, run the setup.exe program.
7. 7. Restart the computer to
   apply the changes.

[Former Member]

Hi Tevfic,

Downloaded the Afaria service pack and hotfix2. When I try to enroll an android device via SSP, we are not able to enroll the device successfully.

Attached are the screenshots of the logs available on the device.

Where are we going wrong?

Regards,

Annuk

[former_member686053]

Check out enrollment policy that , this enrollment policy should be liked for "all devices" Dont use dynamic groups for linking enrollment policy.Because enrollment polict runs before inventory checks.

Ad result  try add "All devices" group se selected in enrollment policy.

[Former Member]

Is there a configuration policy linked to the enrollment policy? If not give that a try