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 TaskManager 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.
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. If it is time for Calendars, it looks for a calendar relationship and if it finds it, it will load the A2ESP.exe to replicate. 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. 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.
With A2E Enterprise edition, there are more services to run because it has the additional functionality. The order for Enterprise edition is to do the one way Gal Syncing (GALSync) caching to a public folder first, and then since it employs relationship templates attached to distribution groups fo automatic creation and removal of relationships, it runs the Rrelationship Manager (RELMan). 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. However, in the Enterprise Edition, you can turn off each process so they don’t run if not turned on. A review of the TaskManager Processes Tab and sorted by Image name and Add2Exchange Event Viewer will give you a clear understanding of how the program operates.
If there are problems in your installation, the quickest way to fix it is getting on Premier Support which is having us remotely log in and investigate and fix it. http://support.diditbetter.com/premium-support.aspx
The free way which comes with every license is to send any of your event log failures, together with an Export of your Setup (Help- Export) attached to a email support request here: /support-request.aspx