Castlewood
asked on
Not able to access the OWA of newly-added CAS.
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
That said, there isn't really a good reason to separate server roles in server 2010.
ASKER
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?