Shulou(Shulou.com)06/02 Report--

In Exchange Server2010, client computers access the exchange server through the Client Access Server role (CAS). Once the Client Access server fails, client computers will not be able to access Exchange systems. In practice, it is recommended to deploy at least two client access servers and form a CAS array to ensure the availability of client access servers. It is recommended that Hub Transport Role (HT) be installed on each Client Access Server, and HT role between two servers automatically completes network Load Balancer migration High Availability.

Preparing for a High Availability Environment

Client access servers accept client access requests. It is recommended to deploy more than two client access servers in a large user environment to relieve the pressure caused by a large number of accesses. Client Access servers use IIS services as a running platform.

1. Deploying CAS arrays

Deployment Reference Blog: blog.chinaunix.net/uid-16829731-id-3629300.html

2. Hardware environment requirements

As a node server of CAS array, the hardware recommendations are as follows:

Node servers use the same hardware configuration;

At least two network cards are deployed on each node server. (for internal and heartbeat networks)

3. Software environment requirements

a. Use the exact same server operating system Windows Server 2008R2 and upgrade to the latest patches;

b. Install the "Network Load Balancer" component provided by windows server 2008R2;

c. Log in with the same exchange administrator user and add that user to the local administrators group.

d. Install the same version of Exchange Server2010, one cannot install Exchange Server 2010SP1, and the other cannot install Exchange Server2010SP2;

e. Use the same version of IIS Server components.

4. Exchange Administrator User

CAS arrays use a dedicated exchange administrator account named "contos\exadmin," which is added to the Schema Admins, Enterprise Admins, and Domain admins groups already added to the server local administrators group.

5. network parameter setting

a. Set static IP address for each node server. Network Load Balancer cluster does not support dynamic address assigned by DHCP server;

Each node server has at least two network adapters (NIC), one for the internal network that provides application services and the other for the heartbeat network that connects node servers. Note: Heartbeat networks are not required.

If the heartbeat network is deployed in the network, only the IP address and subnet mask can be set when setting the IP address of the heartbeat network. DNS parameters and default gateways do not need to be set. In the Advanced TCP/IP Settings dialog box, select the Disable NETBIOS over TCP/IP option;

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.