You can install ipMonitor on a domain controller, but we do not recommend it.
Domain controllers are vital to the security of all devices on your network, and should be dedicated to this task. To maintain the highest level of network security, you should segment your critical resources. You expose your domain controller to increased security risk by merging it with other functions such as web servers, mail servers, or even ipMonitor.
Running ipMonitor on a domain controller also results in less security for ipMonitor. We normally recommend that all our customers create restricted Windows accounts specifically for running the ipMonitor Service that apply only the minimum tokens required for succesful operation of the ipMonitor service. But when you install ipMonitor on a domain controller, the Credential Manager cannot be enabled to impersonate Windows accounts with elevated permissions. There is no allowance for trust relationships outside of the domain, and this results in limited access to many ipMonitor features.
If you must install ipMonitor on a domain controller:
Warning! Windows registry changes can result in severe system damage if performed incorrectly. Before you modify the registry, make a backup copy and ensure you understand how to restore the registry if a problem occurs. For information regarding backing up, restoring, and editing the registry, refer to the Microsoft Knowledge Base article.
1. Start the registry editor (Regedt32.exe)
Access the following registry key:
For X86: HKLM\SOFTWARE\ipMonitor
For X64: HKLM\SOFTWARE\Wow6432Node\ipMonitor
2. Add a STRING value to this registry key:
3. Exit the Registry Editor.