Exchange 2010 and Exchange 2003 Coexistence
We are transitioning from Exchange 2003 to 2010.
The two will coexist for a while.
The single HT/CAS/MBX 2010 server will be a hybrid server for the eventual migration of mailboxes to Office 365 (but that's for another day)
The question I have is:
All users know this as the OWA url:
https://domainname.com/exchweb/bin/auth/owalogon.asp?url=https://domainname.com/exchange/&reason=0
If I wanted to setup OWA redirection, what syntax would I use?
example: Set-OWAVirtualDirectory CAS1\exchweb* -ExternalURL https://webmail.domainname.com/OWA -Exchange2003URL https://domainname.com/exchange
I want to avoid telling users a new URL but I am not sure what to set the OWAVirtualDirectory to(I am just guessing with the example above). I realize there are redirects to OWA at Exchweb and that there is no path past "bin"... So how do I handle this?
Thank you!
-KB
The two will coexist for a while.
The single HT/CAS/MBX 2010 server will be a hybrid server for the eventual migration of mailboxes to Office 365 (but that's for another day)
The question I have is:
All users know this as the OWA url:
https://domainname.com/exchweb/bin/auth/owalogon.asp?url=https://domainname.com/exchange/&reason=0
If I wanted to setup OWA redirection, what syntax would I use?
example: Set-OWAVirtualDirectory CAS1\exchweb* -ExternalURL https://webmail.domainname.com/OWA -Exchange2003URL https://domainname.com/exchange
I want to avoid telling users a new URL but I am not sure what to set the OWAVirtualDirectory to(I am just guessing with the example above). I realize there are redirects to OWA at Exchweb and that there is no path past "bin"... So how do I handle this?
Thank you!
-KB
ASKER
It is the way the client has it set up.
It is a separate domain completely and yes it is just domainname.comh/exchweb/bi
the challenging part of this is:
how do you make the 2010 virtual directory redirect (as the IIS path /exchweb/bin/auth/ does not exist)?
Users will ride in on that long URL and there will be no matching path in IIS - right?
It is a separate domain completely and yes it is just domainname.comh/exchweb/bi
the challenging part of this is:
how do you make the 2010 virtual directory redirect (as the IIS path /exchweb/bin/auth/ does not exist)?
Users will ride in on that long URL and there will be no matching path in IIS - right?
You would have to have some kind of Address Rewrite function possibly. Maybe Application Request Routing (ARR)?
I think this is just a time you say.
"Hey, look, the URL got way shorter and easier. Now its just domainname.com/owa. Isn't Exchange 2010 great?"
That would be the route I'd take.
I think this is just a time you say.
"Hey, look, the URL got way shorter and easier. Now its just domainname.com/owa. Isn't Exchange 2010 great?"
That would be the route I'd take.
ASKER
LMAO! okay that is what I was thinking.
So you don't think you would be able to create the path or what about an asterisk - how is that used?
So you don't think you would be able to create the path or what about an asterisk - how is that used?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
And -Exchange2003URL would be a brand new name. For example. legacy.domainname.com. Now you would need to create legacy in your external DNS and it would need a separate public IP. And require ports 80/443 open to it.
So for example.
Set-OWAVirtualDirectory “EXCHANGE\OWA (Default Web Site)” -ExternalURL https://<original URL>/OWA -Exchange2003URL https://legacy.domainname.com/exchange
I am curious though. This is the URL your users currently know?
https://domainname.com/exchweb/bin/auth/owalogon.asp?url=https://domainname.com/exchange/&reason=0
Do you have a wildcard record such as @ that is pointing everything to the Public IP of your Exchange Server? Not using mail.domainname or webmail.domainname for example?