Active Directory Integration – Appendix A: Prepare a Separate non-AD Server to Install the Connector

Process

If your security policy requires it, the Connector can be installed on a non-Active Directory (AD) server machine, but it must be joined to the same domain as the AD servers that the Connector will be monitoring. 

NOTE: Connector can now only be installed with .NET 4.0 or .NET 4.5 present. There is no need to install .NET 3.5.

1. Provision a virtual or physical machine using a static IP.
2. Install one of the three supported and tested Windows OS versions and other components:
   
   For Windows Server 2008 R2 SP1 or Windows Server 2012 R2 Or Windows Server 2016 (Preferred OSes):
   
   1. Install AD Domain Services Snap-ins and Command-line Tools feature via Remote Server Administration Tools > Role Administration Tools > AD DS & AD LDS Tools > AD DS Tools.
   2. Install .NET v3.5, 4.0 or .4.5.
      For more explicit OS-specific instructions, see https://support.microsoft.com/en-us/kb/2693643.
   For Windows Server 2008 SP2:
   
   1. Install Active Directory Lightweight Directory Services role.
   2. Install .NET v3.5, 4.0 or .4.5.
   For Windows 7 (non-home license):
   
   1. Install Remote Support Administration Tools. Download from http://go.microsoft.com/fwlink/?LinkID=137379.
   2. Enable AD DS and AD LDS tools:
      1. Complete all the steps that are required by the wizard, and then click Finish. 
      2. Click Start, click Control Panel and then click Programs.
      3. In the Programs and Features area, click Turn Windows features on or off. 
         If you are prompted by User Account Control to allow the Windows Features dialog box to open, click Continue.
   3. In the Windows Features dialog box, expand Remote Server Administration Tools, select AD DS and AD LDS Tools, and then click OK.
   4. Install .NET v3.5, 4.0 or .4.5.
   For Windows 10:
   
   1. Install Remote Support Administration Tools. Download from the Microsoft Download Center.
   2. Run the installer (either WindowsTH-KB2693643-x64.msu or WindowsTH-KB2693643-x86.msu, depending on your computer's architecture).
   3. After the installation is complete, all tools are enabled by default.
3. Join the machine to the same domain as the AD Server (domain controller) being connected to.
4. Open WMI ports via the following command run as Administrator: 
   netsh advfirewall firewall set rule group="Windows Management Instrumentation (WMI)" new enable=yes

 

Note:

You may need to permit remote usage of DCOM/WMI on the domain controllers. Changing DCOM permissions will require a reboot of the domain controller.

See Required permissions for OpenDNS Connector User for further detail.

 

 

 

 

 

 

Next section: Appendix B: Configuring AD Servers on Windows Server 2003 R2