Thursday 4 June 2015

RMS Protection Tool

EMS Landing page

Have a look at the RMS Protection Tool which was announced as generally available this week. See the announcement here 

"The RMS Protection Tool contains PowerShell Cmdlets designed for developers and IT professionals who want to use scripting mechanisms to bulk protect and unprotect documents".

With this release, you can do the following:
  • Use admin-defined templates and ad-hoc policies to protect documents.
  • Protect documents of any type - Office file formats, PDFs, text, images, and generic file protection.
  • Use the Cmdlets on Azure RMS and on-premises AD RMS.
  • Service-to-service authentication for Azure RMS scenarios - for server workloads, it is important that the application is authenticated silently, which can be achieved using these Cmdlets.

Download the tool from:

https://www.microsoft.com/en-us/download/details.aspx?id=47256


The download includes x86 and x64 installers and a PDF file explaining the PoSH cmdlets.

Prerequisites
.Net 3.5
AD RMS Client 2.1

Now run the appropriate installer for the tool and the cmdlets are installed under the module "RMSProtection". Get-Help gets you further information on each cmdlet.

The available cmdlets are as follows:

Get-RMSFileStatus (returns RMS protection status of the specified file or files)

Get-RMSServer (returns the list of all AD RMS servers that can issue templates for the user)
  
Get-RMSTemplate (returns a list of AD RMS templates)

New-RMSProtectionLIcense (creates and returns a new ad-hoc license from scratch. The license object returned can be used by Protect-RMSFile to encrypt a file or files)

Protect-RMSFile (protects using RMS encryption the specified file or the files in a specified folder)

Unprotect-RMSFile (unprotects using RMS encryption the specified file or the files in a specified folder)

Get-RMSServerAuthentication (gets the status of the S2S credentials - shows the credentials previously set by Set-RMSServerAuthentication)

Set-RMSServerAuthentication (sets the status of the S2S credentials)


 

 

No comments:

Post a Comment