Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Not able to access the OWA of newly-added CAS.

Posted on 2016-10-25
3
Medium Priority
?
68 Views
Last Modified: 2016-10-28
Prior to yesterday we have one public-facing EX2007 with CAS-only in additional to one EX2007 with HT, internal CAS and MB roles.
Yesterday I just set up one public-facing EX2010 CAS-only server intended to replace the EX2007 CAS-only server. The strange thing is, I found not able to access OWA at EX2010 CAS. Here is the settings:
On EX2010 CAS:
both internal and external OWA URL: EX2010cas.mydomain.com
Outlook Anywhere external host name: owa.mydomain.com

on EX2007CAS:
both internal and external OWA URL: EX2007cas.mydomain.com
Outlook Anywhere external host name: owa.mydomain.com

Two CNAME in our DNS:
autodiscover.mydomain.com points to EX2010cas.mydomain.com
owa.mydomain.com      points to EX2007cas.mydomain.com

Here is the details of the issue:
1. I found Not able to access OWA at EX2010CAS: using EX2010cas.mydomain.com will display the login screen of OWA 2010 but right after log in, it will be redirected to owa.mydomain.com where the version 2007 OWA in the 2007 server is used. That is not what we want. Remember we intend to have EX2010CAS to replace the EX2007CAS? So how to change to use OWA in EX2010CAS instead of EX2007CAS ?

2. Well, I thought I can simply change the CNAME for owa.mydomain.com to point to EX2010cas.mydomain.com and should be able to access OWA at EX2010CAS. Unfortunately no, using EX2010cas.mydomain.com throws an error right after login screen. (At the same time, using EX2007cas.mydomain.com successfully access OWA in 2007 server.) The error is:

A server configuration change is temporarily preventing access to your account. Please close all Web browser windows and try again in a few minutes...

The error sounds like an issue in the local computer. Obviously no since I did clear browser cache and still to no avail.
ActiveSync seems to be working well without a problem.
Can you help? What did I miss here?
0
Comment
Question by:Castlewood
[X]
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
  • 2
3 Comments
 
LVL 43

Accepted Solution

by:
Adam Brown earned 2000 total points
ID: 41859077
When you log in to Exchange 2010's OWA, it will only present you with the 2010 OWA interface if the mailbox of the account you log in with is located on an Exchange 2010 server. If the mailbox for the user is on a 2007 server, OWA will redirect you to the login page for the Exchange 2007 CAS server. This is expected behavior. You'll need to either create a mailbox on the 2010 server and test access with that or you will need to move your mailbox to the 2010 server to use the 2010 OWA interface.
0
 

Author Comment

by:Castlewood
ID: 41859179
Thanks Adam.
So in another words, my original intention to set up the new CAS-only 2010 to replace the CAS-only 2007 is unfeasible, correct? I need to have mailboxes sit in 2010 in order to have 2010 OWA to respond to the users of those 2010 mailboxes. Before that happens, I still need to fully rely on the 2007 CAS-only server for OWA users. (At this moment, the 2010 CAS server is useless in terms of OWA access.)
 
Am I correct?
0
 
LVL 43

Expert Comment

by:Adam Brown
ID: 41864389
That's correct. 2010 CAS only works for mailboxes on 2010 mailbox databases. They can't fully interoperate with other versions.

That said, there isn't really a good reason to separate server roles in server 2010.
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

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

The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
As much as Microsoft wants to kill off PST file support, just as they tried to do with public folders, there are still times when it is useful or downright necessary to export Exchange mailboxes to PST files. Thankfully, it is still possible to e…
how to add IIS SMTP to handle application/Scanner relays into office 365.
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

636 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