Link to home
Start Free TrialLog in
Avatar of Bolton09
Bolton09

asked on

Problem Configuring Outlook

Hi,

We have the following setup:

1 Exchange 2007 server running with the CAS/Hub Transport Roles
2 Exchange 2010 servers running the Mailbox roles in a CCR cluster
1 Exchange 2010 server running CAS/Hub Transport and Mailbox Roles (this is purely used to link us to Office 365)

We're recently installed Exchange 2013 SP1 onto a new server.  CAS/Mailbox roles installed.

Goal is to keep the Hybrid Office 365 environment but move everything on-premise onto the Exchange 2013 server and remove the 2007 and 2010 servers.

Now I've tried to migrate a couple of mailboxes onto the new exchange server, which works fine. I can login to the Web App and send and receive mail on these accounts.

However the problem is configuring Outlook.  I usually try setting up the Outlook profile manually and entering the server name and the username manually.  This all works OK but when trying to open Outlook I get this error:

"Cannot start Microsoft Outlook.  Cannot open the Outlook window.  The set of folders cannot be opened.  The attempt to log on to the Microsoft Exchange has failed."

User generated image
ASKER CERTIFIED SOLUTION
Avatar of Amit
Amit
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Sorry but is not outlook anywhere.

Your actual outlook profile is created in a way to get you authenticated using your 2010 CAS, yes you will get authenticated but that server can't get to open the folders in the new server.  You may need to create a new profile so it will point to your 2013 CAS.
Avatar of Member_2_7599116
Member_2_7599116

it sounds Exchange Server doesn't replicate with primary DC

when you try to create a new user from the exchange server it self, make sure that it dos replicate with primary DC

if doesn't, please let me know I will guide you how to get it resolved

Cheers,
Abs
Just had this one happened and it was malware infection on the PC causing it, interesting indeed.