Outlook 2007 problems accessing Exchange 2010 mailboxes

Hello,

My company is moving from Exchange 2003 to Exchange 2010.  We have one back-end Exchange 2003 server, and two Exchange 2010 servers.  I have setup a DAG using the 2010 servers.  I have also setup a CAS array, and am using hardware load balancers.

If I either create a new Exchange 2010 mailbox, or move an existing mailbox from Exchange 2003, when using a Windows 7 client logged on as the associated user, I can successfully configure and open the mailbox in Outlook 2007.  However, when I am logged onto our Windows 2003 Terminal Server as the same user, I get the message "Outlook cannot log on.  Verify you are connected to the network and using the proper server and mailbox name.  The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action."  If I can get past this point, I get a message saying "Microsoft Exchange is unavailable".

In addition, even though I should have full access to all mailboxes, when I add an Exchange 2010 mailbox as a secondary mailbox to my Outlook profile, I get "Cannot display the folder".  If I create a new Outlook profile to make the Exchange 2010 mailbox a primary mailbox, I am repeatedly asked to enter credentials, and cannot open the mailbox.

Any help would be much appreciated.
vphulAsked:
Who is Participating?
 
vphulAuthor Commented:
In the end I paid for support from Microsoft.

The terminal server issue relates to
 
http://blogs.technet.com/b/kpapadak/archive/2011/03/13/setting-up-kerberos-with-a-client-access-server-array.aspx
 
and the secondary mailbox issue is covered in part by
 
http://support.microsoft.com/kb/907434
 
"We recommend that you do not use accounts that are members of protected groups for e-mail purposes. If you require the rights that are afforded to a protected group, we recommend that you have two Active Directory user accounts. These Active Directory accounts include one user account that is added to a protected group and one user account that is used for e-mail purposes and at all other times."
 
I hope this helps others.
0
 
neothwinCommented:
are you using wildcard certificate? e.g. *.abc.com
0
 
neothwinCommented:
if you are using wildcard cert or your certificate subject name is different from exchange outlook anywhere external host name, you need to run reconfigure your outlook provider:

Set-OutlookProvider EXPR -CertPrincipalName msstd:*.abc.com
or
Set-OutlookProvider EXPR -CertPrincipalName msstd:yourExternalName.company.com

Wildcard certs and SAN certs are OK on win Vista and later OS but not on Win XP/2003.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
vphulAuthor Commented:
Hello Neothwin,

We are not using Outlook Anywhere.

The internal and external address for our CAS array is mail.company.com .

I have run
Set-OutlookProvider EXPR -CertPrincipalName msstd:mail.company.com
and it has made no difference.  Before running it, I could get an Exchange 2010 mailbox to open in Outlook 2007 on our Windows 2003 Terminal Server by disabling RPC Encryption on both our CAS servers, but now I can't.

0
 
neothwinCommented:
it needs to match with the cert name install on CAS servers.
0
 
vphulAuthor Commented:
It does.  We have a Unified Communications certificate with the common name of mail.company.com .
0
 
vphulAuthor Commented:
Upgrading to Exchange 2010 is a real learning curve!!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.