The remote access role is already installed and DirectAccess console cannot load the configuration

The remote access role is already installed and DirectAccess console cannot load the configuration

Troubleshooting DirectAccess Remote Access role is already installed

I recently came across an issue with adding additional servers to the DirectAccess cluster I created. All servers were on the same subnet and no firewalls were placed in between the servers. After extensive digging and tinkering I realized that the Remote Registry was disabled. This is in fact required by DirectAccess and disabling this does seem good practice but you will face the following issues when doing so:

  1. The remote access console will fail to load correctly, error messages usually state the configuration was not loaded from a domain controller, in addition
  2. adding additional servers to the DirectAccess cluster will result in an error stating the “Remote access role is already installed”

Just to clarify when adding additional servers to a DirectAccess cluster you must:

 

  1. Configure the network cards on the new server (Dual homed is recommended)
  2. Install the IPHTTPS certificate
  3. Install the Remote Access role from Server Manager (but do not configure the role once installed)

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: