Create RPC CAS Array
I have 2 Exchange 2010 Servers running side-by-side. Both servers are running the same roles (MB, HT, CAS). I need to move all mailboxes from Server A to Server B and then decommission Server B. I'm clear on all steps that need to be done except for creating a RPC CAS Array. Everywhere I read it says I need to do this before creating a database, but of course, I already have one on Server A as it was created some time ago.
I'm hoping someone can point me to directions for creating a CAS array in this environment solely for the purpose of not having to reconfigure/touch clients when I move their mailboxes.
Thanks.
I'm hoping someone can point me to directions for creating a CAS array in this environment solely for the purpose of not having to reconfigure/touch clients when I move their mailboxes.
Thanks.
A CAS array object should be configured even if you only have one CAS server or one multi-role server.
Reflect for a moment about what was discussed in the prior item. A client will not update itself to use a CAS array object if you add one at a later time. Well what if you only have one CAS? You may think it doesn’t matter. I guess one could argue it doesn’t matter at that very moment, but why not future proof things if you can and save some cycles and frustration later? What if a year from now you find yourself in need of replacing that CAS? If you’re clients profiles are all pointing to a CAS name then you have no clean way to transition them without some kind of outage or manual work. You will have to repair their profiles with one of the means already mentioned after adding a new CAS, or you will have to decommission the existing CAS and introduce a new CAS with the same hostname which will require some downtime. To me none of those options are acceptable.
What if later on your business requirements change and then dictate you should have client access high availability? You can only achieve this goal by adding a second CAS and a load balancing solution. You will find yourself stuck in the same boat again having to repair everyone’s profile through one of the means already discussed. Again these are not acceptable options to me.
What I would suggest is you create a CAS array object from the very beginning. How do you do that if you have no load balancer and only a single CAS? Simple! Configure the CAS array object like you normally would. Give it a name, an AD site, a FQDN, and then simply point the DNS ‘A’ record to the IP as the only existing CAS or multi-role server you have at that time. You have just future-proofed yourself and if you ever have to replace the single CAS or multi-role server all you have to do is build the new server, and then change the DNS record IP address and everything keeps working without interruption. If you ever want to add high availability at a later time then all you have to do is get your load balancing solution operational and then change the CAS array object DNS record IP address to point at the VIP of the load balancing solution. Easy!
Hopefully this article has been helpful in addressing some of the CAS array object misconceptions and will go a long ways towards helping everyone move towards a healthy Exchange Server 2010 migration.
Referenced Link: http://blogs.technet.com/b
Reflect for a moment about what was discussed in the prior item. A client will not update itself to use a CAS array object if you add one at a later time. Well what if you only have one CAS? You may think it doesn’t matter. I guess one could argue it doesn’t matter at that very moment, but why not future proof things if you can and save some cycles and frustration later? What if a year from now you find yourself in need of replacing that CAS? If you’re clients profiles are all pointing to a CAS name then you have no clean way to transition them without some kind of outage or manual work. You will have to repair their profiles with one of the means already mentioned after adding a new CAS, or you will have to decommission the existing CAS and introduce a new CAS with the same hostname which will require some downtime. To me none of those options are acceptable.
What if later on your business requirements change and then dictate you should have client access high availability? You can only achieve this goal by adding a second CAS and a load balancing solution. You will find yourself stuck in the same boat again having to repair everyone’s profile through one of the means already discussed. Again these are not acceptable options to me.
What I would suggest is you create a CAS array object from the very beginning. How do you do that if you have no load balancer and only a single CAS? Simple! Configure the CAS array object like you normally would. Give it a name, an AD site, a FQDN, and then simply point the DNS ‘A’ record to the IP as the only existing CAS or multi-role server you have at that time. You have just future-proofed yourself and if you ever have to replace the single CAS or multi-role server all you have to do is build the new server, and then change the DNS record IP address and everything keeps working without interruption. If you ever want to add high availability at a later time then all you have to do is get your load balancing solution operational and then change the CAS array object DNS record IP address to point at the VIP of the load balancing solution. Easy!
Hopefully this article has been helpful in addressing some of the CAS array object misconceptions and will go a long ways towards helping everyone move towards a healthy Exchange Server 2010 migration.
Referenced Link: http://blogs.technet.com/b
ASKER
I'm not at the very beginning as this article (which I've previously read) suggests.
I already have 2 servers built.
I'm looking for someone who has done this to assist, not just link to articles I can Google myself.
I already have 2 servers built.
I'm looking for someone who has done this to assist, not just link to articles I can Google myself.
Hi,
Let`s Ex. exchange server 1 -ip 192.168.1.1
exchange server 2 -ip 192.168.1.2
Now If you had configured CAS array then IP - 192.168.1.3
in above case if one CAS array exiting then no need to create new CAS array while move all mailboxes from Server A to Server B
all mailbox automatically point to that cas array.
But - if you do not have CAS array, - then you can simply move all mailbox to other server.
ex- server 1 RPC - abc.xyz.local - 192.168.1.1
server 1 RPC - abc1.xyz.local 192.168.1.2
Then Go to DNS create new record for abc.xyz.local - 192.168.1.2
so all user connect exiting abc.xyz.local - -- - new ip 192.168.1.2 (new server which we have already move mailbox) in this case it works
Let`s Ex. exchange server 1 -ip 192.168.1.1
exchange server 2 -ip 192.168.1.2
Now If you had configured CAS array then IP - 192.168.1.3
in above case if one CAS array exiting then no need to create new CAS array while move all mailboxes from Server A to Server B
all mailbox automatically point to that cas array.
But - if you do not have CAS array, - then you can simply move all mailbox to other server.
ex- server 1 RPC - abc.xyz.local - 192.168.1.1
server 1 RPC - abc1.xyz.local 192.168.1.2
Then Go to DNS create new record for abc.xyz.local - 192.168.1.2
so all user connect exiting abc.xyz.local - -- - new ip 192.168.1.2 (new server which we have already move mailbox) in this case it works
ASKER
Jimmithakkar, I would like to start using a CAS Array on the new server. How can I implement it into this scenario?
ASKER
I should specify I, want to implement a CAS Array Object not a CAS Array.
Hi,
The following list is a collection of truths many customers are not aware of when it comes to the CAS array object which I'll try to demystify.
A CAS array object does not load balance your traffic
A CAS array object does not service Autodiscover, OWA, ECP, EWS, IMAP, POP, or SMTP
A CAS array object's fqdn does not need to be part of your SSL certificate
A CAS array object should not be resolvable via DNS by external clients
A CAS array object should not be configured or changed after creating Exchange 2010 mailbox databases and moving mailboxes into the databases
A CAS array object should be configured even if you only have one CAS or a single multi-role server.
CAS Array Object - -
New-ClientAccessArray -Name CASArray -Site "Default-First-Site-Name" -Fqdn mail.abcd.local
The following list is a collection of truths many customers are not aware of when it comes to the CAS array object which I'll try to demystify.
A CAS array object does not load balance your traffic
A CAS array object does not service Autodiscover, OWA, ECP, EWS, IMAP, POP, or SMTP
A CAS array object's fqdn does not need to be part of your SSL certificate
A CAS array object should not be resolvable via DNS by external clients
A CAS array object should not be configured or changed after creating Exchange 2010 mailbox databases and moving mailboxes into the databases
A CAS array object should be configured even if you only have one CAS or a single multi-role server.
CAS Array Object - -
New-ClientAccessArray -Name CASArray -Site "Default-First-Site-Name" -Fqdn mail.abcd.local
ASKER
You're just regurgitating the same article that the first user posted. Ughhh...
Dear,
You can start using a CAS Array (CAS Array Object) on the new server. by using below cmd
New-ClientAccessArray -Name CASArray -Site "Default-First-Site-Name" -Fqdn mail.abcd.local
You can start using a CAS Array (CAS Array Object) on the new server. by using below cmd
New-ClientAccessArray -Name CASArray -Site "Default-First-Site-Name" -Fqdn mail.abcd.local
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Simon. While I have you, would you skip all this and go to 2013 if you had the option?
I have new hardware so I can either move to another 2010 system or go to 2013.
I have new hardware so I can either move to another 2010 system or go to 2013.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Okay. I've created the CAS Array Object. I also created a DNS entry. I created a new mailbox database and moved a mailbox to it. When I launch Outlook for the first time it fails to resolve via autoconfigure. What else do I need to do?
ASKER
It is also adding =SMTP: to the mailbox name.
ASKER
If I make the DNS entry of the CAS Array Object point to the new server it resolves fine. But, if I assign it a new IP, it breaks. I have no load balancers in play. What am I missing?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK. So then if I move mailboxes between cas array servers and then decom one server I just flip the DNS A record instead of touching the clients? Is this correct?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Simon.
Extremely helpful, as always.
Extremely helpful, as always.
ASKER