To support Active Directory (AD) integration with Virtual Appliances, the following requirements must be met.
Table of Contents
To support Umbrella Active Directory (AD) integration, you must configure a server that is a member of the AD domain with the following environment:
- Windows Server 2012, 2012 R2, 2016, 2019 or 2022 with the latest service packs and 100MB free hard disk drive space.
- Service packs prior to SP2 are not supported.
- .NET Framework 4.5 or above
- If a local anti-virus application is running, allow list the OpenDNSAuditClient.exe and OpenDNSAuditService.exe processes.
- AD Domain Services Snap-ins and Command-line Tools feature installed through Remote Server Administration Tools > Role Administration Tools > AD DS & AD LDS Tools > AD DS Tools. This is required for troubleshooting purposes.
If you are deploying AD integration with Virtual Appliances through integration with domain controllers, you will need to deploy one connector per AD domain (with an optional second connector per AD domain for redundancy).
If you have already deployed a centralized Windows Event Log Collector to which all domain controllers forward login events, and you wish to deploy AD integration with Virtual Appliances using this Windows Event Log Collector, you will need to deploy a single AD connector for all AD domains, with an optional second connector for redundancy.
Note: Umbrella does not support installing the Active Directory connector on non-GUI-based Windows servers like Windows Server Core.
Outbound Network Access to Cisco Umbrella
The Connector server requires outbound access as specified below:
- 443 (TCP) to api.opendns.com for syncing
- Access to additional URLs on port 80/443 (TCP) may be required for Windows to perform Certificate Revocation List and Code-Signing checks. For a complete list of ports, see the section on Communication Flow and Troubleshooting.
- 443 (TCP) to disthost.umbrella.com (for downloading upgrades)
If you are using a transparent HTTP web proxy, ensure that the URLs on port 80/443 are excluded from the proxy, and not subject to authentication.
The connector deployment requires you to create a new user account in each AD domain that needs to be integrated. This account should have:
- The logon name (sAMAccountName) set to OpenDNS_Connector. A custom username can be configured, but this custom username should be specified as a parameter when running the Configuration Script on the Domain Controller.
- Password never expires selected
Note: Passwords must not include backslashes, quotations (single or double), greater-than or less-than chevron brackets (< >), or colons.
- The Connector account (OpenDNS_Connector or custom username) must be a member of the following built-in groups on each AD domain:
- Enterprise Read-only Domain Controllers
- Event Log Readers
Note: In a parent/child domain scenario, the "Enterprise Read-only Domain Controller" only exists in the parent domain. In this case, follow the instructions listed here to provide the required permissions for the Connector account. You must add other missing groups.
Active Directory Integration with the Virtual Appliances < Prerequisites > Active Directory User Exceptions
Updated 5 months ago