Active Directory connector

The AD connector enables read only import of user information from Microsoft Active Directory (AD).

The AD connector does not enable importing of users from Notes.

Using the AD connector, the user can import users and groups from AD using the Select  AD Users function. The AD integration can also be set up to import users automatically at specific times.

The AD connector requires a valid license to be able to connect to the Totalview 3 server.

The TotalviewADTester program can be used to test the settings to be used when reading user information from AD. The tester program is found in then <Totalview>\InstallFiles\AD folder.


AD connector parameters

LDAP address
The path in ActiveDirectory to use when importing users. Only users belonging to the path or groups in the path are imported. If blank, all users in AD are imported.

Examples of LDAP paths are listed below.

In case the user running the AD connector does not have access to ActiveDirectory, credential for a user with access can be added.

Add Username and Password for a user with access to ActiveDirectory. The Username should be in the format

The LDAP address must specify ad domain, or the IP or name of the AD server. E.g., srv-ad or IP address.

When username/password are used the authentication method use is Secure.

Users filter group
Optional LDAP path to group in ActiveDirectory with users to import into Totalview. Only users in the group are imported. If path is left blank all users in the LDAP address path are imported.

It’s required that the Users filter group path is within the LDAP address path.

Ignore paths
Optional LDAP path to filter out users with an ending path equal to specified path. E.g. filter out all users with ending path “ou=Users,dc=Contoso,dc=Com”.

Multiple paths to ignore can be separated by ;.

Device length
Part of the WORK number to be used as local device number in case of fully qualified WORK numbers. E.g. if WORK number is registered as (+45)34123400 then a Device length of 4 will result in a local device number of 3400. If Device length is 0 no changes are made to the WORK number.
Trim numbers
Remove blanks from phone numbers when importing.
Remove parentheses
Remove parentheses from phone numbers when importing.
Include security groups
Include AD security groups in the AD search result. Default is false.
Ignore child groups Only synchronize user in the selected LDAP path and ignore any child groups.
Multiple groups can be separated by ;.
Mapping parameters
If required the default mapping between Totalview fields and AD properties can be changed. Change the default mapping by adding a new mapping for the Totalview field.
More than one AD property can be mapped to the same Totalview field.
Separate the AD property value with comma (,) or semicolon (;) to be able to create more than one Totalview field. E.g. register two mobile numbers separated by comma to have two Totalview contact items of type Mobile created for the user.
The default mappings are listed hereThe Totalview fields that start with CF: are Custom fields. When mapping to custom fields with predefined values, the values must be defined in the list before they can be synchronized.


Examples of LDAP paths

The entire local AD is imported.
The entire AD is imported
LDAP://ADservername or IP
The entire AD is imported.
Users and groups under the TVUsers group are imported.
Users and groups under the TVUsers group on the specified ad server are imported.


Active directory sync settings

Sync with AD
Activate automatic synchronization with AD. When activated the synchronization will be performed once a day at the hour specified in Sync every day at.

The synchronization will read from the current AD and update users in Totalview accordingly.

Clear resource details
If set all the non-private contact information is cleared when a user is synchronized. If not set, contact information is merged. Preferred if all contact information is read from Active Directory.
Sync every day at
Hour of day, in 24 hour format, when to run the automatic AD synchronization.
Last edited on March 14th, 2019