15.5 User groups
219
The following operations will be performed automatically within each conversion:
•
substitution of any appearance of the local account in the
WinRoute
configuration (in
traffic rules, URL rules, FTP rules, etc.) by a corresponding account from the
Active
Directory
domain,
•
removal of the account from the local user database.
Accounts not selected for the conversion are kept in the local database (the collision is still
reported). Colliding accounts can be used — the accounts are considered as two independent
accounts. However, under these circumstances,
Active Directory
accounts must be always
specified including the domain (even though it belongs to the primary domain); username
without the domain specified represents an account belonging to the local database. However,
as long as possible, it is recommended to remove all collisions by the conversion.
Note:
In case of user groups, collisions do not occur as local groups are always independent
from the
Active Directory
(even if the name of the local group is identical with the name of the
group in the particular domain).
15.5 User groups
User accounts can be sorted into groups. Creating user groups provides the following benefits:
•
Specific access rights can be assigned to a group of users. These rights complement
rights of individual users.
•
Each group can be used when traffic and access rules are defined. This simplifies the
definition process so that you will not need to define the same rule for each user.
User groups Definitions
User groups can be defined in
User and Groups
→
Groups
.
Figure 15.17
WinRoute user groups
Содержание Firewall6
Страница 1: ...Kerio WinRoute Firewall 6 Administrator s Guide Kerio Technologies...
Страница 129: ...8 5 HTTP cache 129...
Страница 404: ...404...
