Users Granted Permission to Manage the Certificate Authority Are Unable to Access It Remotely

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry


When users who have been granted the right to manage certificates on a Windows 2000 Certificate Authority (CA) attempt to remotely access the CA through the CA snap-in, they receive the following error message:

Access is Denied. 0x5 (5)


The CA snap-in requires users to have remote access to the following registry key on the CA:
If users do not have access to this registry key, they receive the error message described in the Symptoms section.


WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this issue, give the user permission to manage the CA. To grant this access to a non-administrative account, follow these steps:

  1. Open the CA snap-in.
  2. Right-click Certificate Authority Root and click Properties.
  3. Click the Security tab.
  4. Add the user who needs access and grant that user the required permissions.
The CA snap-in must be installed on the remote machine for the user to have remote access to the CA.

To give a non-administrative account permission to remotely manage a CA, follow these steps:

  1. Open the CA, click Run, and then type Regedt32.
  2. Navigate to the following registry key:
  3. Open the Machine key and at the bottom of the key add the following value:
  4. Click Save.
The remote user now has remote access to the CA.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

More Information

For additional information about restricting access to the registry from a remote computer, click the article number below to view the article in the Microsoft Knowledge Base:

153183 How to Restrict Access to NT Registry from a Remote Computer