Hello everyone,
Many of you have requested the ability to automate (and integrate) the process of protecting and unprotecting content. We’re happy to announce the GA release of the RMS Protection Tool . Shubha is a PM on the team and she will talk about this release in more detail.
Hello, this is Shubha.
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. This tool will eventually replace the Bulk Protection tool which would enable similar and other e-Discovery scenarios for AD RMS.
With this release, you can do the following:
Protecting a file using ad-hoc protection (if you provide a folder path to the –File parameter, all files in that folder will be protected):
C:PS>$lic = New-RMSProtectionLicense -UserEmail user1@abc.com -Permission EDIT
Protect-RMSFile -License $lic -File C:Test.txt
InputFile EncryptedFile
--------- -------------
C:Test.txt C:Test.ptxt
Description
-----------
Protects a single file (Test.txt) using the ad-hoc license just created and places
encrypted output file in the same location.
Unprotecting a file (if you provide a folder path to the –File parameter, all files in that folder will be unprotected):
C:PS>Unprotect-RMSFile -File C:Test.ptxt -OutputFolder C:Temp
InputFile DecryptedFile
--------- -------------
C:Test.ptxt C:TempTest.txt
Description
-----------
Unprotects a single file and places decrypted output file in the specified output folder location (C:Temp).
Extensive help on the Cmdlets is available via Get-Help. To get started, you can use the documentation PDF included with the download.
August update: The documentation has been updated and you'll find the latest version online - RMS Protection Cmdlets .
If you have downloaded the PowerShell Cmdlets from Microsoft Connect , please upgrade to this GA version. Our future plans for the RMS Protection Tool include support for emails and PST files. Watch this blog for updates.
As always, if you have any questions or comments, you can reach us at askipteam@microsoft.com
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.