Exchange server2013 Series 7: high availability deployment of Client Access Servers

Last Update:2014-07-03 Source: Internet

Author: User

Tags rsat

Developer on Alibaba Coud: Build your first app with APIs, SDKs, and tutorials on the Alibaba Cloud. Read more ＞

Exchange server2013 Series 7: high availability deployment of Client Access Servers

Du Fei

In the previous article, we introduced the High Availability Technology of client access servers. From this article, we will look at a detailed high availability deployment solution.

First, let's take a look at our server list:

No.	Service name	IPAddress	Function
1	Hyv01	IP: 10.41.3.6 \ 16 Gateway: 10.41.1.254	Host
2	Hyv02	IP: 10.41.4.6 \ 16 Gateway: 10.41.1.254	Host
3	DF-DC01	IP: 10.41.4.210 \ 16 Gateway: 10.41.1.254 DNS: 10.41.4.210 10.41.4.211	DC Dufei.com
2	DF-DC02	IP: 10.41.4.211 \ 16 Gateway: 10.41.1.254 DNS: 10.41.4.210 10.41.4.211	DC Dufei.com
3	DF-CAS01	IP: 10.41.4.212 \ 16 Gateway: 10.41.1.254 DNS: 10.41.4.210 10.41.4.211 IP: 172.16.1.1 \ 24 heart	CAS
4	DF-CAS02	IP: 10.41.4.213 \ 16 Gateway: 10.41.1.254 DNS: 10.41.4.210 10.41.4.211 IP: 172.16.1.2 \ 24 heart	CAS
5	DF-MBX01	IP: 10.41.4.214 \ 16 Gateway: 10.41.1.254 DNS: 10.41.4.210 10.41.4.211 IP: 172.16.1.3 \ 24 heart	Mbx
6	DF-MBX02	IP: 10.41.4.215 \ 16 Gateway: 10.41.1.254 DNS: 10.41.4.210 10.41.4.211 IP: 172.16.1.4 \ 24 heart	Mbx
7	Mail	IP: 10.41.4.216	NLB
8	Dag01	IP: 10.41.4.217	Dag

PS: I deployed this environment on the company's blade. Due to restrictions, I only used one network card when I was working on NLB and Dag, that is, only the business segment 10.41.4.0 \ 16, no heartbeat network, the operation is feasible.

For more information about the hardware environment, software environment, and domain environment planning of the Exchange Server, see http://dufei.blog.51cto.com/382644/1410764.

Step 1: Create an ad DS domain

Here, we deploy two DC servers to achieve fault tolerance. If you are in an experimental environment, you can consider using one. We installed the ad DS component on the DF-DC01 first.

After the component is successfully installed, upgrade the server to a domain controller, as shown in:

Next, specify the domain name used:

Specify the location of the ad ds database, log file, and sysvol:

Other options are generally left by default. After the primary domain controller is installed, it restarts your computer, and then installs the extra Domain Controller on 10.41.4.211. Select "add domain controller to existing domain", as shown in:

Specify the password in directory service recovery mode. Other options are default. As shown in:

After the installation is successful, there are many ways to check the normality and health of the domain. Here I directly use the dcdiag command for health check. The results are roughly as follows:

Step 2: Add two CAS servers to the dufei.com domain, As shown in:

650) This. width = 650; "Title =" image "style =" border-right-width: 0px; Background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; padding-Right: 0px; border-top-width: 0px; "Border =" 0 "alt =" image "src =" http://img1.51cto.com/attachment/201407/2/382644_14043140536Wwl.png "width =" 305 "Height =" 393 "/> 650) This. width = 650; "Title =" image "style =" border-right-width: 0px; Background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; padding-Right: 0px; border-top-width: 0px; "Border =" 0 "alt =" image "src =" http://img1.51cto.com/attachment/201407/2/382644_1404314053CeK6.png "width =" 311 "Height =" 392 "/>

Next, we also need to perform some preparation operations, install the remote tool management package, prepare prerequisites, prepare the ad architecture and domain, and install ucma4.0. Here we take DF-CAS01 as an example to explain the installation process of exchange.

Step 3: Install the remote tool management package

For security and management convenience, we create an exchange management account exadmin in DC.

Next, we log on to cas01 using this account to install and deploy the entire exchange.

Step 4: prerequisites for installing the exchange role.

Install the mailbox server role, client access role, and both environments by using the following command to install the necessary items.

Install-windowsfeature as-http-activation, desktop-experience, net-framework-45-features, RPC-over-http-proxy, RSAT-clustering, RSAT-clustering-Guest interface, RSAT-clustering-MGMT, RSAT-clustering-powershell, web-mgmt-console, was-process-model, Web-Asp-Net45, web-Basic-auth, web-client-auth, web-digest-auth, web-Dir-browsing, web-Dyn-compression, web-http-errors, web-http-logging, web-http-redirect, web-http-tracing, web-ISAPI-Ext, web-ISAPI-filter, web-lgcy-mgmt-console, web-metabase, web-mgmt-console, web-mgmt-service, Web-Net-Ext45, web-request-Monitor, web-server, web-stat-compression, web-static-content, web-Windows-auth, web-WMI, windows-identity-Foundation

