Exchange Server 2010 Learning (13) Highly available post-deployment configuration work

We used NLB to achieve the high availability of the CAS+HT role, using DAG technology to realize the high availability of mailbox databases. But if you want Exchange to actually run, you need to make some necessary settings. In the third article of this system, the settings after the triple role deployment are described in detail. In fact, these settings are the same, but now the role is separate, and achieve the corresponding high availability, the configuration of a slight change, this article will explain this part of the content.

Server License

After the Exchange Server installation is complete, the default is a 120-day trial version, and when we open the EMC console, we will display server information for the Exchange server that is not licensed in the current organization, and the four servers we use in this case are listed, As shown in the following illustration:

Exchange 2010 servers that do not have a product key entered can only use Standard Edition features. A maximum of 5 databases can be mounted per mailbox server. The Enterprise Edition supports up to 100 databases. We need to change the product key after purchasing the license, which is very simple. Do the following on four servers (or select different servers in EMC on any of the servers): Open the Exchanger management console, switch to the Server configuration node, select the server name, and then click the Enter Product key on the right, as shown in the following illustration:

Certificate

The exchange Server2010 needs to use a multiple domain name certificate because there are multiple client access methods, such as when a user connects to an Exchange server using Outlook or OWA, The server is required to provide a certificate called mail.uec.com, and when the Autodiscover feature is used, the server needs to produce a autodiscover.uec.com certificate. After the Exchange Server installation completes, a self-signed certificate is generated, which is issued to itself by the Exchange server, so the client does not trust the certificate, which is extremely inconvenient to use. So, we need to create a new certificate.

The first step is to install the CA server. The user can purchase the certificate directly from the authoritative CA as required, where we are within the organization's own CA server. We install Certificate Services on the DC1, open the server role, and select AD Certificate Services. As shown in the following illustration: