The Add2Exchange Service requires very particular permissions over the Exchange Information Stores, permissions which are explicitly denied to the Administrator account and most other administrative roles (and periodically reset by the system, even if they have been manually reconfigured by you, the administrator) .  While you may be tempted to combine the Add2Exchange Service Account role with another account (such as a Blackberry admin account), this invariably results in unmaintainable configuration that either never works or breaks in the future.  Fixing such configurations is much more difficult than simply following the instructions in this manual.  DidItBetter Software does not support such configurations.

If you have already installed Add2Exchange as the Administrator or any other account, see the Add2Exchange Technical Bulletin 173 for instructions on migrating Add2Exchange to a new Service Account.

The Add2Exchange Service requires very particular permissions over the Exchange Information Stores, permissions which are explicitly denied to the Administrator account and most other administrative roles (and periodically reset by the system, even if they have been manually reconfigured by you, the administrator) .  For this reason, the Service Account cannot be a member of any groups other than those shown in the instructions.

Also, DON'T delegate Exchange rights to the Service Account using the Delegate control... function in Exchange System Manager.  This will break synchronization.

If you are installing Add2Exchange on a separate Synchronization Server, please refrain from installing Outlook there.

If Outlook has already been installed on your Exchange/Synchronization Server, the instructions will show you how to remove it and reregister CDO.

The Service Account must be visible in the Global Address List for synchronization to function.

Add2Exchange tags any copy it generates with a hidden field, designating the new item as a copy.  If you or a user places a copy in a Source folder, expecting it to replicate, the relationship will ignore the item and no other copy will be generated.

In order to restore or move items into a Source folder, make sure they were the originals from a Source folder.  If you are unsure about whether the items you have are originals, you can "clean" items of the hidden field by exporting and importing the items to a CSV file.  See Add2Exchange Technical Bulletin 153 for details on how to do this and the limitations imposed by this process.

The Add2Exchange Console and Service require the special permissions associated with the Service Account.  Running them from another account, even using Run as... functionality will not give the proper permissions for Add2Exchange to synchronize.

Always log on with the Add2Exchange Service Account whenever administering Add2Exchange.

Pivot folders are working space for items to be moved between mailboxes.  They should be hidden from users and should definitely not be the Source or Destination of a relationship.  See the section Create Pivot Folders for details on how to configure these folders.

When moving Exchange to a new server, Exchange changes the identifiers used by Add2Exchange to track the relationship.  Relationships and Add2Exchange copies must be removed (part of the relationship deletion process) prior to moving the mailboxes and public folders to the new server.  Installation on the new server proceeds like a brand new install.

New licensing keys must be requested from the new server.

Add2Exchange requires special configuration and permissions and is meant to run in a server environment.  See the System Requirements section for details.

Add2Outlook and Add2Exchange are aware of each other and will not synchronize folders used in relationships of the other.  If Add2Outlook's relationships are not deleted prior to running Add2Exchange, synchronization will appear to fail.  Contact DidItBetter Software support if you have already removed Add2Outlook without removing its relationships.

Once purchased, your license key will only be processed after we receive the licensing information from your system.  This is sent to us by the license key request function in the Add2Exchange Console under the License menu.  See the section License Menu for more details.

See the System Requirements section for details.

See Technical Bulletin 164 for details.

Major revisions of Add2Exchange may make fundamental changes to the way it operates.  Occasionally this causes issues with older installations.  In general it is prudent to always have backups available when making changes to a powerful automated system like Add2Exchange.

Our experience shows that even after following update procedures correctly, some system dependencies of Add2Exchange don't always function properly after a Microsoft/Windows update.  We strongly recommend scheduling a reboot after all Microsoft/Windows updates, even when not mandated by the update system.

Exchange Service Packs may change fundamental assumptions about interoperating with Exchange that are only taken into account by the most recent version of Add2Exchange.

Generally, Windows Service Packs shouldn't cause the same concern.

Upgrading Add2Exchange without renewing your Software Assurance agreement will put relationships into Alert status until a Current Version Upgrade license is purchased, requested from the Add2Exchange Console and installed.  Take care of these prerequisites prior to upgrade to ensure continual operation.

Antivirus scanning severely slows down performance writing to the Add2Exchange database during synchronization.  Exclude the Add2Exchange folders from scanning.

Add2Exchange synchronization changes its database files, sometimes causing file verification errors in the backup.  See the Stopping the Add2Exchange Service during Backup section for details.

Both the Add2Exchange Service as well as the SQL Server (A2ESQLSERVER) service use the Service Account to authenticate.  Change their credentials in the Logon tab of the Services Administrative Tool.