Cannot open your default e-mail folders, mixed 2010 - 2013 environment when creating second profile

Hi

I have a mixed 2010 - 2013 environment and things are almost working as expected. 

Right now I have 3 mailboxes in 2013, but if I try to create a new Outlook with one of those mailboxes I get the "cannot open your default e-mail folders".

If I log on to a pc with that user, Outlook finds the mailbox without any problems.

Why does it fail when I try to create a profile on another users login? It seems that it resolves to the old CAS array (RpcClientAccessServer). Even if I try to repair the Outlook profile it resolves the wrong (2010) CAS array.

Any ideas?

BR
Steen


August 21st, 2015 12:20pm

Are the Autodiscover, EWS and OAB URLs pointed to the Exchange 2013 server?
Free Windows Admin Tool Kit Click here and download it now
August 22nd, 2015 7:00pm

The problem is at a customer and they say they have done that. (maybe only the Autodiscover).

I was at another customer at the time I got the question. They are also during a migration. I could reproduce the error. At that customer autodiscover was not pointed to the 2013 servers, but I tried to do it in the host file, but that didn't change anything.

I am not sure about EWS and OAB urls. What if you wish to change namespace during the migration? I mean, if you use "something.domain.com" and in the 2010 environment you wish to use "mail.domain.com" in 2013, would you then change anything in the 2010 servers?

BR
Steen


August 23rd, 2015 3:00am

Hi

Thats the problem. When we create the new profiles (logged in as another user) it resolves the server to the "cas-array name". outlook.domain.com and not the 2013 format.

If I then do a "Repair" on the profile it resolves correct and works.

All this is only a problem when you are logged in as another users. They want to open a shared mailbox in its own profile and they have the password.

If I do a Outlook test of autoconfiguration of that account, it resolves corret to the GUID@domain.com The OA adress is also correct, in fact everything seems right. Outlook just wont start with the second profile, unless I do a repair.

I am able to reproduce this in a clean lab, so it is not only for that customer.

BR
Steen


Free Windows Admin Tool Kit Click here and download it now
August 24th, 2015 4:45am

Hi

1. It doesn't matter if it is a new or migrated account. 

2. How would you add another users account other way than the way I do? The PC is domain joined so I guess it doesnt use autodisover anyway? (SEE EDIT)

What I still don't get is, the scenario is like this.

- If user B logs in and starts Outlook, everything works as it should.

- If User A gets full access to users B, User A gets users B mailbox automapped as it should.

- If users A logs in, creates a new profile for User B mailbox, it resolves it wrong....UNTIL i do a repair on the profile - then it resoves it correct. :-)

Here is the autodiscover you asked for, for my lab.

EDIT:

Logged in as another user.

I just tried to create the profile for e.g. Alan Reid the other way:

And then it works. It resolves it correct the first time. Why is that? Why is there difference if I create the profile the other way. Strange :-)

That way is just not usable because the user needs the password for the second account. They don't have the password, only Full Access to the mailbox. 

BR
Steen


August 25th, 2015 8:35am

Hi,

Sorry for delay.

An Exchange 2013 database only has an RpcClientAccessServer field on it, for backwards compatibility with Exchange 2010 PowerShell objects. Exchange 2013 doesn't use the field at all.

Note that the Exchange server field does not state the name of any of the Exchange servers, and it's a deliberate design change in Exchange 2013 to provide a single consistent identity that Outlook could store. Therefore, we recommend use autodiscover service to configure Outlook client or use ExchangeGUID for your mailbox to manually configure Exchange 2013 user.

Free Windows Admin Tool Kit Click here and download it now
August 28th, 2015 2:48am

Hi

But why does Outlook resolve the name wrong when doing setting up the account without Autodiscover? It should get the correct data from AD.

Where does it get the RPCclientAccessarray fqdn from if it is not from the 2013 database?

We can not use the autodisover way since the users doesn't have the accounts password.

Is it a bug or am I doing the same thing wrong in my lab as two customers?

BR
Steen

August 30th, 2015 11:08am

Hi,

It's the FQDN of Mailbox database server instead of Outlook Anywhere.

Run Get-MailboxDatabase | FL Identity,*RPC*,Server, if it return below result:

Database     RPCClientAccessServer   Server
DB1             outlook.klaphat.com       Exch02

Then change LegacyExchangeDN to same as below:
/o=Klaphat/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EXCH02/cn=Microsoft Priva

Free Windows Admin Tool Kit Click here and download it now
September 2nd, 2015 8:42am

Thanks again.

I just tried that. Then it resolves to exch2.klaphat.com

That won't work. There is a HWLB in front with a name cas.klaphat.com

BTW, I just tried this in a clean installed lab only with a DC and a Exch 2013 server. No migration and no previous Exchange and I see the same. Outlook can't setup a profile manual. Only the autodisover setup method works.

I think I will have to tell the two customers that there are no other way anymore?

BR
Steen

September 2nd, 2015 8:54am

Hi,

Thank you for your understand and cooperation.

Free Windows Admin Tool Kit Click here and download it now
September 3rd, 2015 9:39pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics