droid 2.2 froyo update, breaks exchange
ok i don't have time to research this.
exchange 2k7 with ALL updates, on server 2008 sbs 64bit
client has a bunch of droids working great on the 2.1 droid OS. one guy got the froyo 2.2 update today and his exchange immediately stopped working on the droid. his account works fine on other 2.1 droids.
so, it's a 2.2 issue and clearly tons of people have the same problem.
one suggested fix was to change IIS to "ignore" client certificates instead of accepting them.
some people elude to needing, or disabling, the pin policy in EAS. ours was never enabled and isn't enabled. will enabling it fix it?
what can i do to get this phone working, as all the other users will probably update to 2.2 tomorrow even though they were told not to.
please no answers like "get touchdown it rocks"
exchange 2k7 with ALL updates, on server 2008 sbs 64bit
client has a bunch of droids working great on the 2.1 droid OS. one guy got the froyo 2.2 update today and his exchange immediately stopped working on the droid. his account works fine on other 2.1 droids.
so, it's a 2.2 issue and clearly tons of people have the same problem.
one suggested fix was to change IIS to "ignore" client certificates instead of accepting them.
some people elude to needing, or disabling, the pin policy in EAS. ours was never enabled and isn't enabled. will enabling it fix it?
what can i do to get this phone working, as all the other users will probably update to 2.2 tomorrow even though they were told not to.
please no answers like "get touchdown it rocks"
Adrian Cantrill
Do you have a externally trusted SSL certificate on the BOX your droids are syncing to - the FRF91 update has a problem with self signed, or internally trusted (with added certificates on the devices) and seems to work fine when using externally trusted certs....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Let me know how you get on :)
ASKER
woolnoir you were exactly right - i changed the vsite for eas to 'ignore' client certs and it worked right away... wow i thought i did that before posting here but i guess not
now if motorola would just tell their users this rather than providing free touchdown licenses for their X users :)
now if motorola would just tell their users this rather than providing free touchdown licenses for their X users :)
No worries, I'm looking at recommending android adoption for my ORG too... issues like this make it constantly harder to recommend.
ASKER
i guess moto will have this "fixed" sometime in september - but, yeah that sucks :)
overall though, i find them a TON easier than dealing with the blackberry enterprise server software... iphones work ok but who wants AT+T and 100% five-bars even when you really have 1 bar.
overall though, i find them a TON easier than dealing with the blackberry enterprise server software... iphones work ok but who wants AT+T and 100% five-bars even when you really have 1 bar.
ASKER
for what it's worth, the droid1 still doesn't work with exchange 2010 sp1...
i ended up getting an "app installer" app to install a custom Email.apk file from here:
http://forum.xda-developers.com/showthread.php?t=821297
someone was nice enough to hack the built-in email application so it disregards the exchange requirements for password policies
i ended up getting an "app installer" app to install a custom Email.apk file from here:
http://forum.xda-developers.com/showthread.php?t=821297
someone was nice enough to hack the built-in email application so it disregards the exchange requirements for password policies