Chat now with support
Chat mit Support

Identity Manager 9.1 - Administration Guide for Connecting to Active Directory

Managing Active Directory environments Synchronizing an Active Directory environment
Setting up initial synchronization with an Active Directory domain Adjusting the synchronization configuration for Active Directory environments Running synchronization Tasks following synchronization Troubleshooting Ignoring data error in synchronization Pausing handling of target system specific processes (Offline mode)
Managing Active Directory user accounts and employees
Account definitions for Active Directory user accounts and Active Directory contacts Assigning employees automatically to Active Directory user accounts Supported user account types Updating employees when Active Directory user account are modified Automatic creation of departments and locations based on user account information Specifying deferred deletion for Active Directory user accounts and Active Directory contacts
Managing memberships in Active Directory groups Login information for Active Directory user accounts Mapping of Active Directory objects in One Identity Manager
Active Directory domains Active Directory container structures Active Directory user accounts Active Directory contacts Active Directory groups Active Directory computers Active Directory security IDs Active Directory printers Active Directory sites Reports about Active Directory objects
Handling of Active Directory objects in the Web Portal Basic data for managing an Active Directory environment Configuration parameters for managing an Active Directory environment Default project template for Active Directory Processing methods of Active Directory system objects Active Directory connector settings

Creating home directories using batch files

To satisfy specific demands of individual network environments, you can use a batch file, which is run when you create a home directory with One Identity Manager Service. Whether the home directory is ultimately enabled depends on the result of running the batch file.

To use this function, a Netlogon share must exist on all home servers. Subdirectories are added in the Netlogon share, which correspond to the NetBIOS names of the domain. If there is a batch file in this directory with the name HomePre.CMD, it is run before the home directory is added. If the batch file ends in failure (that means Errorlevel <> 0), the home directory is not added.

Pass the following command line parameters to the batch file HomePre.CMD to be used during the run (in the given order; database column names are used):

SAMAccountName (from table ADSAccount)

Ident_Domain (from table ADSAccount)

Ident_Server (from table QBMServer)

SharedAs (from table ADSAccount)

HomeDirPath (from table ADSAccount)

HomeShare (from table ADSAccount)

You can run another batch file again after adding a home directory. This must be kept in the same place as before and have the name HomePost,CMD. You pass the parameters in the same way as HomePre.CMD. Merely, the exit code (Errorlevel) is not handled.

Example:

A user account Test1 is created in the domain Dom2. Its home directory should be created on the server Serv3 in the shared drive Share7 with the name TestHome6 and be released as TestShare5. On the running home server ServHome the files HomePre.CMD and HomePost.CMD are found in the \\ServHome\Netlogon\Dom2 directory.

Batch call before creating the home directory:

\\ServHome\Netlogon\Dom2\HomePre.CMD Test1 Dom2 Serv3 TestShare5 TestHome6 Share7

If the batch run returns an exit code 0, the home directory is created. Otherwise, the process is stopped with a log message.

Batch call after creating the home directory:

\\ServHome\Netlogon\Dom2\HomePost.CMD Test1 Dom2 Serv3 TestShare5 TestHome6 Share7

Supporting multiple profile directories

The different Windows operating system versions use different repositories for roaming user profiles. For more information about storing roaming user profiles, see the MicrosoftTechNet Library.

To map the roaming user profile in One Identity Manager.

  • Provide a template structure for the user profile on the profile server.

    Example of a template structure for user profiles on a profile server

    PROFILE

    UserProfile

    All required folders/files

    UserProfile.V2

    All required folders/files

    UserProfile.V3

    All required folders/files

    UserProfile.V4

    All required folders/files

  • In the Designer, set the TargetSystem | ADS | Accounts | ProfileFixedString configuration parameter and define the part of the user profile directory that you want to attach to the default profile path. The default value is UserProfile.

As a result, the directory paths for the user profiles are mapped as follows in the default installation.

  • If the profile directory is created in the home directory:

    \\Servername\HOMES\Username$\PROFILES\UserProfile

  • If the profile directory is not created in the home directory:

    \\Servername\PROFILES\Username\UserProfile

