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
Total Posts 158

How Add2Exchange Works

In order to access Add2Exchange, you must be logged into the "replication server" as the Add2Exchange Service Account, by default, named "zadd2exchange" if installed as the default user.  If you do not know the Sync Service account, stop the Add2Exchange SErvice on the replication server and change the password and make note of it.  It is a powerful account, so make it be hard to guess and not the same as any other account.

In order for Add2Exchange to replicate, you cannot have the Add2Exchange Console open or be making changes to the relationships in the Add2Exchange Console.  Also, there can not be another session with that account logged in with the Add2Exchange Console open.  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 Add2Exchange event log for success or failures.  We suggest setting logging to start and stop logging to monitor sync times. Please close the Add2exchange Console and start the Add2Exchange service. 

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 will ask you to start the Add2Exchange Service.  Start it.  If if fails, check password starting the Add2Exchange Service. You can start the Add2Exchange Service from the Services Control Manager (services.msc) applet with the A2E Service Account Credentials.  The SQL2005 Express A2ESQLServer Instance should also be started with the A2E Service Account Credentials, but SQL2008 should be started as local system account.   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 the Add2Exchange Service Starts, A2E will do the first sync cycle, which is independent of the timers.   In the Add2Exchange Console there are several modules in the Services Utility.  If set to anything other than 0, it will do that kind of Sync, and then finish, then wait 60 seconds and then do the next type.  The initial Sync will run all modules and then wait about 60 seconds between modules and run the next no matter what the time sleep interval is set to in the Console. 
It runs GAL, RELMAN, CALENDARS, CONTACTS, POSTS, NOTES, TASKS, and Confidential Email Notifier. 
This special timing 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 Add2Exchange Service and if syncing, the AddAgent.

How A2E works:

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

If you open Task manager and go to processes tab and sort by image name for all users, it shows the Add2Agent program getting some CPU time, sometimes in bursts.  That program usuallyi stays in memory during the entire processing of all relationships of that folder type.   When it is done with that relationship type, it will drop, and if there is another one, the Add2Agent will direct to load and process that relationship automaticallyi until they are all completed.  If you have Start and Stop logging on from within the Add2Exchange Console, Services, Utility, it will put a success audit of that module 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 each folder type, it waits another 60 seconds and then does Contacts and then Tasks, etc, 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 Add2Exchange Enterprise edition, you can "turn off" the sync process modules for each module type 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 module runs 60 seconds after the Add2Exchange Service is initially started after the Add2Exchange Console is closed. 

First the Gal Syncing (GALSync) caching function runs if set to some non zero schedule.  All the GAL items specified to be included in the GAL sync are copied and synced to that location specified.  Usually the GAL is set to once a day or more, depending on amount of GAL changes expected.  Remember,  if you want it more often, you can always stop the Add2Exchange Service, wait for it to stop, and then start it up again.

Next, after GAL is done, (or first if GAL is set to off)  it will wait 60 seconds and then process Relationship Management (RelMan) if set to some non zero schedule. Usually this is set to once a day.    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