On a more innovative note, SP1 also includes an updated lockbox, the component that manages encryption, validation, and similar operations. In the first version of RMS, the lockbox concentrated mainly on client applications such as Office. SP1 updates the lockbox to a server lockbox, which allows administrators to configure RMS to apply document protection at the server level, the client level, or even both.
SP1 also updates the RMS SDK so that third-party developers can integrate RMS features into their products. Adobe Acrobat already has a third-party RMS plug-in from Liquid Machines, for instance. These features are also intended to allow RMS to integrate with content inspection gateways, so these products will scan RMS-protected e-mail.
See, that's a bit of a problem for every large client on my list. Everyone in that space tends to scan incoming and outgoing e-mail for keywords such as porn, embezzle, Pearson, and the like. An RMS-protected e-mail is, however, immune to such a scan. That means all kinds of e-mail content -- and attachments -- can be run through your network and be completely invulnerable to content scans. That's how RMS will work unless these third-party solutions come out and play.
Given today's political and security considerations, that's not happening at most general enterprises, and definitely not at places such as financial institutions. RMS is a system with a solid features set, but without the more complete third-party support that Microsoft is promising for only later this year, you'll need to deploy it carefully.