NOTE: All editing options are also available in the Designer under Base Data | Installation | Job server.
The server function defines the functionality of a server in One Identity Manager. One Identity Manager processes are handled with respect to the server function.
NOTE: More server functions may be available depending on which modules are installed.
Table 19: Permitted server functions
Active Directory connector
Server on which the Active Directory connector is installed. This server synchronizes the Active Directory target system.
|Server on which the CSV connector for synchronization is installed.
The Active Directory domain controller. Servers that are not labeled as domain controllers are considered to be member servers.
Server that acts as a print server.
Server for generic synchronization with a custom target system.
Server for adding home directories for user accounts.
This server automatically updates the software on all the other servers. The server requires a direct connection to the database server that One Identity Manager database is installed on. It can run SQL tasks.
The server with the One Identity Manager database installed on it is labeled with this functionality during initial installation of the schema.
SQL processing server
It can run SQL tasks. The server requires a direct connection to the database server that One Identity Manager database is installed on.
Several SQL processing servers can be set up to spread the load of SQL processes. The system distributes the generated SQL processes throughout all the Job servers with this server function.
CSV script server
This server can process CSV files using the ScriptComponent process component.
Native database connector
This server can connect to an ADO.Net database.
One Identity Manager database connector
Server on which the One Identity Manager connector is installed. This server synchronizes the One Identity Manager target system.
One Identity Manager Service installed
Server on which a One Identity Manager Service is installed.
Primary domain controller
Primary domain controller.
Server for setting up profile directories for user accounts.
SAM synchronization Server
Server for running synchronization with an SMB-based target system.
Server from which One Identity Manager Service sends email notifications. Prerequisite for sending mails using One Identity Manager Service is SMTP host configuration.
Default report server
Server on which reports are generated.
Windows PowerShell connector
The server can run Windows PowerShell version 3.0 or later.
Home and profile servers are expected when user account home and profile directories are added.
To declare home and profile servers
- OR -
- Select the Active Directory | Basic configuration data | Servers category.
- Select the Job server entry in the result list.
- Select the Change master data task.
- Edit the Job server's master data.
- Select the Assign server functions task and specify the Home server and Profile server server functions.
- Save the changes.
You may use other settings for create home and profile directories.
- If you want a user’s home directory to be linked at the time of login, in the Designer, set the QER | Person | User | ConnectHomeDir configuration parameter.
- To create the user profile in the user’s home directory, in the Designer, set the QER | Person | User | PropertyMapping | ProfileFromHome configuration parameter.
- You can use a batch file for creating the home directory, the result of which determines whether the home directory is enabled.
- You can create a template structure on the profile server that is used in the process of creating the profile directory.
- Home and profile directory permissions can be granted through the One Identity Manager Service.
To satisfy specific demands of individual network environments, you can use a batch file, which is executed when you create a home directory with One Identity Manager Service. Whether the home directory is ultimately enabled depends on the result of executing 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 executed 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 executed (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.
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 executing 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 execution returns an exit code 0, the home directory is created. Otherwise, the process is aborted with a log message.
Batch call after creating the home directory:
\\ServHome\Netlogon\Dom2\HomePost.CMD Test1 Dom2 Serv3 TestShare5 TestHome6 Share7
The different Windows operating system versions use different repositories for roaming user profiles. For exact information about storing roaming profile, see the MicrosoftTechNet Library.
To map the roaming user profile in One Identity Manager.
As a result, the directory paths for the user profiles are mapped as follows in the default installation.
The following directories exist after handling the processes.
- If the profile directory is created in the home directory:
- If the profile directory is not created in the home directory:
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.