Exchange 2010 - setting up CAS array after mailbox creation

I'm working towards setting up some redundancy for exchange 2010.  Unfortunately I did not create a CAS array during my initial setup and now need to go back and fix this.  I have clear directions for setting up the CAS ( but could use a little help figuring out how to get my clients connected to it after its been setup.  I'm mostly worried about my Citrix users.  Is there a script I can run or some other way to automate updating everyone's profile or would I need to slug it out manually for each mailbox?
First LastAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

Bruno PACIConnect With a Mentor IT ConsultantCommented:
Ok I reviewed the articles and as all these people have similar issues I suppose I was in a specific situation when I did it myself.

It looks like Outlook 2007/2010 doesn't dectect this change as a mailbox move and then do not refresh by itself.

If you don't minde to create a new database and move your mailboxes from one database to another you can avoid reconfiguring all your outlook profile.
Take a look at :

The steps will be:
Create a CAS array object in Exchange
Create the DNS record for this CAS Array name.
Create a new mailbox database (as a CAS array now exist this database should automatically be associated with the CAS array). Check the RpcClientAccessServer on the new database.
Move the mailboxes from the old database to the new one. If users have Outlook 2010 the move can be done with no need to quit and restart Outlook.

The article I gave you talks about a sort of workaround to force outlook to realize the change on the RpcClientAccessAttribute by temporarily removing the CAS hostname from DNS but I don't recommend to touch anything about DNS name of production CAS servers.

The "move" solution is the most sure solution.

Just a warning: a mailbox move will generate a volume of transaction logs on the new database as bug as the mailbox data size so be aware of the log files volume when you move mailbox to not fill you disk and make the store service to fail. Also, differential backups will increase.
Bruno PACIIT ConsultantCommented:

There's nothing to do on MAPI clients (Outlook).

After your create your CAS Array object and a DNS record fir it you use Set-MailboxDatabase to change the RpcClientAccessServer on every existing database with the FQDN of the CAS Array.

Next time MAPI client will connect they will be reconfigured to use the FDQN that now appears in the RpcClientAccessServer attribute of their database.
All will look like a mailbox move in fact...

The only required thing is to close Outlook and relaunch it.

Have a good day.
First LastAuthor Commented:
Hi PaciB

That almost sounds too good to be true!  I've posted here several times with various exchange setup questions and one item that seemed to come back to haunt me is not setting up the CAS right away.  A number of people have commented that I will have a lot of work ahead of me since I didn't set it up at the beginning.  Here is one post for reference:

Would you mind reviewing that one and let me know if what you see there matches your experience?  What I'm being told is that each Outlook profile would need to be repaired if I add a CAS after setting up the mailboxes.
First LastAuthor Commented:
Awesome, this makes perfect sense now.  Thank you for taking the additional time to check the other articles, very much appreciated.
Am I correct that the mailbox move will only point them to the Databases's CAS Array hostname only if the mailbox was not pointing to an existing CAS Array hostname?
If it was pointing to CAS-Array-1, then you do a mailbox move to a database that is CAS-Array-2, the profile will still be pointing to CAS-Array-1?
But if the mailbox was not pointing to CAS-Array-1, and instead just, then it will point to the CAS-Array-2 after it's moved?
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.