The following directories exist after handling the processes.

  • If the profile directory is created in the home directory:

    \\Servername\HOMES\Username$\PROFILES\UserProfile

    \\Servername\HOMES\Username$\PROFILES\UserProfile.v2

    \\Servername\HOMES\Username$\PROFILES\UserProfile.v3

    \\Servername\HOMES\Username$\PROFILES\UserProfile.v4

  • If the profile directory is not created in the home directory:

    \\Servername\PROFILES\Username\UserProfile

    \\Servername\PROFILES\Username\UserProfile.v2

    \\Servername\PROFILES\Username\UserProfile.v3

    \\Servername\PROFILES\Username\UserProfile.v4

The directory paths for the repository on the terminal server are mapped in the same way. In this case, in the Designer, change the TargetSystem | ADS | Accounts | TProfileFixedString configuration parameter accordingly. Specify in this configuration parameter the part of the user profile directory path which is appended to the default profile path on a terminal server. The default value is UserProfile.

Home and profile directory access permissions

Table 65: Configuration parameters for setting up user directories
Configuration parameter Meaning

QER | Person | User | AccessRights

Configuration of permissions for accessing user directories.

NOTE: To assign permissions to directories and files, it is sometimes necessary to define user account names such as Administrators, Everyone, or Domain Users in specific languages. The default language for the user accounts names is English.

To grant access permissions for the home directory

  • In the Designer, set the QER | Person | User | AccessRights | HomeDir and its configuration subparameters, and enter the access permissions in the configuration parameters.

    Granting access permissions to the home directory is done by the One Identity Manager Service.

    Table 66: Configuration parameters for home directory access permissions
    Configuration parameter Effect when set

    QER | Person | User | AccessRights | HomeDir

    Configuration of access permissions for the user’s home directory. To set the permissions, the configuration parameter and subparameters need to be set.

    QER | Person | User | AccessRights | HomeDir | EveryOne

    Everyone has permissions to access a user’s home directory.

    Default: -r-w-x

    QER | Person | User | AccessRights | HomeDir | User

    Defines the user’s home directory permissions.

    Default: +r+w-x

To grant access permission for the profile directory

  • In the Designer, set the QER | Person | User | AccessRights | ProfileDir configuration parameter and its configuration subparameters, and enter the access permissions in the configuration parameters.

    Granting access permissions to the profile directory is done by the One Identity Manager Service.

    Table 67: Configuration parameters for profile directory access permissions
    Configuration parameter Effect when set

    QER | Person | User | AccessRights | ProfileDir

    Configuration of access permissions for the user’s profile directory. To set the permissions, the configuration parameter and subparameters need to be set.

    QER | Person | User | AccessRights | ProfileDir | EveryOne

    Everyone has permission to access a user’s profile directory.

    Default: -r-w-x

    QER | Person | User | AccessRights | ProfileDir | User

    Defines the user’s profile directory permissions.

    Default: +r+w-x

To grant access permissions for the home directory on a terminal server

  • In the Designer, set the QER | Person | User | AccessRights | TerminalHomeDir and its configuration subparameters, and enter the access permissions in the configuration parameters.

    Granting access permissions to the home directory is done by the One Identity Manager Service.

    Table 68: Configuration parameters for access permissions to the home directory on a terminal server
    Configuration parameter Effect when set

    QER | Person | User | AccessRights | TerminalHomeDir

    Configuration of access permissions for an Active Directory user account’s terminal server home directory. To set the permissions, the configuration parameter and subparameters need to be set.

    QER | Person | User | AccessRights | TerminalHomeDir | EveryOne

    Everyone has permission to access a user’s terminal server home directory.

    Default: -r-w-x

    QER | Person | User | AccessRights | TerminalHomeDir | User

    Defines the user’s terminal server home directory permissions.

    Default: +r+w-x

