Deploy client to access Exchange 2013 server
Deployment prerequisites:
Domain, two main Exchange 2013 servers,
Environment: windows server 2012 r2
The domain has been deployed before, its domain name is hzz.com DMS is 200.200.208.201
Here are the steps to deploy the client of Exchange 2013:
- Environment: windows server 2012r2 DNS: 200.200.208.201
- Preparations before installation: 1. Join the domain, become an ordinary member, download the dependent windows components and Exchange 2013
Start the installation below:
The first thing to install is the necessary component: UcmaRuntimeSetup.exe, execute the following code before installation: Remember that you don’t need to execute the Install-windowsfeature RSAT-ADDS command, just execute the following one and it’s ok.
Install-WindowsFeature Server-Media-Foundation, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, 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, RSAT-ADDS
This code is best copied on the official website, I have seen many wrong codes on the Internet
After the installation is complete, you can install Exchange 2013
This is the same as the previous installation steps. Click setup.exe directly. However, there is only one difference, as shown in the figure below. Check the following. Its function is the client access role, and the first one is the mailbox role (this is Installed when the service database is installed)
The following is the installation. Normally, there are 10 steps to install. Both installations are the same. I tried to install the two together, but I don’t know if it will have any effect.
Deploy CAS array
After installation, combine the previous and the two deployed this time into a CAS array (client access server high availability), and then serve externally
Project environment:
1. Participating clients access the server
2. Cluster name
3. Network planning
Necessary components:
Install the "Network Load Balancing" component that is not installed on the client's access server. The Exchange administrator needs to manually install the component, both of which are required
Create a cluster record:
The next thing to deploy is the cluster: this is to create the DNS on the domain controller side, and open the DNS in the management center in the master domain controller.
In the DNS as shown below, click the domain name hzz.com, right-click, and click New Host as shown in the interface below
Enter the central node conversion you want to create for the client to access the server, and its IP address can be set to the intranet
Until the next step, click Finish.
Create a cluster:
The above preparations are all done, and the following is to create a cluster: the steps to deploy through the "Network Load Balancing" function:
Since the one I have here is built in Hyper-V, I need to check the function of MAC address spoofing, as shown in the figure below
The following starts to create network load balancing:
Open Network Load Balancing, right-click the pop-up interface, and click New Cluster, as shown in the figure below
Log in to cas1 or cas2 with the administrator's account, enter one of the clients to access the server, here is the operation in cas1
The default next step is just fine
Until the next step, click Add, and when you pop up to add an IP address, the entered IP address is the IP address of the cas created in the main domain controller. The IP set at that time is 200.200.208.190, and then click Next.
At this point, click Multicast, and then, the next step
Just click finish
The second step is to add another cas2 to the CAS. Because I accidentally deleted cas1 in the dc (domain), I cannot add cas2 normally.
The process of troubleshooting: 1. Ping cas1 in cas2 and then see if it can be pinged. As shown in the figure below, ping cas1 does not work.
If they are all in the same domain, they can be pinged, but this is different from ping. The reason is that the dns of cas1 in dc has been deleted. At that time, the ping IP address can still be pinged.
The solution is to restart the DNS of cas1 into the DC, and the command is executed in the computer of cas1, ipconfig/registerdns
This command is to lease the DNS again, so that the DNS in the DC deletes the DNS of CAS1
The following is added successfully
