Comments on: Installing your first Exchange 2010 CAS or the truth about Exchange2003Url – Part 1

By: anandamira

anandamira — Sat, 17 Sep 2011 09:36:00 +0000

You have quite literally preserved my sanity with the silent redirection workaround. I inherited an Exchange 2003 Cluster that had never been configured with a front-end server for reasons far to tedious to get into here. Suffice it to say that I have been tearing my hair trying to figure out how to gracefully deal with redirecting Exchange 2003 users to the correct OWA URL while we are migrating to 2010. Big fat kudos for you!

By: Jason Thomas

Jason Thomas — Wed, 18 May 2011 23:44:23 +0000

I'm running SBS 2003 (Exchange 2003) and want to move to Exchange 2010. It is published externally at https://owa.mydomain.com On SBS, Exchange 2003 in not in back-end / front-end mode. Our plan was to install Exchange 2010 on a new server and publish it to https://owa2.mydomain.com, and make that accessible externally as well. My thought is, everything continues to work as before (Outlook, Activesync) until a users mailbox is moved, at which point they will have to start using https://owa2.mydomain.com. Will this work?

By: Mk

Mk — Tue, 15 Mar 2011 01:23:46 +0000

do i need 2 seperate external ip addresses for this to work?? when i try this, i get the message, “your request couldn't be completed because no server with the correct security setting was found to handle your request”??

By: Brian

Brian — Mon, 22 Mar 2010 20:51:38 +0000

My issue is with a non intentet addressable domain e.g. mycompany.internal and the 2003 exchange server is in that domain (exch03.mycompany.internal), but the email addresses are internet addressable (itmanager@mycompany.com).

Exchange 2010 authenticates the user, determines the mailbox version is Exchange 2003 by performing a service discovery lookup in Active Directory, and retrieves the Exchange 2003 mailbox server FQDN of exch03.mycompany.internal. Then attempts to proxy the connection to the Exchange 2003 mailbox server's Microsoft-Server-ActiveSync virtual directory. Somthing like this (frm the Exchange 2010 IIS log):

POST /Microsoft-Server-ActiveSync/default.eas User=itmanager&DeviceId=foo&DeviceType=PocketPC&Cmd=FolderSync&Log=PrxTo:exch03.mycompany.internal_LdapC2_ 443 contosouser5 10.20.100.117 MSFT-PPC/5.1.2301 200 0 0 189

Exchange 2003 activesync will not accept connections that are not addressed to the suffix domain of the users email address in this case mycompany.com. If we can direct Exchange 2010 to proxy to exchange 2003 using the internet addressable FQDN oldmail.company.com or similar that would work.

Thoughts?

By: Antoine Khater

Antoine Khater — Sat, 20 Mar 2010 16:08:19 +0000

Hi Brian, in short exchange 2010 will proxy ActiveSync requests to the 2003 mailbox server as long as Integrated authentication is enabled the ActiveSync virtual directory in Exchange 2003.

By: Brian

Brian — Fri, 19 Mar 2010 16:11:32 +0000

What about Active Sync?

Can you set the path Exchange 2010 uses to Proxy Active Sync requests?

By: Antoine Khater

Antoine Khater — Sat, 13 Mar 2010 12:39:12 +0000

Hi Brian, your answer is on part 3 of this tutorial http://www.zerohoursleep.com/2010/03/installing-y...

By: Installing your first Exchange 2010 CAS – Part 3 | Zero Hour Sleep

Installing your first Exchange 2010 CAS – Part 3 | Zero Hour Sleep — Fri, 12 Mar 2010 20:41:10 +0000

[...] is the third, and last, part of the "Installing your first Exchange 2010 CAS" tutorial. In part 1 we discussed migration from Exchange 2003 to Exchange 2010, In part 2 migration from Exchange 2007 [...]

By: Antoine Khater

Antoine Khater — Fri, 12 Mar 2010 19:26:12 +0000

Hi Brian, this is actually the subject of part 3 of this tutorial you will have the answer in a few hours thanks

By: Bryan

Bryan — Mon, 08 Mar 2010 20:33:14 +0000

Ok so this is for 2003 what about a mixed 2003/2007 environment? I currently have 2007 CAS and using ISA to publish. Any users with mailboxes in 2003 get to OWA with out an issue. How is this handled now with the introduction of 2010? This is where i believe alot of people are becomming confused. So many people talk about 2003 or 2007 integration but very few speak of both. In any case will publishing legacy.domain.com and pointing that to my 2007 CAS take care of the users in 2003? Thanks