If your question doesn't fit those topics, or you wish Add2Exchange did something else too, post here

5/23/2011 11:51:07 AM
Gravatar
Total Posts 156

How Add2Exchange Works

In order to access Add2Exchange, you must be logged into the "replication server" as the Add2Exchange Service Account, usually named zadd2exchange if installed as the default.

In order for Add2Exchange to replicate, you cannot be making changes to the Add2Exchange Console.  Please close the Add2exchange Console and start the Add2Exchange service.

Tip: Sometimes there may be another RDP connection to the server (TSADMIN) which has the Add2exchange Console open in another session.  Look to Task Manager for all users image name on the replication server.  You can see success audits eventually in the Add2Exchagne event log for success or failures.  We suggest setting logging to start and stop logging to monitor sync times.

If you open the Add2Exchange Console after you start the Add2Exchange (A2E) Service, the A2E Service will the stop automatically.

When you close the A2E Console it may or may not ask you to start the service (does not in Win 2008 R2).  If it asks you, then start it.  If not you can start the Add2Exchange Service from the Services Control Manager (services.msc) applet with the A2E Service Account Credentials.  The SQL 2005 A2ESQLServer Instance should also be started with the A2E Service Account Credentials.  We have made a white DidItBetter Management Console (DidItBetter MMC.msc) on your desktop which combines many useful features used in A2E for ease of use. 

After Add2Exchange Starts, A2E will do an initial sync.  An initial Sync will wait about 60 seconds and then run a full cycle of Calendars, then after all Calendar relationships are done, it will wait 60 seconds and then do Contact replication and if relationships it will load and sync.  When done with Contacts, it will wait 60 seconds, and then do Task replication. This happens only if the A2E Console is closed and no matter what interval you set in the Add2Exchange program.  After it does this initial sync cycle, it will wait the intervals you specify and then start syncing for that folder type.  If you open the Console, it stops the A2E Director, the A2ESP (sync) and the Add2Exchange Service.

How A2E works:

The Add2Exchange Service is in memory 24/7 365.  When it hits the initial sync cycle or on the timed interval, the A2E Director comes into memory and directs the program on which folder type to replicate. 

A2E Standard edition.  60 Seconds after the service is initially started, A2E will sync Calendars. A2E loads the A2E Director and looks for a calendar relationship and if it finds it, it will load the A2ESP.exe to replicate.  It will drop A2ESP.exe when done and then load another until it is complete.

If you open Task manager and go to processes tab and sort by image name for all users, it shows the A2ESP program getting some CPU time, sometimes in bursts.  Again, when it is done with that relationship, it will drop, and if there is another one, the A2E Director will direct the A2ESP to load and process that relationship. If you have Start and Stop logging on from within the Add2Exchange Console, Services, Utility, it will put a success audit in the Add2Exchange Event log.  You can conveniently access that from the White DidItBetter MMC icon on the desktop or from Event viewer.msc.

Then when done with Calendars, it waits another 60 seconds and then does Contacts and then Tasks, then it will wait until the appropriate interval and do them again.  They will not run simultaneously, but wait for the next cycle.  Each will put a success audit in the log.  Add2Exchange will always report all errors and Start and Stop logging is normal and will tell you how long it takes for each sync cycle for each folder type.

With A2E Enterprise edition, there are more services to run because it has the additional functionality.  Unlike A2E Standard, you can turn off the sync process for each service from within the Add2Exchange Console, Services, Utility.  The order for Enterprise edition to run through syncing is slightly different, but each folder type goes through the initial sync.  If not set to 0, for time interval (off), each service runs 60 seconds after the Add2Exchange Service is initially started after the Console is closed.  First the Gal Syncing (GALSync) caching function runs.  Then since Add2Exchange Enterprise employs a relationship template system for the attachment to distribution groups for the automatic creation and removal of relationships, it runs the Relationship Manager (RELMan).  If on, these two processes run before Calendars, Contacts, Tasks, Notes, Posts and the “Confidential-E Post it Notifier” process with a 60 second interval between them in that order.  Again, in the Enterprise Edition, you can turn off each process so they don’t run if not turned on.  A review of the Task Manager Processes Tab and sorted by Image name and Add2Exchange Event Viewer will give you a clearer understanding of how the program operates and how long it takes to sync each folder type.  Keep the Logging on Start and Stop logging from within the Add2Exchange Console.  There is usually no need to do Full logging as any errors will always show. Look for Success Audits in the Add2Exchange Event Viewer for a history of syncs and how long it takes.

If you have issues, please communicate to Support the "free way" (comes with every license) is to send any of your event log failures, together with an Export of your Setup (Help- Export) attached to an email support request here: /support-request.aspx

Live Help for Exchange Sync