Comments on: Exchange 2010 Databases and the RPCClientAccessServer Database Parameter

By: Elan Shudnow

Elan Shudnow — Wed, 23 Nov 2011 20:07:37 +0000

I always create a CAS Array even if it's 1 CAS. Therefore, even if you end up adding more CAS Servers down the road, no worries and you won't have to worry about the update issue. Outlook 2003 clients should also have an issue as it's an issue with the RPC Client Access Service, not the clients.

By: David

David — Wed, 23 Nov 2011 20:03:53 +0000

Thanks Elan. I am going to try the method of creating a new DB and moving the mailboxes. Do you know if this will work for Outlook 2003 clients? Also do you know if it's possible to create a one server CAS array? We don't have the resources for 2 servers right now….but at least if I can configure this using a 1 server "array", I shouldn't encounter this same problem again in the future.

Thanks.

By: Elan Shudnow

Elan Shudnow — Wed, 23 Nov 2011 15:10:33 +0000

It is not fixed and it is unknown when it will be fixed.

By: David

David — Wed, 23 Nov 2011 14:42:01 +0000

Does anyone have an update on this? Does SP1 correct this issue?

By: Frank

Frank — Thu, 30 Jun 2011 14:57:10 +0000

I'm in the same boat. Did Elan's suggestion work?

By: Elan Shudnow

Elan Shudnow — Fri, 10 Jun 2011 04:21:42 +0000

Easiest way I can think about is create new databases that are stamped with CAS Array and move them to the new databases. Their profiles "should" get updated after the mailbox move. Give it a shot with a mailbox or two.

By: Byron

Byron — Tue, 07 Jun 2011 05:47:12 +0000

I'm also looking to migrate from a single CAS / HT server to a CAS array. This is concerning if all users need to manually run a repair. Are there any options to automate this?

By: JScott

JScott — Fri, 11 Mar 2011 21:46:05 +0000

Hello,

Has there been any update to this? Are there any possible solutions to updated clients automatically to use the RPCCAS array fqdn automatically?

Thank you.

By: Elan Shudnow

Elan Shudnow — Tue, 14 Dec 2010 21:51:32 +0000

I haven't seen a fix. These types of issues have existed since Outlook 2007 and Exchange 2007 with Outlook not being able to update Outlook Anywhere FQDN if it can still contact its old Outlook Anywhere endpoint. Not sure when Microsoft will ever fix these issues, if ever.

By: Frederic Demeyere

Frederic Demeyere — Fri, 10 Dec 2010 11:53:53 +0000

Hi all,

I have the same issue with Outlook 2007 and Outlook 2010 not updating the RPC Endpoint after changing RPCClientAccessServer on mailbox database to cas array fqdn. I have 2 HUB-CAS-MBX boxes in a DAG.
When I do a profile repair the profile gets updated with the cas array fqdn but the profile is in offline mode. I have to disable that too. Someone told me this has to do with CAS and MBX role residing on one box.

Is there still no fix for this bug? These issues are preventing me for changing the RPCClientAccessServer parameter on my mailbox databases