Navigation:  Add2Exchange Sync Overview and Best Practices >

Add2Exchange Operation

Print this Topic Previous pageReturn to chapter overviewNext page

Operation of Add2Exchange consists of:

1)Creating relationships - see the section Add2Exchange Console for details on creating and managing the various kinds of relationships.
2)Exiting the console and starting the Add2Exchange Service - see the section Add2Exchange Service for details on managing the operation of the service.

All management of Add2Exchange must be done from the Add2Exchange service account under which Add2Exchange was installed.  This account has special privileges necessary for both the console and service executables.  Do not try to use the Windows Run as... feature to work around this, as it does not function correctly for Add2Exchange.

All synchronization is performed by the Add2Exchange service.  In order for synchronization to occur, the service must be running.  The service account does not need to be logged into the server interactively (such as on the server console or through Remote Desktop Connection) in order for synchronization to occur.  The service is non-interactive.

The Add2Exchange console stops the Add2Exchange service while it is open so management functions do not interfere with synchronization.  If you want synchronization to occur when you are finished with the console, make sure to start the service.

Service Start Dialog

You will be prompted to start the service when you exit the console, so all you have to do is respond in the affirmative.

Once the Add2Exchange service is started, Add2Exchange waits approximately 30 seconds and then starts processing.  The initial processing of modules goes first with calendars, then with contacts, then with tasks.  The service processes each module once immediately, and according to the schedule for the module thereafter.  See the section Processing Interval for details on setting processing intervals.

Modules are not processed at the same time.  If the schedule for two modules overlaps, they are processed in the order they arrived on the schedule.  If a module's interval is set too short and processing for it has not finished from the last time, it is queued until the last processing has finished.

Windows Task Manager

While the service is synchronizing, you can monitor operation from a high level by using the Windows Task Manager.  While Add2Exchange is synchronizing, the A2E Director.exe and A2ESP.exe processes will appear in the task list.  Be sure you have the Show processes from all users option checked.

Calendar Module Success Audit

When complete, the service puts a Success Audit naming the module which was processed as well as the processing duration in the Add2Exchange event viewer log.  The Add2Exchange Service.exe process remains in the process list, waiting for the next scheduled synchronization to start the other processes.  The service process will exit when the console is opened or the service is stopped.

Add2Exchange relationships will remain defined after the initial trial period has expired; however, they will be in alert status and no synchronization will take place.  When a valid license key is entered into the console, the relationships will come out of alert status and pick up where synchronization left off.  This may cause the initial subsequent synchronization to take longer than usual because of additional processing due to the period of inactivity.

blog comments powered by Disqus


Page url: