Novell IdM – Implementing Remote Loader on Microsoft Windows
When implementing Novell’s (or NETIQs) Identity Manager product there are times when a certain connector(s) must be run on the MS Windows platform. If Meta-Directory Engine is running on a Linux (or other non-Windows) platform the requirement is the use of the Remote Loader.
When asked if it is better to run the Remote Loader on a Windows Domain Controller or simply on a Windows Member Server, the answer is to run it on a Member Server for several reasons:
Most organizations maintain a very controlled environment particularly when it comes to what is installed on Domain Controllers. Most organizations will not allow a service such as the Remote Loader (RL) to run on said Domain Controllers. As a result it is generally required, due to policy, to run the Remote Loader on a Member Server.
Additionally, through experience, we have found over the years that due to patching and security controls that take place specific to Domain Controllers it becomes more efficient, in terms of over-arching stability, to run the RL on a Member Server.
Lastly, the separation of duties between the Active Directory team and the Identity Management team generally makes life easier to manage the RL if it is running on a Member Server (i.e. less political).
Another advantage of running the RL on a Member Server is the ability to run the RL in a clustered environment. Member Servers may be configured in a Microsoft cluster with instrumental registry keys for password synchronization configured as a clustered resource. This will allow the Domain Controllers to communicate with the clustered resource for password synchronization to the Identity Vault and it will allow the Identity Vault to do the same. This is a configuration that is supported by both Novell and Microsoft and is considered to be the best way to provide password synchronization failover.