We recommend that you do not install ipMonitor on a domain controller.
The domain controllers in a Microsoft Windows® 2000/XP/2003 network are vital to the security of all the devices on that network. To maintain the highest level of network security, segmenting critical resources appropriately is key. Domain controllers should be dedicated to the task, and not be merged with other functions such as web servers, mail servers, or any other products that would increase the security risk to an inadequate level.
To take full advantage of ipMonitor's security features, we suggest that you create an account specifically for the ipMonitor Service to run under that applies the minimum tokens required by the ipMonitor Service to operate successfully. However, when ipMonitor is installed 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, resulting in limited access to many ipMonitor features.
If you must install ipMonitor on a domain controller regardless of the issues mentioned above, proceed with the following steps:
IMPORTANT! These instructions require making changes to the registry, which 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 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.
Note: If the registry key does not exist, it may be necessary to create it.
For information on other features and concepts related to those discussed in this article, refer to the following ipMonitor resources:
< Back
![]()
Last Updated: November 27, 2006 | What did you think of this topic?