Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 210
  • Last Modified:

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
0
K B
Asked:
K B
  • 3
  • 2
1 Solution
 
Gareth GudgerCommented:
You would make the -ExternalURL whatever you want users to continue to point to.

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?
0
 
K BAuthor Commented:
It is the way the client has it set up.
It is a separate domain completely and yes it is just domainname.comh/exchweb/bin/auth/....
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?
0
 
Gareth GudgerCommented:
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.
0
 
K BAuthor Commented:
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?
0
 
Gareth GudgerCommented:
Not sure if a asterisk would work. Think you would need to do some kind of URL rewrite with ARR. But personally I would push them to accept the new URL.

Here is an article on URL rewrite with ARR. ARR is a free add-in for IIS.
http://www.msexchange.org/articles-tutorials/exchange-server-2013/mobility-client-access/iis-application-request-routing-part3.html
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now