Google Apps for Domains and Email client

---

Anyone managed to get Exchange ActiveSync working on the Tab Email client with a Google Apps for Domains account?

I know my domain is set up correctly, because I can use ActiveSync support on my Desire with these accounts, but on the Tab although everything seems to be ok I do not get any email in my Inbox and in "Accounts & Sync" settings, there is only the option for Contacts and Calendar sync.

Regards,

Dave


Sent from my GT-P1000 using Tapatalk

exchange setup could not finish: Unable to connect server

---

Mine doesn't connect at all. When I checked at mail.mycompany.com phone option I see it already register but couldn't complete the registration but got access denied message on access state.

Anybody have this issue and know how to fixed it?

Below is the detail info from exchange server (2010 version):

Status: OK



First sync:
11/7/2010 5:34 PM
Last successful sync: Not Available
Folders synced: 0

Device name:
Not Available
Device model: Android
Phone number: Not Available
Mobile network: Not Available
Device type: Android
Device ID: validate
Device IMEI: Not Available

Device OS:
Not Available
Device language: Not Available
User agent: Android/0.3

Access state:
Access Denied
Access set by: Security Policy Application

Policy applied:
Default - Not applied
Policy updated: Not Available
ActiveSync version: 12.0

additional info

---

Sorry forgot to mention, I've also set to accept all SSL certificates. Still not working..

Somehow it works, but only one time and cannot redo

---

Just wanna update this thread. After hard reset for the third time suddenly the active sync connection is working and show a pop up of whether I want to continue being forced to have a security policy forced to Galaxy Tab.

It loads around 2 minutes, then goes to security setting and set screen lock.

After that the account sync!

When I try adding one more exchange account it fails with the above error message again.

A bug in the android mail app for pushed security policy, perhaps?

Make sure you have "Allow non-provisionable devices" checked in exchange.