What doesn't RMS do out of the box?

As I said in my previous post, RMS is not a golden egg to solve the world's security problems. Out of the box, RMS does not:

- Provide a holistic policy enforcement based on business groups (finance, HR, legal). What this means is that you will need to configure each group of RMS consumers and manage them seperately outside of RMS. There is also no way to identify who can use RMS and who can protect using RMS.
- There is no way to enfore an RMS Template to be applied to a document, whether it be word or an email. More on RMS template will be discussed in another posting.
- Protection of Derivative content - RMS protection does not move between applications.
So if a user moves RMS content into a non RMS protect document that content (assuming they have the RMS rights) is no longer RMS protected.
- Non-Microsoft Applications - with RMS SP2, xps and infopath products are now RMS Enabled applications in addition to those existing RMS enabled applications (word, excel, powerpoint and outlook). If you want to enable RMS protected for non microsoft applications, you would need to look into customzing the application using the RMS SDK or look into using a third party tool (Liquid Machines Document Control 6.x)
- Role based document expiration - there is no way to expire documents on a per user and role basis.