Quantcast
Channel: Exchange Server 2010 forum
Viewing all articles
Browse latest Browse all 8820

From 2003 to 2010, iPhone ActiveSync co-existence

$
0
0

I am planning for a 2003 to 2010 migration that we hope to happen very soon. The only outstanding question is: when we promote the 2010 CAS, will this break iPhone ActiveSync users that still have mailboxes on Exchange 2003?

I have read all morning long on this issue. See link:http://msexchangeteam.com/archive/2009/12/08/453472.aspx

It appears Window Mobile phones will support CAS proxy or redirecting to the Exchange 2003 front end box. However, the iPhone may not fully support all of the ActiveSync protocols. I haven’t been able to find if the latest iPhone OS fixes this or not. I built a test lab with Exchange 2003 and 2010, but torn it down already. I may have to build another one to test this issue. : (

From the link:
Important: Some third-party ActiveSync devices advertise support for protocol version 12.1 or later; however, they do not correctly process the 451 error response by updating the device profile. For these devices you will have to manually update the namespace in the device ActiveSync profile once CAS2010 has been deployed with the legacy.contoso.com namespace.  Please contact your device manufacturer to determine when they will provide support for redirection.

Is the iPhone one of these devices that do not fully support 12.1? I haven’t been able to find any information. Where would I go to “update the namespace in the device ActiveSync profile once CAS2010 has been deployed with the legacy.contoso.com namespace.” Does the "device ActiveSync profile" mean the iPhone settings?

It wouldn’t be the end of the world if we had to send an email to users to let them know they need to change the hostname on their phones and another one when we move them to 2010. But we need at least a few days lead time. Thanks for your help.


Viewing all articles
Browse latest Browse all 8820

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>