I can create the RMS template in the RMS management utility on the RMS server, put the templates in a shared location and enable RMS by specifying a template location in a Group Policy.
The result is thatusers will see the message classifications in Outlook
… but when I try to create a transport rule based on the template, the templates are not available in ECP in the dropdown for message classification (the ones you see in the example below are there b/c I added them via Exchange powershell.
The other way to add message classifications is to create them in PowerShell on the mail server. When created this way the Message classifications show up when creating a new rule (as seen above) butthe end users don’t see them in Outlook.
One source says to make a registry change on the user’s computers:
Next, copy the XML file to a location on the client or networked location which is readable by Users. On the client, make the following registry changes:
[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\Policy]
"AdminClassificationPath"="c:\\Classifications.xml"
"EnableClassifications"=dword:00000001
"TrustClassifications"=dword:00000001
After trying both a network share and a local file, the Classifications still don’t show up in Outlook.
So the only way to get them to show up in Outlook doesn’t allow you to include them in a transport rule (and thus you’re not able to create a rule that allows forwarding inside the domain only) and the way to get them to show up when creating a transport rule doesn’t seem to work as far as getting them to show in Outlook.
Adding them via PowerShell on the Exchange server actually does get them to show up in OWA the way you would expect, they just won't show in Outlook 2010. I imagine the issue is with the reg entry that points Outlook to the xml
file….(and I do realize reference given is Offfice 2013) it’s entirely
possible that Office 2010 requires a new key in a slightly different place but
im only seeing references to office 2007 and 2013