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

• Edited by steenpedersen Friday, August 21, 2015 12:24 PM

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

• Edited by steenpedersen 22 hours 26 minutes ago

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

• Edited by steenpedersen Monday, August 24, 2015 8:59 AM

I get crazy :-)

Here I am logged in as Alice Mullins in my lab. 

I create an additional Outlook profile for Alan Reid.

My 2010 CAS array is outlook.klaphat.com and OA in 2013 is cas.klaphat.com

I then enter the data manuel

As soon as I press Check Name, it resolves it to the RPCclientaccess

Why? 

Every thing works fine if I log in as Alan Reid or if I give Alice Mullins full access to Alan Reids mailbox. Then it gets automapped correct.

BR
Steen

Hi,

Thank you for cooperation, according to your description, I want to ensure below questions:
1. Whether this issue occur on mailbox who migrate to Exchange 2013, or same issue with new account in Exchange 2013?
2. How about use Autodiscover service to configure Outlook profile when add another account instead of manual configure?

Please run Get-ClientAccessServer | FL Identity,*URI* to check configuration for AutoDiscover. Meanwhile, here's an article about Step-by-Step Exchange 2007 to 2013 Migration, for your reference:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx

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

• Edited by steenpedersen 19 hours 34 minutes ago

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

• Edited by steenpedersen Tuesday, August 25, 2015 11:55 AM

Hi,

According to my test, I have Exchange 2010, Exchange 2013 in existence environment, the SCP for CAS server is the FQDN of each CAS server.

If I change all RPCClientAccessServer parameter for mailbox database in 2013 to cas.contoso.com, manually configure Outlook however it return cas.contoso.com in server name field. Also, run Get-MailboxDatabase| FL Identity,*RPC*,Server to check the value of RPCClientAccessServer, it's empty.

By the way, I do not reproduce your problem. Just as an advice, please run Get-MailboxDatabase| FL Identity,*RPC*,Server to check. If it's same with my situation, please open ADSI Edit and expand:
Configuration\CN=Configuration\CN=Services\CN=Microsoft Exchange\CN=First Organisation\CN=Administrative Groups\CN=Exchange Administrative Group (FYDIBOHF23SPDLT)\CN=Databases

Check the legacyExchangeDN value for database, the default value is point to FDQN for Mailbox server which host th

Hi and thanks

If I run the command in Exchange 2013 (in my lab) I get this

Thats the RPC clientaccessserver (CAS array fqdn).

If I check LegacyExchangeDN, it is the same for both Exchange 2010 and 2013 databases

/o=Klaphat/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=outlook.klaphat.com/cn=Microsoft Private MDB

Should I change anything?

BR
Steen

Hi,

It should be same with below, you can modify it in ADSI Edit:
/o=Klaphat/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Mailbox FQDN/cn=Microsoft Private MDB

By the way, if you want to manual configure Exchange 2013 account for internal Outlook client, please type "Mailbox FQDN" in Server Name field, it will query AD to get the ExchangeGUID for this mailbox.

Hi again

I changed it to the outlook anywhere fqdn, but it didn't change a thing

Still resolves to the wrong address. Exchange 2010 cas array address. Since my 2013 namespace is autodiscover.klaphat.com and cas.klaphat.com

I guess something is missing when changing namespace in a migration fase? 

In my lab I do it, the two customers does it - and we can all reproduce this error / bug.

BR
Steen