Tuesday, February 4, 2014

Exchange Server 2013 NLB Best Practice



Assume if you don't have Hardware Load balancer to configure array for the Client Access server we move to the next option of using windows network load balancer for high availability. While performing the patching over the CAS server we need to perform rebooting the server. This may leads to impact to the end user since the connection needs to be moved to the next CAS Server and may result to get reconnected again which will cause to prompt user name and password sometimes or it prompt "Outlook got disconnected"

In order to avoid the above behavior the best practice that can be followed for Network Load Balance

1. Open the Exchange management shell and run the following command providing the Exchange CAS Server Name

Get-Counter "\MSExchange RpcClientAccess\User Count" -ComputerName
Get-Counter "\MSExchange OWA\Current Unique Users" -ComputerName


2. Open the Windows Network LoadBalancer and perform drain-stop

3. Verify again on executing the same command

Get-Counter "\MSExchange RpcClientAccess\User Count" -ComputerName
Get-Counter "\MSExchange OWA\Current Unique Users" -ComputerName


4.  Stop the Microsoft Exchange RPC Client Access service (MSExchangeRPC)

5. Finally reboot the server

No comments:

Post a Comment