If Add2Exchange was working and now it's not, post here.
A partial mesh is more complicated than just the three templates needed in a full mesh. See it in pictures: Common Relationships.
In a full mesh, you need a public to private, private to public and private to private template attached to one distribution group.
You can make individual relationships, but it is much easier to make relationships with the relationship group manager so you can make exactly what you want with ease, instead of making one to one relationships as in Standard. You can actually drive the relationship creation and removal by the inclusion or removal from a specially attached distribution list, named something like z_ContactSync. The members get the kind of relationships you would attach a template to.
In this case, you have a ripple. Some people can make them and some people can’t, but everyone needs to get copies of the items.
In the Enterprise/365 edition you will need two Distribution lists, one whose members can edit/make items and one whose members cannot.
Scenario: One public folder to 7 people, 2 of which can edit the copied items and update everyone and the same 2 who can make new items and have them go to the Public and to the other 5. The 5 people can make items in their privates, but they dont get copied anywhere.
In our example, let’s call the distribution lists:
z_ContactSync_noedit for those who cannot edit
z_ContactSync_Edit who can edit and make items from their folders.
Your 5 non editing people would be in the z_ContactSync_noedit.
Your two super users (older citizens) can make and edit and are in z_ContactSync_Edit.
Next we would make a few templates to attach them to:
Public to Private - non edit (unidirectional) and attach to z_ContactSync_noedit to make 5 relationships.
Public to Private - edit and create (directional) and attach to z_ContactSync_Edit to make 2 relationships.
Private to Public - attach to z_ContactSync_Edit to make 2 relationships – anything made in the 2 users privates will go to public.
Private User 1 to 5 Users - attach to z_ContactSync_noedit to make 5 relationships - anything made in the private 1 go to 5 users.
Private User 2 to 5 Users - attach to z_ContactSync_noedit to make 5 relationships - anything made in the private 2 go to 5 users.
Single Private User 1 - to user 2 to make 1 relationship - anything made in user 1 goes to 2.
Single Private User 2 - to user 1 to make 1 relationship - anything made in user 2 goes to 1.
Total of 21 relationships.
The result is user 1 and 2 can make and edit all from the public and they make items that go to the public and everyone else.
Non editing users can’t edit anything but get all contact items made in public and either private.
Anyone with editor or above Client access permissions to the public folder can edit and delete any items from the public no matter where it was made.
If this is still confusing, we include remote install and certification support in every Value Bundle so we can set up exactly the relationships you need!!
Below are some tips and links which may prove helpful:
Our Add2Exchange server-side solution is versatile – you can set it up to sync new items created in a public folder to a user’s mailbox folder or another public folder; you can set it up to sync new items made in a user’s mailbox to a public folder or someone else’s private folder. For more information please reference the administration guide ‘Sync Models & Concepts’ sections. For mobile device users who want to view public folders Contacts for example, you would create a public to private relationship for each user from the Exchange public folder Contacts to the user’s mailbox folder; once Add2Exchange gets the information into the personal folder, the device’s sync software takes over from there. If a user will be creating a new item on the device, or in the personal mailbox folder and you want the item to sync to the public folder and to the other users, you would create a private to public folder relationship and also a private to private relationship for each user. When anyone makes it anywhere and it goes to everyone else, we call this a Full Mesh Sync Relationship.
Each relationship has its own sync rules so the data can be for information purposes only or users can edit from the mobile device and it be synced back to others. The same with deleting; it can be recopied if deleted or actually delete them all. You can even exclude items marked ‘private’ for all folder types supporting it. In Calendar relationships you can still block out time and replicate only a portion of the item’s details. To help identify where the copied item came from, it is also helpful to use the automatic placement of initials in the subject of the item.
Every source to destination combination (folder pair) equals 1 relationship; the source is the folder new items are made in and the destination is the folder you want it to sync to. Once installed and set up, the solution works automatically in the background based on the settings and process intervals you selected during the installation.
Helpful Topic: Product Guide includes prerequisites, system requirements and guided install steps.