iPhone 3.1 Won't Sync w/ Exchange

Don't know if its any help but I've got a WORKROUND (Test system Exchange 2003 / Iphone 3G 3.1 )

It's 2 step
1. Iphone 3G will Sync with exchange when a connected Outlook client is running on the Domain. Startup an outlook client and leave it running. All new stuff will sync to the I-Phone no problems
2. If you want old stuff to sync then you need to have your outlook reorganise it. I found it easier to do with exchange webmail and you do it once only. I created a new folder under contacts then shifted all my contacts into it and then moved them back and hey presto all the contacts synced. Same with the E-Mail and the calendar. Didn't have a huge success doing this within Outlook but the Exchange webmail worked a treat.

As I said this is NOT a fix only a way my I-Phone 3.1 will sync continuously with my Exchange.

The problem lies with the fact that you have to leave an Outlook client running all the time and this may present a problem for mobile uses or users with strict logoff policies in the workplace. I simply fired up a virtual machine inside the domain and left outlook running on that until a proper fix is in place.

Hope this helps somebody

Can someone help me here?
(1)If the iphone 3G running 3.0 is currently lying to Exchange, why can't an iphone 3G running 3.1 lie also?
(2)If it is common knowledge that the 3G running 3.0 is lying, what is to stop Exchange from syncing with 3.0?
(3) From reading this discussion it appears that no one believes that Apple can or will correct this issue?

(1)If the iphone 3G running 3.0 is currently lying to Exchange, why can't an iphone 3G running 3.1 lie also? - Because 3.1 apparently purposely "corrected" the lying.
(2)If it is common knowledge that the 3G running 3.0 is lying, what is to stop Exchange from syncing with 3.0? - Nothing,
(3) From reading this discussion it appears that no one believes that Apple can or will correct this issue? - Referring to your first point, it's because 3.1 is actually a correction. Since the 3G doesn't support encryption (see here: http://support.apple.com/kb/TS2941) I think Apple believes there's nothing to "fix" as 3.1 is essentially a fix.

kinda sad, eh?

One thing is for sure. Apple has a made a lot of Blackberry converts (such as myself) really ticked-off.

Message was edited by: Larsim

Same here with me and trying to sync with Exchange Server 2007 at work. I found this..

http://www.dslreports.com/forum/r22999133-iPhone-31-breaks-Exchange-Sync-for-pre 3GS-phones

which proves that unchecking the 'require encryption' box fixes the issue. I can't see my work doing that though. How do you rollback to OS 3.0?

I know people laughed at my earlier post that the 3G - 3.1 Exchange sync problem was tied to the release of MMS, but I just received a text message from AT&T saying that MMS was now available and the only thing I needed to do was go to iTunes and "Check for Update, then restart your iPhone".

So, if I update to 3.1 I will get MMS but lose Exchange!

Message was edited by: JRB2

There is something else going on here. Our ActiveSynch policy does NOT require device encryption. Most of the users that have upgraded to 3.1 can connect. However, one user cannot and gets the device encryption message. The only difference is the one user appears to have an older device, model MB704LL. We don't seem to have the issue with MB702LL devices. So, Apple does have some work to do.

This will be addressed in Exchange Server 2010. Exchange Server 2010 will support device profiling. This will allow admins to change security policies based on a group of similar devices. It will also be possible to limit device access to only certain features of Exchange based on this grouping.

This was done to address issues with the iphone and many other devices that only partially support the Activsync feature set.

I am an admin of an Exchange 2007 infrastructure and I do not support removing the policy requiring encryption on the device. I am really looking forward to eliminating those devices that ignore policies in Exchange 2010. I am responsible for making sure e-mail policies are enforced. How can I do that is the manufacturer of the devices is activly circumventng the policies sent to the device.

The iPhone, at least in our company, is an option only when the user purchases the device. No support is given for the device.

Thank you to everyone here who has provided helpful information. My question is pretty basic. Is this a problem for iPhone 3G and Exchange 2003 servers? All the references seem to be for Exchange 2007 servers with SP1 installed.

This is not a problem for Exchange 2003. The version of Exchange Activesync that showed up with SP2 (For Exchange 2003) had only a few policies. None of them pertained to requiring that data be encrypted on the device.

The "Require Device Encryption" policy was introduced with Exchange 2007. Since none 3GS devices lack the ability to encypt data on the device they cannot enforce the policy requirement if it is set; hence they will not be allowed to sync.

This is a failing of Apple not building in proper support for the Exchange Active Sync protocol into their devices. Software based encryption is possible (It happens on Windows Mobile just fine). Apple chose not to provide a software/OS update to support it. I guess they would prefer that users buy newer hardware than provide software updates to older hardware.

1. Probably becuase Microsoft said something like "Either enforce the policies if they are set or lose your licence to build in support Exchange Activesync." I am IT admin who administers Exchange and mobile devices. If I could have blocked the non-conforming devices I would have. Exchange 2010 will remedy this with device identification and polling. We will be able to interrogate the device to find out what capabilities it has. If it can not support a policy we can then block the device. Lying to Exchange will no longer work.

Imagine having a digital lock that you can just lie to and the door unlocks and lets you in. Basically makes policies worthless if they can not be enforced.

2. Exchange did not have the ability to identify which devices were connecting and then interrogate them to determine their capability. This will be fixed in Exchange 2010. Most vendors assume that when they license technology (Like Exchange Activesync) that the licensee will actually abide by the agreement.

3. OS update 3.1 only supports encryption on devices that have an extra encryption processor. Apple could have provided software encryption for older devices that lacked hardware assist chip for encyption. They did not do this. Most likely to force people to upgrade.

I think this was the best description of the problem that I have come across

Apple explains iPhone OS 3.1 Exchange changes
http://news.cnet.com/8301-13579_3-10354209-37.html

Hi

Apologies of this has been answered and I have missed it. Will a 3GS running 3.1.2 work with Exchange 2003, or does it only work with Exchange 2007?

Many thanks for your help 🙂

Well, a 3GS running 3.1.2 and Exchange 2003 doesn't work either. Starting to wonder if there are simply some settings not right with our Exchange Server. We're able to authenticate with the server, but nothing syncs at all. Just an empty Inbox, Contacts and Calendar are available and outgoing messages fail to send.

Any ideas?

I think Apple had (has) a simple fix available they overlooked. Replace all the phones that can't meet the standard.

For those people who need and rely on this mail service, they should supply the hardware which actually meets the stated abilities.

Every phone sold and used prior to 3.1 which accessed Exchange encrypted services compromised the security of the organization which used them.

I have been an Apple user and advocate for years, but this was a "there is NO excuse for this" stupid blunder of major proportions that they should take equally serious measures to address

<Edited by Host>