[Last Call] Learn about multicloud storage options and how to improve your company's cloud strategy. Register Now


OWA 2003 and 2010

Posted on 2011-09-27
Medium Priority
Last Modified: 2012-05-12
I have user mailboxes on 2003 and a few on 2010 (testing phase). My mailbox on 2010 can send and receive emails no problem. But when I go to https://webmail.domain.com I get the OWA 2010 login screen but when I try to login nothing happens - just freezes.

When a user who has a mailbox on 2003 goes to the same link and is presented with the 2010 OWAlogon scrren and logs in they are then redirected to their OWA (2003 format).

How can I get it to work with users on 2010?
Question by:tolinrome
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 3

Author Comment

ID: 36713250
I think the problem may be that the redirection (legacy hostname?) redirects my logon credentials to the 2003 Echange Server and doesn tfind it there since its on 2010.
If this is the problem si there a way to not have it redirect for users who hav emailboxes on 2010?
LVL 16

Expert Comment

ID: 36715525
You are right.

It is recommend to create new OWA servername in DNS and on the Ex 2003 IIS that will be used to redirect requests to Ex2003 OWA and to change the IP for the current OWA url in DNS to point to the Ex2010. This way if you go to https://webmail.domain.com you will be connected to 2010 and if a mailbox still resides on 2003 it will be redirected to the 2003 OWA. There are lots of articles about it on the web. Just search for Exchange2003URL. For example this one:


Hope this helps.

Author Comment

ID: 36717847
Did you mean inyour first sentence Ex 2010 instead of 2003?
"It is recommend to create new OWA servername in DNS and on the Ex 2003 IIS"
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

LVL 16

Expert Comment

ID: 36719076
No, i meint 2003. This way you will Be able to use the old webmail URL during Migration and also afterwards. Users will connect to old URL but get to 2010. If Mailbox IS on 2010 they get their owa site. If not, they will Be redirected to the newly created URL which Points to 2003 and get their owa page from there. You just Need the newly created URL set as Exchange2003Url in 2010.

Author Comment

ID: 36771688
I think I've already done all that? I have the legacy domainname URL that redirects clients from 2010 OWA to 2003 OWA when they use the current https://webmail.domain.com -

On 2010 CAS OWA properties I have the external URL as https://webmail.domainname.com - which is the same URL 2003 users use to access OWA.

What specifically do I need to do? I feel that it's a simple thing but I just cant get it.

Thanks for understanding.
LVL 16

Expert Comment

ID: 36813488
Exchange2003URL is different from External URL. Have a look at this article:


Especially look at the section "Installing Exchange 2010" and there number 4 and 5. You need to specify the Exchange2003URL through Exchange Management Shell as explained there. You can verify the setting via this command:

Get-OwaVirtualDirectory "<CAS-Servername>\OWA*" | fl Exchange2003Url

If you want to access OWA from outside your company LAN, i. e. Internet, you need to configure your firewall to match the changes. If you need help for this, please let me know.

Author Comment

ID: 36815124
I was reading that exact article, thanks. Ok, I used that command on the 2010 server and the Exchange2003Url is the legacyhostname, its the URL that redirects to the 2003 Exchange server. So redirection seems to be working fine, I remember setting that up a while ago. When 2003 mailbox users log into OWA they are presented with the 2010 OWA login screen and when loggin gin you cnasee the URL as the legacy hostname, so thats working fine.

I noticed on my firewall that I still had the primary mail.domainname.com pointing to the Exchange 2003 server and when I pointed it to the 2010 Exchange server I was able to receive email from RPC\HTTTP, my mailbox is on 2010 - but then when I went to https://webmail.domain.com it didnt work.

So this is the status:

currently mail.domainname.com is pointing to Exchange 2003 Server in firewall
active sync is working for mailboxes on 2003 and 2010
OWA works internally and externally for 2003 mailbox users only
OWA doesnt work at all for 2010 users although they are presented with the 2010 logon screen
Exchange 2010 mailbox users cannot use RPC\HTTP, but when I switch mail.domain.com to the 2010 Exchange server in the firewall then they can (had to switch it back to 2003 Exchange server).

I know it's just a little tweaking and I'll have it, thanks for all your help!!!

Accepted Solution

tolinrome earned 0 total points
ID: 36943770
this solved the problem.
Set-OwaVirtualDirectory -identity "Owa (Default Web Site)" -LogonAndErrorLanguage 1033
Set-OwaVirtualDirectory -identity "Owa (Default Web Site)" -DefaultClientLanguage 1033

Author Closing Comment

ID: 36972704
I answered my own question.

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Here in this article, you will get a step by step guidance on how to restore an Exchange database to a recovery database. Get a brief on Recovery Database and how it can be used to restore Exchange database in this section!
This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Suggested Courses

650 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question