To grant access permissions for the profile directory on a terminal server

  • In the Designer, set the QER | Person | User | AccessRights | TerminalProfileDir and its configuration subparameters, and enter the access permissions in the configuration parameters.

    Granting access permissions to the profile directory is done by the One Identity Manager Service.

    Table 69: Configuration parameters for access permissions to the profile directory on a terminal server
    Configuration parameter Effect when set

    QER | Person | User | AccessRights | TerminalProfileDir

    Configuration of access permissions for an Active Directory user account’s terminal server profile directory. To set permissions, the configuration parameter and subparameters need to be set.

    QER | Person | User | AccessRights | TerminalProfileDir | EveryOne

    Everyone has permissions to access a user’s terminal server profile directory.

    Default: -r-w-x

    QER | Person | User | AccessRights | TerminalProfileDir | User

    Terminal server profile directory permissions.

    Default: +r+w-x

Related topics

Configuration parameters for managing an Active Directory environment

The following configuration parameters are additionally available in One Identity Manager after the module has been installed.

Table 70: Configuration parameters
Configuration parameters Description

QER | ITShop | AutoPublish | ADSGroup

Preprocessor relevant configuration parameter for automatically adding Active Directory groups to the IT Shop. If the parameter is set, all groups are automatically assigned as products to the IT Shop. Changes to this parameter require the database to be recompiled.

If you disable the configuration parameter at a later date, model components and scripts that are not longer required, are disabled. SQL procedures and triggers are still carried out. For more information about the behavior of preprocessor relevant configuration parameters and conditional compiling, see the One Identity Manager Configuration Guide.

QER | ITShop | AutoPublish | ADSGroup | AutoFillDisplayName

The configuration parameter specifies whether the template should be applied to the ADSGroup.DisplayName column.

QER | ITShop | AutoPublish | ADSGroup | ExcludeList

List of all Active Directory groups that must not be automatically assigned to the IT Shop. Each entry is part of a regular search pattern and supports regular expression notation.

Example:

.*Administrator.*|Exchange.*|.*Admins|.*Operators|IIS_IUSRS

TargetSystem | ADS

Preprocessor relevant configuration parameter for controlling database model components for Active Directory target system administration. If the parameter is set, the target system components are available. Changes to this parameter require the database to be recompiled.

If you disable the configuration parameter at a later date, model components and scripts that are not longer required, are disabled. SQL procedures and triggers are still carried out. For more information about the behavior of preprocessor relevant configuration parameters and conditional compiling, see the One Identity Manager Configuration Guide.

TargetSystem | ADS | Accounts

Allows configuration of user account data.

TargetSystem | ADS | Accounts | InitialRandomPassword

Specifies whether a random password is generated when a new user account is added. The password must contain at least those character sets that are defined in the password policy.

TargetSystem | ADS | Accounts | InitialRandomPassword | SendTo

Employee to receive an email with the random generated password (manager cost center/department/location/business role, employee’s manager or XUserInserted). If no recipient can be found, the password is sent to the address stored in the configuration parameter TargetSystem | ADS | DefaultAddress.

TargetSystem | ADS | Accounts | InitialRandomPassword | SendTo | MailTemplateAccountName

Mail template name that is sent to supply users with the login credentials for the user account. The Employee - new user account created mail template is used.

TargetSystem | ADS | Accounts | InitialRandomPassword | SendTo | MailTemplatePassword

Mail template name that is sent to supply users with the initial password. The Employee - initial password for new user account mail template is used.

TargetSystem | ADS | Accounts | MailTemplateDefaultValues

Mail template used to send notifications about whether default IT operating data mapping values are used for automatically creating a user account. The Employee - new user account with default properties created mail template is used.

TargetSystem | ADS | Accounts | NotRequirePassword

Specifies whether a password is required when creating new Active Directory user accounts in One Identity Manager. If the configuration parameter is not set, entry of a password that meets the defined password guidelines is requested when a new Active Directory user account is created. If the configuration parameter is set, it is not necessary to specify a password when creating new Active Directory user accounts.

TargetSystem | ADS | Accounts | PrivilegedAccount

Allows configuration of privileged Active Directory user account settings.

TargetSystem | ADS | Accounts |
PrivilegedAccount | SAMAccountName_Postfix

Postfix for formatting the login name of privileged user accounts.

TargetSystem | ADS | Accounts | PrivilegedAccount |
SAMAccountName_Prefix

Prefix for formatting a login name of privileged user accounts.

TargetSystem | ADS | Accounts | ProfileFixedString

Fixed string appended to the default profile path of a user profile.

