|
<< Click to Display Table of Contents >> Navigation: System Administration > Interfaces > bMS-Interface > Setup Import bMS AD Persons |
Importing person data from bMS
With bMS bConnect version 2.0, it is also possible to perform an automatic user import.
This allows user data that is synced with a local AD in bMS to be automatically synced with bTS.
This requires at least the bConnect 2.0 interface on the bMS side
|
Important note: •To ensure that all data required for bTS is available in the bMS bConnect interface, variables must be created in bMS.
•It is not recommended to import data for the same individuals via both CSV and bMS at the same time, in order to avoid potential conflicts.
•You can find instructions for preparing data imports on the bMS side in the baramundi Knowledge Base (requires a baramundi Support Account): https://feedback.baramundi.de/knowledge-base/article/KB17190-DE |
Importing person data from bMS into the ticket system
1. Start import
Personal data can be imported from bMS either as a one-time import or at regular intervals.
For a one-time import, select the appropriate job (“Import AD users from baramundi”) and the desired execution time in the “Import objects from the baramundi Management Suite” section.

|
Note: A job is created as soon as the user clicks the “Execute” button and is executed as soon as the scheduled execution time is reached. If no specific execution time has been selected, the job is executed immediately. |
To set up automatic imports at regular intervals, you must specify the import interval and the start time (“Automatic Person Import Time”). Automatic imports are scheduled and executed at the start time.

2. Execute import
Scheduled and completed imports are displayed in the list at the bottom of the form.

Please note the following:
If the status “Successful” is displayed, the import job was executed without technical errors and the connection to bMS is working properly.

However, it is possible that some records or references could not be imported. This is caused by incorrect or incomplete data within bMS.
|
Note: If a job execution has a “Successful” status despite an error description, this does not indicate an error with the interface or the import. The cause lies in the data within bMS and must be resolved there. |
Detailed information on this can be found in the error description for the respective job run. There, the affected records are listed section by section along with the corresponding cause.
The error messages first indicate the affected object, for example:
“Error saving new person …”
The cause or a troubleshooting tip is then displayed, for example:
“Please fill in the following required field(s): Organizational Unit”

In the screenshot shown, users could not be imported because the required “Organizational Unit” field was not filled in the data provided, or the organizational unit provided has not (yet) been created in the system.
If the status “Failed” is displayed, a connection to bMS could not be established, or the import job could not be started.
In this case, first check whether the configured connection details have been entered correctly. In particular, verify the server address, username, password, and other configured connection settings (for more detailed information, see: Setup Interface Gateway.
If you cannot identify the cause and the error persists, please contact Support.