Difference between revisions of "Retain Address Book"

Revision as of 23:10, 29 December 2014

Address Book

Here we will discuss the t_abook table in the database, which holds the "address book" info. This might also be a good place to discuss how Retain gets the data via LDAP from Exchange, SOAP via GroupWise, and csv files for O365 via powershell scripts.

SOAP via GroupWise

The Trusted Application Key allows Retain full access to the GroupWise API to ask for the List of users and groups which is handed off via the SOAP protocol.

LDAP via Exchange

Retain logs into Active Directory with the Impersonation User Account and accesses the homeMDB field.

That directory path allows Retain to retrieve the homeMDBBL field from Active Directory which provides the list of mailboxes in Exchange.

O365 via Powershell

Retain uses the data in the exchangeusers.csv and exchangegroups.csv to allow users to log into Retain the first time. If exchangeusers.csv is blank (as sometimes happens). Once they have logged in Retain uses its internal database of user credentials.

One of the big things about using sync365.ps1 is that you have to set up a recurring task in Task Scheduler so that it is updated regularly (eg Nightly).

If you are good at powershell create a script that will copy the current version of exchangeusers.csv and exchangegroups.csv to a safe place if it is not 0 bytes.

Mailbox Mapping and Merging

This is different from what Migration Tool Kit does.

This is used when merging two email systems. The typical example is an organization migrates from GroupWise to Exchange. To make things easy for the users mailbox merging can be used to make the user's GroupWise and Exchange mailbox look like one within Retain.

Important: This needs to be setup before refreshing the address book of the new system for the first time.

Back to Retain Module Configuration