TargetSystem | ADS | Accounts | TransferJPegPhoto

Specifies whether changes to the employee's picture are published in existing user accounts. The picture is not part of default synchronization. It is only published when employee data is changed.

TargetSystem | ADS | Accounts | TransferSIDHistory

Specifies whether the SID history is loaded from the target system.

TargetSystem | ADS | Accounts | TSProfileFixedString

Fixed string appended to the default profile path of a user profile on a terminal server.

TargetSystem | ADS | Accounts | UnlockByCentralPassword

Specifies whether the employee's Active Directory user account is unlocked when the central password is synchronized.

TargetSystem | ADS | Accounts | UserMustChangePassword

Specifies whether the Change password at next login option is enabled when a new user account is created.

TargetSystem | ADS | AuthenticationDomains

Pipe (|) delimited list of domains to be used by the manual Active Directory authentication module to authenticate users. The list is processed in the given order. This list should only contain domains to be synchronized.

Example:

MyDomain|MyOtherDomain

For more information about One Identity Manager authentication modules, see the One Identity Manager Authorization and Authentication Guide.

TargetSystem | ADS | AutoCreateDepartment

Specifies whether departments are automatically created when user accounts are modified or synchronized.

TargetSystem | ADS | AutoCreateLocality

Specifies whether locations are automatically created when user accounts are modified or synchronized.

TargetSystem | ADS | AutoCreateHardwaretype

Specifies whether corresponding device types are created automatically in the database for imported printer objects.

TargetSystem | ADS | AutoCreateServers

Specifies whether entries for missing home servers and profile servers are created automatically when user accounts are synchronized.

TargetSystem | ADS | AutoCreateServers | PreferredLanguage

Language of automatically created servers.

TargetSystem | ADS | DefaultAddress

Default email address of the recipient for notifications about actions in the target system.

TargetSystem | ADS | HardwareInGroupFromOrg

Specifies whether computers are added to groups based on group assignment to roles.

TargetSystem | ADS | MaxFullsyncDuration

Maximum runtime of a synchronization in minutes. No recalculation of group memberships by the DBQueue Processor can take place during this time. If the maximum runtime is exceeded, group membership are recalculated.

TargetSystem | ADS | MembershipAssignCheck

Specifies whether membership validity is verified on saving when group memberships are assigned in the One Identity Manager database.

Disable this configuration parameter if several trusted domains with access across memberships are managed in the database.

TargetSystem | ADS | MemberShipRestriction

General configuration parameter for restricting membership in Active Directory.

TargetSystem | ADS | MemberShipRestriction | Container

Number of Active Directory objects allowed per container before warning email is sent.

TargetSystem | ADS | MemberShipRestriction | Group

Number of Active Directory objects allowed per group before warning email is sent.

TargetSystem | ADS | MemberShipRestriction | MailNotification

Default mail address for sending warning emails.

TargetSystem | ADS | PersonAutoDefault

Mode for automatic employee assignment for user accounts added to the database outside synchronization.

TargetSystem | ADS | PersonAutoDisabledAccounts

Specifies whether employees are automatically assigned to disabled user accounts. User accounts are not given an account definition.

TargetSystem | ADS | PersonAutoFullSync

Mode for automatic employee assignment for user accounts that are added to or updated in the database by synchronization.

TargetSystem | ADS | PersonExcludeList

Listing of all user account without automatic employee assignment. Names are listed in a pipe (|) delimited list that is handled as a regular search pattern.

Example:

ADMINISTRATOR|GUEST|KRBTGT|TSINTERNETUSER|IUSR_.*|IWAM_.*|SUPPORT_.*|.* | $

TargetSystem | ADS | PersonUpdate

Specifies whether employees are updated if their user accounts are changed. This configuration parameter is set to allow ongoing update of employee objects from associated user accounts.

TargetSystem | ADS | ReplicateImmediately

Speeds up synchronization of modifications between two domain controllers When set, the accumulated modifications in Active Directory are immediately replicated between domain controllers.

TargetSystem | ADS | VerifyUpdates

Specifies whether changed properties are checked when the system is updated. If this parameter is set, the objects in the target system are verified after every update.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen