For OWA clients, we have just deployed a permission template that is already working properly and does not require any additional settings.
650) this.width=650; "title=" 712b8c52d00a40f1b7155c74a18c2ca0 "style=" border-top:0px;border-right:0px; background-image:none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; " Border= "0" alt= "712b8c52d00a40f1b7155c74a18c2ca0" src= "http://s3.51cto.com/wyfs02/M02/7F/33/ Wkiol1cw4fxj1y5oaaciplz8fza918.jpg "height=" 365 "/>
We send a test e-mail to see the effect.
650) this.width=650; "title=" 7016e795d96d4c669b12ec44b3a983db "style=" border-top:0px;border-right:0px; background-image:none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; " Border= "0" alt= "7016e795d96d4c669b12ec44b3a983db" src= "http://s3.51cto.com/wyfs02/M02/7F/35/ Wkiom1cw35bckhe9aacicufoh7m287.jpg "height=" 383 "/>
Then we came to the Outlook 2016 client, using Rmsuser1 to receive the encrypted message.
The RMS server is also contacted the first time it is received.
650) this.width=650; "title=" 1c9df13eadb34beab4e19b35a8fd649e "style=" border-top:0px;border-right:0px; background-image:none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; " Border= "0" alt= "1c9df13eadb34beab4e19b35a8fd649e" src= "http://s3.51cto.com/wyfs02/M00/7F/35/ Wkiom1cw35ecjx3paaekait9678790.jpg "height=" 442 "/>
Then you can view the mail.
650) this.width=650; "title=" De78cebb3bd345aa99778ae83fa9a7ec "style=" border-top:0px;border-right:0px; background-image:none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; " Border= "0" alt= "de78cebb3bd345aa99778ae83fa9a7ec" src= "http://s3.51cto.com/wyfs02/M00/7F/33/ Wkiol1cw4fjdrgvzaaeqyigq_o4295.jpg "height=" 343 "/>
From what you can see, you can view or reply to the message. In addition to the other permissions are no.
650) this.width=650; "title=" 93ffaa412730435a85f5f480ce65cc70 "style=" border-top:0px;border-right:0px; background-image:none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; " Border= "0" alt= "93ffaa412730435a85f5f480ce65cc70" src= "http://s3.51cto.com/wyfs02/M01/7F/35/ Wkiom1cw35ngozf1aac20fyhqx4286.jpg "height=" 484 "/>
Outlook 2016 has been able to use our previous custom templates after contacting the RMS server, with two more templates: Allow view and reply, and allow printing and viewing.
650) this.width=650; "title=" 6defae43acbf4fec928eb8631d70eec4 "style=" border-top:0px;border-right:0px; background-image:none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; " Border= "0" alt= "6defae43acbf4fec928eb8631d70eec4" src= "http://s3.51cto.com/wyfs02/M01/7F/33/ Wkiol1cw4fqc2owmaadzhgzu-_0983.jpg "height=" 370 "/>
Then we look at the RMS cache locally on the outlook2016 machine and see the RMS templates that are synchronized.
The following path is under the AppData hidden folder of the currently logged-on user.
650) this.width=650; "title=" 3d8cc01868c14f3e8dd168fe8150fa12 "style=" border-top:0px;border-right:0px; background-image:none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; " Border= "0" alt= "3d8cc01868c14f3e8dd168fe8150fa12" src= "http://s3.51cto.com/wyfs02/M02/7F/35/ Wkiom1cw35qwmm8vaab4iixrnds366.jpg "height=" 176 "/>
In fact, in the Task Scheduler of the Outlook client within the domain, we can also go to manually synchronize the RMS template information.
650) this.width=650; "title=" c8943930ccce42d0998106ab958a442e "style=" border-top:0px;border-right:0px; background-image:none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; " Border= "0" alt= "c8943930ccce42d0998106ab958a442e" src= "http://s3.51cto.com/wyfs02/M02/7F/35/ Wkiom1cw35zcqpsjaae3jto0r8o653.jpg "height=" 407 "/>
Then we can open the following folder to view the cached information after synchronization. The information that is synced here is placed in the DRM folder instead of the previous MSIPC folder.
650) this.width=650; "title=" 58db0da1014743d5839de8b344c86a4a "style=" border-top:0px;border-right:0px; background-image:none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; " Border= "0" alt= "58db0da1014743d5839de8b344c86a4a" src= "http://s3.51cto.com/wyfs02/M02/7F/33/ Wkiol1cw4fzingdfaacm38f7joe070.jpg "height=" 228 "/>
As you all know, the Outlook client is divided into different versions, so is the version of Outlook 2010/2013 supported by our RMS template as in Outlook 2016? This requires us to do more testing. Of course, you can also deploy Group Policy in AD and then combine the different versions of the Office Group Policy template to push our RMS rights template information. Because different versions of Office are slightly different when it comes to RMS.
I'll show you the next lesson. If you are deploying Group Policy, let users who use Outlook 2010 get the RMS template information.
This article from "Zeng Hung Xin Technical column" blog, declined to reprint!
Exchange 2016 integrated adrms series-9: Use custom RMS templates within a domain