We have installed the client to access the server role. Therefore, execute this command, as shown in:

Restart the computer as prompted.

Step 5: Ad architecture preparation and domain preparation(This step can also be performed independently and automatically when exchange is deployed)

Exchange needs to expand the schema partitions, configuration partitions, and domain partitions of the domain, as shown in the following code:

Ad architecture partition preparation:

Put the exchange 2013 SP1 installation media on the Exchange Server and run the setup/PS/iacceptexchangeserverlicenseterms Command, as shown in

Configure partitions and prepare domain partitions:

Run the following command:

Setup/preparead/organizationname: organization name/iacceptexchangeserverlicenseterms, as shown in figure

Setup/preparead/organizationname: dufei/iacceptexchangeserverlicenseterms

Step 6: Install the Unified Communication API (ucma)

Unified Communication hosting API (ucma) 4.0 is a managed code platform, developers can use it to build applications for accessing and controlling Microsoft enhanced presence information, instant messaging, telephone and video calls, and audio/video conferencing. This program needs to be downloaded separately. Its: http://www.microsoft.com/zh-cn/download/details.aspx? Id = 34992, and then double-click to install it.

Step 7: Install the exchange Client Access Server role

After preparations, you can install the Client Access Server role.

Next, ask if you want to update and select as needed:

Next, wait until the page shown in the figure is reproduced:

Grant the license terms and proceed.

Here, we only install the Client Access Server role, as shown in:

Specify the installation path. Here I will default:

Next, check the existing environment, as shown in:

Click Install to start the installation. Have a cup of water and have a chat.

After the installation of the first CAS server is complete, continue to install the second CAS server. The installation method is the same as the above steps, but no need to prepare the ad architecture and domain. So I will not go into details here. After both CAS servers are successfully installed, configure NLB.

First, install the NLB component on the access server of the two clients, as shown in:

Then, open the network load balancing Manager using the management tool and select "create cluster", as shown in:

Connect to cas01 and specify the IP address and priority of the machine, as shown in:

Next, specify the cluster IP address and use 10.41.4.216 here, as shown in:

Specify the full Internet name. Here I use mail.dufei.com

The first node in the cluster is successfully created, as shown in:

Add Node 2 as follows:

650) This. width = 650; "Title =" image "style =" border-right-width: 0px; Background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; padding-Right: 0px; border-top-width: 0px; "Border =" 0 "alt =" image "src =" http://img1.51cto.com/attachment/201407/2/382644_1404314060jLUb.png "width =" 496 "Height =" 244 "/> 650) This. width = 650; "Title =" image "style =" border-right-width: 0px; Background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; padding-Right: 0px; border-top-width: 0px; "Border =" 0 "alt =" image "src =" http://img1.51cto.com/attachment/201407/2/382644_1404314060ivZj.png "width =" 395 "Height =" 245 "/>

Other options are basically the default, and the entire process is relatively simple. The final result is shown in:

Note: During NLB unicast in hyper-V environment, you must enable ARP spoofing for the NIC. All NLB nodes must be enabled, as shown in:

Anyone who has deployed exchange 2010 Server Load balancer knows that in 2010, there is a client access array concept. That is to say, after the Active Directory site configures the client access array, all client access servers in the site will automatically become members of the array. In the current version of exchange 2013, you do not need to configure the client access array, because load balancing and highly available service deployment is much easier.

As described at the beginning of this article, I only use one network card in the environment. Therefore, when I open the NLB manager, the following prompt may be reported:

Therefore, we recommend that you use two NICs in Unicast mode. When NLB is successfully created, you need to perform relevant tests. The common method is to find a client to ping the cluster IP address, and then re-enable the two nodes to check whether network communication is normal. For more information about the Exchange Server deployment, see: http://technet.microsoft.com/zh-CN/library/bb691354 (V = exchg.150 ). aspx # ws2012mbx. Of course, our deployment is not over yet. The next document will introduce the deployment of the email server role Dag.

This article is from the "du Fei" blog, please be sure to keep this source http://dufei.blog.51cto.com/382644/1433743

This article is an English version of an article which is originally in the Chinese language on aliyun.com and is provided for information purposes only. This website makes no representation or warranty of any kind, either expressed or implied, as to the accuracy, completeness ownership or reliability of the article or any translations thereof. If you have any concerns or complaints relating to the article, please send an email, providing a detailed description of the concern or complaint, to info-contact@alibabacloud.com. A staff member will contact you within 5 working days. Once verified, infringing content will be removed immediately.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

Get Started for Free

Sales Support

1 on 1 presale consultation

Chat Contact Sales
After-Sales Support

24/7 Technical Support 6 Free Tickets per Quarter Faster Response

Open a Ticket
Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.

Learn More