Administrator's Guide - Kerio Software Archive

16.4 User accounts in Active Directory — domain mapping
Figure 16.10
Importing accounts from the Windows NT domain
Note: Import of user accounts from Windows NT is available only in Kerio Control on
Windows.
When connection with the corresponding domain server is established successfully, all
accounts in the selected domain are listed. When accounts are selected and the selection
is confirmed, the accounts are imported to the local user database.
16.4 User accounts in Active Directory — domain mapping
In Kerio Control, it is possible to directly use user accounts from one or more Active Directory
domain(s). This feature is called either transparent support for Active Directory or Active Directory
domain(s) mapping. The main benefit of this feature is that the entire administration
of all user accounts and groups is maintained in Active Directory only (using standard system
tools). In Kerio Control, a template can be defined for each domain that will be used to
set specific Kerio Control parameters for user accounts (access rights, data transfer quotas,
content rules — see chapter 16.1). If needed, these parameters can also be set individually for
any accounts.
Note: The Windows NT domain cannot be mapped as described. In case of the Windows NT
domain, it is recommended to import user accounts to the local user database (refer to 16.3)
Domain mapping requirements
The following conditions must be met to enable smooth functionality of user authentication
through Active Directory domains:
• For mapping of one domain:
1. The Kerio Control host must be a member of the corresponding Active Directory
domain.
2. 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. If another DNS
server is used, user authentication in the Active Directory may not work correctly.
• For mapping of multiple domains:
229