Major Exchange headache -- no contacts, calendar

[jldeitch]

We have a new Xoom WiFi, and would love the thing except for one major problem. When we connect our main Exchange account, it spins forever but downloads nothing -- no emails, contacts or appointments.

If we add an account that's email only, the emails come down and everything works as expected for that account. If I move contacts into one of these secondary accounts, then they no longer work.

We have similar issues with Touchdown for Tablets, except there no mail appears in the inbox -- only subfolders. Plus only today appears in the Calendar. Appears to be a Touchdown bug -- bad one.

We really, really want to keep this tablet. But it's going back unless we can actually access and use our email, contacts and calendar.

It's an Exchange 2010 server, and we're accessing it via https over ActiveSync. Any assistance is most appreciated.

 

[cwizardtx]

Can you connect any other android devices to it?

 

[jldeitch]

Yes -- no problem connecting other devices

We have two Droid Xs and a Droid Incredible attached to the server. No issues.

 

[Antebios]

What are you talking about? I connected to my company's Exchange account with no problem, and I was able to get to the company contacts and see my calendar on the XOOM.

Here is a trick that I found out:
When you add your login account enter in the format "\my_login_id". Notice that I being the login with a backslash "\". DO NOT enter your domain name.

 

[jldeitch]

/your_id

That's what I did. It apparently has something to do with the security settings back on the server. If anyone has any experience there, it might help us troubleshoot...

 

[dougvan]

Your Exchange administrator might be enforcing security settings (Required PIN, remote wipe, etc). Generally you are supposed to get a warning from android stating it is being required and asking you if you want to enable it. Any chance you said no to this?

One of my friends had almost the same issue and for some reason his phone wasnt acknowledging the requirements. He had to set them manually and then he got his contacts and emails.

not sure it's your problem but it might help

 

[jldeitch]

That sounds more than reasonable. I did hit "OK" when asked to allow Exchange to set the security parameters on the phone, so I know it was being asked to adhere to some standard.

What's the process for the manual setup you alluded to in your post? I'd like to give that a try.

Thx...

 

[DroidzFX]

Also check how many items you have in your mailbox. If you have over 20,000 you may have some trouble syncing.

Sent from my DROIDX using XDA Premium App

 

[Gwartan]

With the zoom it does not seem to use the "standard" MS Active Sync which allows just using your address and password then it auto configures based on settings in exchange.

When setting up my exchange accounts I entered the email address and password. When it went to auto detect I have to click cancel. Then go back and put the domain in front of the user name then add the address for the owa site (owa.server.xxx)

Do you have outlook? Go into the account settings then select your account then change. Look for the More settings button > then connection > Exchange Proxy Settings this will give you some idea what you need it it is configured.

So:
Domain\username
Password
server (owa address)
check use SSL

 

[hatxtrick]

That sounds more than reasonable. I did hit "OK" when asked to allow Exchange to set the security parameters on the phone, so I know it was being asked to adhere to some standard.

What's the process for the manual setup you alluded to in your post? I'd like to give that a try.

Thx...

Please don't take this the wrong way.. You should call your company/schools helpdesk or Exchange admin. The native email client is pretty easy to setup, from your description it sounds like you've got a local (device side) configuration problem.

When you are setting up the client, are you:
1. Entering the correct domain\username - if you are having problems try not adding domain\ . Instead enter your username with your company's FQDN (example: [email protected]) please note this is not the sane thing as your email address.

2. When entering your server info, you do not add the "xttps://" just enter the URL (example: Wrong - xttps://owa.xxxxx.. - Correct - owa.xxxxx.)

3. If your company is more than likely enforcing the EAS policy - if so once you successful configure the client you will be prompted to set a password/pin (if they set that as a rule) so if you get that far you should be golden....

Hope you get it working...

Cheers,
Hatxtrick


Sent from my Xoom using Tapatalk

 

[hatxtrick]

That sounds more than reasonable. I did hit "OK" when asked to allow Exchange to set the security parameters on the phone, so I know it was being asked to adhere to some standard.

What's the process for the manual setup you alluded to in your post? I'd like to give that a try.

Thx...

I haven't seen a responce from OP so I thought I'd pop a few screenshots off, as a walk through.

jldeitch one other possibility: Have you ever had a EAS type of device activated on your exchange server? i.e WMD (Windows Mobile Device), Palm, etc… any smart phone other than a *blackberry
(Please see * in next comment)
If you haven’t your exchange admin may need to enable that feature on your exchange account depending on how your company has setup account provisioning. .( Also if you carry a Blackberry for your organization you would still need to have the exchange active sync featured on your account. BB’s have their own server/account outside of exchange .
Also your company’s EAS policy may be setup to require encryption on the device & to not allow non-provisionable devices. (I’m not sure if the Xoom will pass the device encryption requirements, if not then the second part of the rule would block you from completing the activation.)
I’m an Exchange/BlackBerry admin for my company, we had to tweak the hell out of our policy to get the wide range of devices & Android OS levels to work with our EAS Policy. A good example is the OG Droid, once a EAS policy w/ a mandatory password (PIN) rule is turned on the devices would stop communicating with Exchange due to the inability to enter a PIN only a pattern screen lock, if we set our policy to allow non-provisionable devices, the user could partially active their device but most had trouble with features such as PUSH, calendars & contacts.
I’ve added a couple of screenshots of our ‘pretty generic’ EAS policy, to help you understand.