Just wanted some claification. I have 2 Exchange servers, both hosting the CAS, HT, and MB roles. Both servers are members of a DAG for database failover. All outlook clients are currently connected to Server1, and the RpcClientAccessServer attribute are pointing to Server1 for all the databases. My boss believes that because the 2 server are members of a DAG, if Server1 goes down, clients can connect to the CAS on Server2 and connectivity will be uninteruppted. Is this correct? From what I understand, this is not true...and it's what the CAS Array is for. However, since we have a DAG, we can't use the CAS Array. Now, my question is if Server1 goes down, if I change the RpcClientAccessServer on the databases to Server2, will that do anything? What if I were to create load balancing using DNS Round Robins, would that work?

In that case you can't use NLB on the servers, it would be an option to use NLB from TMG or even better use HW LB if that's available? Yes, that's what casarrays are for, so this is a manual process that needs to be done, which means if Server1 "goes offline" the clients will be disconnected Databases can be mounted since you should have quorom online (FSW) and the RpcClientAccessServer value needs to be changed to point to Server2 instead. Have you checked these HW LB? Take a look http://www.kemptechnologies.com/en/loadbalancingresource/ms-exchange-2010.html http://www.kemptechnologies.com/en/server-load-balancing-appliances.htmlJonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

Just to add up some useful links to Jonas Andersson's. Having deployed two KEMP LoadMaster virtual appliances myself, I total agree with Jonas. Btw, they now support Hyper-V. Load Balancing Exchange 2010 Client Access Servers using an Hardware Load Balancer Solution (Part 1 through 3) http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/load-balancing-exchange-2010-client-access-servers-using-hardware-load-balancer-solution-part1.html Part 4 discusses the LoadMaster configuration Uncovering the new RPC Client Access Service in Exchange 2010 (Part 1 through 4) http://www.msexchange.org/articles_tutorials/exchange-server-2007/planning-architecture/uncovering-new-rpc-client-access-service-exchange-2010-part1.html Here you find KEMP's own guidelines for Exchange 2010 with firmware 5.1 http://www.kemptechnologies.com/emea/loadmaster-documentation.html An excellent source if you read German: http://www.loadbalancerblog.de/ MCTS: Messaging | MCSE: S+M | Small Business Specialist

That was some nice info for me aswell about Hyper-V :) Thanks Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

There are some god reviews of KEMP's LoadBalancing offerings here: http://www.ntpro.nl/blog/archives/2032-Load-balancing-vCloud-Director-multi-cell-with-the-Kemp-Loadmaster.html http://vinfrastructure.it/en/2012/04/kemp-virtual-loadmaster-introduction/ http://vinfrastructure.it/en/2012/04/kemp-virtual-loadmaster-installation/ http://vinfrastructure.it/en/2012/04/kemp-virtual-loadmaster-configuration/ http://vinfrastructure.it/en/2012/04/kemp-virtual-loadmaster-load-balancing/ http://www.mikes.eu/index.php/home/item/kemp-s-server-load-balancing