Posted by: kurtsh | June 30, 2006

BETA: Rights Management Services (RMS) 1.0 Service Pack 2 (SP2) BETA

Windows Rights Management Services (RMS) 1.0 Service Pack 2 (SP2) for Microsoft Windows Server 2003, a security service for Windows Server 2003, is information protection that works with RMS-enabled applications to help safeguard digital information from unauthorized use – both online and offline, inside and outside of the firewall. For more information about RMS, please go to www.microsoft.com/rms.
 
Since this server component is provided as a premium service for Windows Server 2003, a Windows RMS Client Access License (CAL) is required for each user publishing and/or consuming Rights Management Services (RMS)-protected content. However, up to two users may simultaneously access or use RMS solely for administration of the software without a CAL. For more details on licensing requirements, please review the End User License Agreement when downloading this premium service.
 
Although RMS is designed for and tested with database servers running SQL Server 2000/2005 and MSDE, and Microsoft does not support the usage of RMS together with a database provider other than either SQL Server 2000/2005 or MSDE, RMS can be run on other database servers that use the ADO.NET interfaces that are provided by the Microsoft .NET Framework. Therefore, other database vendors may have developed compatible database providers for RMS. You may use any database provider together with RMS on the condition that the corresponding database server complies with the following criteria:
  • The database server must be Transact-SQL compliant because RMS initialization scripts and RMS stored procedures use Transact-SQL.
  • The database server must support any Microsoft SQL Server-specific extensions.
  • The database provider must be able to:
    Respond to method calls of the System.Data.SqlClient namespace of the .NET Framework.
    Provide the corresponding functionality of the System.Data.SqlClient namespace.
    Use Windows Integrated Authentication instead of SQL authentication.
If you use RMS in any other configuration, contact the relevant database vendor or solution provider whose database provider you are using in your customized deployment.
 

Categories

%d bloggers like this: