In Exchange 2013, you can use the Information Rights Management (IRM) function to apply persistent protection to emails and attachments
Through the integration with RMS, exchange 2013 mail users can control the recipients' permissions on emails.
What IRM can achieve:
- Prevent IRM-protected content from authorized recipients to forward, modify, print faxes, save or cut and paste the content
- File format protected with the same protection level as mail
- Support the expiration of emails and attachments protected by IRM, etc.
Preface reminds: The environment is windows server 2012 r2. This installation should be cautious. When installing for the first time, there will be a certificate occupying the SSL of the server. After uninstalling directly, the installation of the same server will fail, and then The AD RMS module related to the site and service functions is deleted. The same is not true. It can only be uninstalled after downloading the RMS-related tools from the Microsoft official website. However, I searched the official website for a long time, but did not find it, so it is recommended to install carefully and do not uninstall easily.
Install AD RMS
I read the next book about Exchange 2013. I personally feel that it is not good. The jump is too fast. The commands for building Exchange in the previous chapters are also wrong.
It is recommended not to install this feature on the domain control server
Start experimenting: The deployment is best to install AD RMS on the Exchange server
As shown in the figure below, select the server in the red box, which is the back-end. Of course, you can also choose the front-end mailbox server. This is just an experiment. Then the next step
As shown in the figure below; select the red box, this is the AD RMS to be installed today, and then, the next step
The default here is just fine, the next step
Here is the next step
The default here is just fine, the same is the next step directly
Just install it here
AD RMS cluster installation
After installation, click in the red box below, and then proceed to the next step
Enter the interface below. As shown below, the next step
Here, choose the local server, choose the following figure, the next step
Then, as shown in the figure below, a red prompt appears. I wanted to use a domain account here, but it didn’t work. It can only be used conditionally. The first condition is that it must be in the Administrator group.
The second condition is that it must be in the domain user
Add the ADDC account to the Administrator in AD, and then the next step
Back to the Ex server, and then implement the following steps, here is to enter the above name
Then comes the next step
Then comes the next step, set the password
The choice of installation here is on Exchange, so the choice in the following figure is the second one, and then the next step
For the cluster address below, the name of the server is selected for SSL encryption: ex.hzz.com
As shown below
There is no screenshot here. It was recreated after deletion, but there is a problem that it was not deleted cleanly, so it resulted in such a result. You can download the rms related tools and uninstall it completely, but I haven’t found it yet, wait for the download to be found. Repeatedly continue to write about the problems I encountered, I will now install another one.
In this case, install the certificate again, click Properties, and the interface as shown in the figure below will pop up. Install the certificate. The steps are not explained, just default to the installation.
As shown in the figure below, the box below indicates that the installation was successful
Although talking about a server, but the following steps are the same, backup on the host, as shown in the figure below, and then go directly to the next step
This step, wait until the installation is complete
The following is installed
The following figure is only available when AD RMS is installed, but it does not mean that the cluster was created successfully
The installation is successful, as shown in the figure below, which is installed on the client server
