How to configure AD Connector (ADC) with Event log collector

In this article, we will explore how the Active Directory Connector (ADC) functions and how to configure it with Event Log Collectors and Domains.

Configuration Options 

There are two setup options available for using the Active Directory:

1. Registering Domain Controllers: This involves the use of Virtual Appliances (VA) and the AD Connector, with the AD Connector communicating directly with all registered Domain Controllers (DCs). 
2. Event Log Collector: This setup includes the Domain, VA, and the AD Connector. In this scenario, Windows Event Log Forwarding sends information from the DCs to a central Event Log Collector server. The AD Connector then communicates only with this central server, not the DCs

Please note: Registering Domain Controllers and adding domains are different processes.

1. To start the configuration in the Umbrella dashboard, navigate to Deployments > Configuration > Sites and Active Directory and click Add. Select Windows Event Log Collector and click Next.

2. Customers can check the log file properties (in Windows Event Viewer) to find out the name of the log. Please note that the log file name should be entered without the .evtx extension or full path details.

Important Considerations:

For the Connector to function correctly, it's necessary to continue with normal deployment steps:

1. Register a 'Domain' on the 'Sites and Active Directory' page for the purpose of user provisioning. This is necessary because there's no registered DC to sync users/groups from.

2. Deploy 'Virtual Appliances'.

There are some known limitations to this deployment mode:

• The Connector might appear in an error state, even when working properly.

For the AD connector to work efficiently, certain permissions are required. You can review these permissions here: Required Permissions for the OpenDNS_Connector User.