NOTE: All editing options are also available in the Designer under Base Data > Installation > Job server.
NOTE: More properties may be available depending on which modules are installed.
Table 63: Job server properties
|
Server |
Job server name. |
|
Full server name |
Full server name in accordance with DNS syntax.
Syntax:
<Name of servers>.<Fully qualified domain name> |
|
Target system |
Computer account target system. |
|
Language |
Language of the server. |
|
Server is cluster |
Specifies whether the server maps a cluster. |
|
Server belongs to cluster |
Cluster to which the server belongs.
NOTE: The Server is cluster and Server belongs to cluster properties are mutually exclusive. |
|
Local Active Directory DC |
You can enter a domain controller that is physically nearby for home servers or profile servers on a member server. The Active Directory is accessed over it when jobs are being processed. If no server is entered the main domain controller for the domain is used. |
|
IP address (IPv6) |
Internet protocol version 6 (IPv6) server address. |
|
IP address (IPv4) |
Internet protocol version 4 (IPv4) server address. |
|
Max. number of homes |
Maximum number of home directories to maintain if the server is a home server. This number is compared with the number of (according to the database) existing home directories on the server (<Homes created>) when a new home directory is added for a user. If this number is less than the given maximum number of directories, the home can be added. Otherwise the addition of a new home directory is forbidden. |
|
Homes created |
Number of homes directories already in existing on the home server. |
|
Copy process (source server) |
Permitted copying methods that can be used when this server is the source of a copy action. At present, only copy methods that support the Robocopy and rsync programs are supported.
If no method is given, the One Identity Manager Service determines the operating system of the server during runtime. Replication is then performed with the Robocopy program between servers with a Windows operating system or with the rsync program between servers with a Linux operating system. If the operating systems of the source and destination servers differ, it is important that the right copy method is applied for successful replication. A copy method is chosen that supports both servers. |
|
Copy process (target server) |
Permitted copying methods that can be used when this server is the destination of a copy action. |
|
Max. home storage space [MB] |
Maximum permitted storage in MB for home directories on the home server. This is taken into account when the home directory is allocated. |
|
Coding |
Character set coding that is used to write files to the server. |
|
Parent Job server |
Name of the parent Job server. |
|
Executing server |
Name of the executing server. The name of the server that exists physically and where the processes are handled.
This input is evaluated when the One Identity Manager Service is automatically updated. If the server is handling several queues, the process steps are not supplied until all the queues that are being processed on the same server have completed their automatic update. |
|
Queue |
Name of the queue to handle the process steps. The process steps are requested by the Job queue using this queue identifier. The queue identifier is entered in the One Identity Manager Service configuration file. |
|
Server operating system |
Operating system of the server. This input is required to resolve the path name for replicating software profiles. The values Win32, Windows, Linux, and Unix are permitted. If no value is specified, Win32 is used. |
|
Service account data |
One Identity Manager Service user account information. In order to replicate between non-trusted systems (non-trusted domains, Linux server), the One Identity Manager Service user information has to be declared for the servers in the database. This means that the service account, the service account domain, and the service account password have to be entered for the server. |
|
One Identity Manager Service installed |
Specifies whether a One Identity Manager Service is installed on this server. This option is enabled by the QBM_PJobQueueLoad procedure the moment the queue is called for the first time.
The option is not automatically removed. If necessary, you can reset this option manually for servers whose queue is no longer enabled. |
|
Stop One Identity Manager Service |
Specifies whether the One Identity Manager Service has stopped. If this option is set for the Job server, the One Identity Manager Service does not process any more tasks.
You can make the service start and stop with the appropriate administrative permissions in the Job Queue Info program. For more information, see the One Identity Manager Process Monitoring and Troubleshooting Guide. |
|
No automatic software update |
Specifies whether to exclude the server from automatic software updating.
NOTE: Servers must be manually updated if this option is set. |
|
Software update running |
Specifies whether a software update is currently running. |
|
Server function |
Server functionality in One Identity Manager. One Identity Manager processes are handled with respect to the server function. |
Related topics
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 64: Permitted server functions
|
Active Directory connector |
Server on which the Active Directory connector is installed. This server synchronizes the Active Directory target system. |
|
CSV connector |
Server on which the CSV connector for synchronization is installed. |
|
Domain controller |
The Active Directory domain controller. Servers that are not labeled as domain controllers are considered to be member servers. |
|
Printer server |
Server that acts as a print server. |
|
Generic server |
Server for generic synchronization with a custom target system. |
|
Home server |
Server for adding home directories for user accounts. |
|
Update server |
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. |
|
Generic 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. |
|
Profile server |
Server for setting up profile directories for user accounts. |
|
SAM synchronization Server |
Server for running synchronization with an SMB-based target system. |
|
SMTP host |
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. |
Related topics
Home and profile servers are expected when user account home and profile directories are added.
To declare home and profile servers
-
In the Designer, set the TargetSystem | ADS | AutoCreateServers and TargetSystem | ADS | AutoCreateServers | PreferredLanguage configuration parameters.
If these configuration parameters are set, entries for missing home servers and profile servers are created automatically when user accounts are synchronized.
- OR -
-
In the Manager, select the Active Directory > Basic configuration data > Server category.
-
Select the Job server entry in the result list.
-
Select the Change main data task.
-
Edit the Job server's main 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.
Related topics
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
