• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 239
  • Last Modified:

exch 2007 and exch 2010 together owa issue

We have exch 2007 and exch 2010 running together so that we can migrate to 2010 but we are having an issue with OWA from the outside. We get the error Outlook We Access could not connect to exchange..
We have the legacy in place and tested ok but we keep getting this from OWA. Is this an issue with an IIs setting possibly or where should I check?
0
vmich
Asked:
vmich
  • 7
  • 6
1 Solution
 
EEhotlineCommented:
Hello,

How did you access OWA from outside? By 2010 or 2007 url? Have you disabled your ExternalURL on the exchange 2007 box?
0
 
vmichAuthor Commented:
No we have not disabled the ext on the 2007 should I do that?
0
 
EEhotlineCommented:
Yes, you will have to disable External Url on Exchange 2007.

Please refer to the below article's for more information on the upgrade path from Exchange 2007 to Exchange 2010.

http://technet.microsoft.com/en-us/library/dd351133.aspx

Please look at the part: Changing the External Client Access from this:

https://www.simple-talk.com/sysadmin/exchange/upgrade-from-exchange-2007-to-exchange-2010---part-1/
0
Microsoft Certification Exam 74-409

VeeamĀ® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
vmichAuthor Commented:
Ok made progress but I get this now with exch 2007 accts but 2010 are ok...

 A server configuration change is temporarily preventing access to your account. Please close all Web browser windows and try again in a few minutes. If the problem continues, contact your helpdesk
0
 
EEhotlineCommented:
Make sure that you have set ExternalURL in Exchange 2010

Set-OWAVirtualDirectory <CAS2010>\OWA* -ExternalURL https://mail.contoso.com/OWA

It should look like this:

2007  CAS

Internal URL https://server.contoso.com/owa

External URL https://legacy.contoso.com/owa

2010  CAS

Internal URL https://server.contoso.com/owa

External URL https:// mail.contoso.com/owa

Also, can you try to restart IIS?

Check this link, it will give you a lot of details for OWA coexistence:
http://blogs.technet.com/b/exchange/archive/2009/12/02/3408921.aspx
0
 
vmichAuthor Commented:
Yes that is how we have the urls on both setup now..
0
 
EEhotlineCommented:
Can you try to clear your browser cache and reset Virtual Directory under Client Access in EMC?
0
 
vmichAuthor Commented:
Found the issue...
The legacy was not pointing to one of the CAS servers. Once I made that change, all was good....
0
 
EEhotlineCommented:
Nice, glad you found it.
0
 
vmichAuthor Commented:
One more item if I could run past you...
We found now if we add the users to the 2010 exch, if they don't have the following security rights that cant get past the exch 2010 login screen: we have to go into advanced security permissions and set them for each user for Windows Authentication Read properties, then they are able to login...
Any idea what this maybe?
0
 
EEhotlineCommented:
Do you check this one for ea user in your org? I could only think that's the reason.
Inheritable permissions
0
 
vmichAuthor Commented:
Are you saying in AD for each user check this
0
 
vmichAuthor Commented:
check setting
0

Featured Post

Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now