Exchange 2010 accessing via OWA

Posted on 2010-08-26
Last Modified: 2012-05-10
I have setup a new 2010 exchange server.
I currently have a 2003 exchange server.
I have migrated the mailboxes from 03 to 10.

when I try and connect to the new server via:
I am greeted with the login screen, and to select public or private computer.
I enter in the correct details and the the following error appears: Any ideas appreciated. thanks

"Your request couldn't be completed because no server with the correct security settings was found to handle the request. If the problem continues, contact your helpdesk."
Question by:Jamesm007

Expert Comment

ID: 33539106
Does this point to your 2010 Exchange OWA? -  https://mail/owa

What if you enter: https://x.x.x.x/owa (where x.x.x.x is the IP address of 2010 Exchange)

If you don't plan on keeping the Exchange 2003, then I would suggest to remove it, as this is may also be a conflict/confusion issue:


LVL 28

Expert Comment

ID: 33539118
get-owavirtualdirectory | fl
output the contents here.

Did you move your mailboxes from 2003 to 2010 ?

Check in your DNS > what does mail resolve to

ping from a workstation to MAIL
it might be pointing to the old exchange 2003

if that is the case, go to your dc

start > run > dnsmgmt.msc

change the a-record for mail to point to the new exchange 2010 lan ip

Accepted Solution

v_9mhdrf earned 500 total points
ID: 33539122
You have to go through the proper coexistence steps as Exchange 2010 CAS cannot access OWA for Exchange 2007 users. This will help get started;

Essentially you need to maintain a legal hostname for Exchange 2003/2007 users. For your Exchange 2010 OWA virtual directories you need to then set this legacy host name to ensure single-sign-on redirect for Exchange 2003/2007 users happens correctly.

For example of needed their Exchange 2003/2007 usres to log into the 2010 OWA page and then get to their mailboxes it may look like this.

Set-OwaVirtualDirectory -identity "Servername\owa (Default Web Site)" -Exchange2003URL

The '2003' in the attribute is correct no matter if that legacy URL is pointing to Exchange 2007 CAS servers or Exchange 2003 Front-End servers.
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.


Expert Comment

ID: 33539127
If you install another CAS temporarily and then forward your OWA/ActiveSync rules to this then it will be able to proxy for both the 2003 server and the 2010 server.

Just don't install the mailbox role.

Expert Comment

ID: 33539129
You need to redirect OWA from exchange 2010 to exchange 2003

Ie. if your user is on exchange 2003 then he will receive above errors.

OWA Configuration
During installation of the Exchange Server 2010 Client Access Server all settings have been configured for use on the Internet. The only thing that needs to be configured is the coexistence information for Outlook Web App. The Client Access Server needs to be configured in case a mailbox is still on Exchange Server 2003 and the client needs to be redirected to the Exchange Server 2003 front-end server.

On an Exchange Server 2010 server enter the following Management Shell Command:

Set-OWAVirtualDirectory <CASHUB01>\OWA ‘
-ExternalURL ‘

This will make sure that when a user connects to Exchange Server 2010 Client Access Server for Outlook Web Access and the mailbox is still on Exchange 2003 the client will be redirected to the old Exchange Server 2003 front-end server.

refer this it has good exploitation with pictures which show you additional steps on migrate to exchange 2010


Expert Comment

ID: 33539132
when a 2003 mailbox user connects to and the cas server detects the mailbox is on 2003 it looks at this attribute to send the request

step 5 from the above link
5.Configure the Exchange 2003 URL property on the /owa virtual directory. This is necessary for Exchange 2003 and Exchange 2010 to coexist. To configure this property, use the following command.

Set-OWAVirtualDirectory <CAS2010>\OWA* -Exchange2003URL 

You must enable forms-based authentication on the Exchange 2003 front-end server to allow your users to access their mailboxes through a single sign-on during the coexistence period.

Author Comment

ID: 33539213
Thanks for all the responses, I will go through in more details them when I get a minute.
I have located the issue related to the old mailboxes that had not yet migrated due to errors, so I have managed to get them across and I can log in now.
I do want to remove the 03 from the network now so this is my next step. I will assign points shortly.
thank you for the responses.

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
Office 365:  Cross-Premises Full Access Permissions 4 47
exchange2007 4 20
Intune/ Microsoft EMS 1 28
Email Header Detail 12 51
Lotus Notes – formerly IBM Notes – is an email client application, while IBM Domino (earlier Lotus Domino) is an email server. The client possesses a set of features that are even more advanced as compared to that of Outlook. Likewise, IBM Domino is…
This article explains how to install and use the NTBackup utility that comes with Windows Server.
In this video we show how to create an Accepted Domain 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 Mail Flow >> Ac…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

813 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

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now