Mapping Active Directory Domains

Mapping Active Directory

Mapping is one-way only, data are synchronized from directory service to Kerio Control. In order to map to the AD Domains, certain conditions are applicable.

Mapping features

1. Adding a new user in Kerio Control creates a local account.
2. Use ASCII (American Standard Code for Information Interchange) for usernames when creating user accounts in a directory service.
3. If you disable users in Microsoft Active Directory, they are also disabled in Kerio Control.
4. If you disable users in Apple Open Directory, they stay enabled in Kerio Control.
5. Thus, only the Kerio Control hosts can successfully map an AD domain.

Conditions required for mapping the AD domains

1. Hosts in the local network (user workstations) should use the Kerio Control's DNS module as the primary DNS server, because it can process queries for Active Directory and forward them to the corresponding domain server.
2. If another DNS server is used, user authentication in the Active Directory may not work correctly.
3. The Kerio Control host MUST be a member of the mapped domain, else, authentication in the Active Directory might work incorrectly.
4. In case of mapping multiple domains, the Kerio Control host must be a member of one of the mapped domains (primary domain).
5. The primary domain must trust all other domains mapped in Kerio Control.