ADRMS and SharePoint IRM Integration Error - 0x80020009

Description:

You have configure ADRMS properly in your environment. Now you want to make SharePoint to use ADRMS. At the SharePoint Central Admin, you specify the location of the RMS Server.

However when you try to open a document protected with RMS, there's a pop-up error saying couldn't find the document. At the SharePoint event viewer you saw the following error:

Information Rights Management (IRM): There was a problem while ensure IRM client. Status value: -1, error value: 0x80020009.

[Information Rights Management (IRM): There was a problem while creating the generic issuance license template.

All issuance licenses for protected documents are constructed from a generic, base issuance license template.

Additional Data

Error value: 0x800704DC

Resolution:

Please go to the SharePoint Central Admin and make sure you already select or type in the correct RMS cluster server address. Use HTTPS instead of HTTP when typing the RMS cluster address.

Sample SQL Script to Update ADRMS Configuration Database during Parallels Upgrade

UPDATE [dbo].[DRMS_ClusterPolicies]

SET PolicyData = '' --(your new string with updated information goes between the ' ' )
WHERE PolicyName='CertificationUserKeyStorageConnectionString'
 
UPDATE [dbo].[DRMS_ClusterPolicies]
SET PolicyData = '' --(your new string with updated information goes between the ' ' )
WHERE PolicyName='DirectoryServicesCacheDatabase'
 
UPDATE [dbo].[DRMS_ClusterPolicies]
SET PolicyData = '' --(your new string with updated information goes between the ' ' )
WHERE PolicyName='LoggingDatabaseServer'

Update AD RMS Config Database using SQL Server Management Studio during Parallels Upgrade

Description:

During AD RMS Parallels Upgrade, you need to modify the restored database to point to the new database servers.

Resolution:

1. Log on to the AD RMS configuration database server as local Administrator or another user account that is a member of the local Administrators group.
2. Click Start, point to All Programs, point to Microsoft SQL Server 2012, and then click SQL Server Management Studio.
3. On the Connect to Server page, ensure that the new database server name is listed in the Server name box, and then click Connect.
4. Expand Databases, expand DRMS_Config_<RMS cluster name>_<Port>, and then expand Tables.
5. Right-click DRMS_ClusterPolicies, and then click Open Table.
6. In the results pane, change the value in the PolicyData column of the LoggingDatabaseServer row to the new RMS database server name.
7. Change the value in the PolicyData column of the CertificationUserKeyStorageConnectionString row to reflect the new database server. The value should be data source=<new database server name>;integrated where <new database server name> is the name of the new database server.
8. Repeat steps 6–7 for the value in the PolicyData column of the DirectoryServicesCacheDatabase row.
9. Close Microsoft SQL Server Management Studio.

Active Directory Rights Management Services - Parallels Upgrade

Description:
You have an Active Directory Rights Management Services (ADRMS) being deployed in your IT Environment. You need to upgrade the version of ADRMS, the Windows OS, and also the Database with minimal downtime and minimal risk to new Windows 2019 and SQL 2019 machines.
You decided to do a Parallel Upgrade.

Resolution:

You would need to perform the following:

1. Prepare the new Windows 2019 OS and SQL 2019 Databases on different machines. Install all the necessary patches.
2. Back up the existing AD RMS database.
3. Restore the AD RMS databases to a new location (new instance, new SQL server, etc.).
4. The following SQL changes must be made on the restored databases.
• Database: DRMS_Config
• Table: DRMS_ClusterPolicies
• PolicyName entries in which the PolicyData value needs to reflect the new SQL connection string information.
• LoggingDatabaseServer
• CertificationUserKeyStorageConnectionString
• DirectoryServicesCacheDatabase
5. Built a new Windows Server of the desired version for the AD RMS cluster upgrade.
6. Add the AD RMS role.
7. When it gets to the role configuration choose the “join an existing cluster” option.
8. At the SQL database dialog enter the NEWLY RESTORED SQL database location, not the actual production database currently in use.
9. Complete the role configuration using all the same settings, service accounts, etc.
10. Edit the NTFS permissions on new AD RMS server's "C:\inetpub\wwwroot\_wmcs\certification\ServerCertification.asmx" file. Configure the same permissions as on the existing AD RMS server.

PowerShell Command to Identify Local Admin Account

Description:

You have several local account on your computer. One day, you need to find out which one is the real local Admin Account.

Resolution:

You can run the following PowerShell command on the local computer:

Get-CimInstance -ClassName Win32_UserAccount -Filter "LocalAccount = TRUE and SID like 'S-1-5-%-500'"