Monthly Archives: April 2006

SharePoint Replication


Do you have the following scenario? “Head office (HQ) with remote locations – location A and location B. Due to bandwidth/geographical consideration, staff at location A Or B do not want to view documents stored at HQ or at the other location. Everyone wants a copy of other location locally”. An ISV product Syntergy Replicator is available to resolve this common situation.

A picture is worth a thousand words – here is a rough schematic of the solution. Syntergy Replication

We proceed as follows. Head Office has SharePoint Portal Server 2003, Location A & Location B have Windows SharePoint Services. In each case MS-SQL server is needed. “EDIT” – The replicator will work with SPS-MSDE but will not work with WSS-WMSDE – I have this clarified from the Syntergy folks who were kind enough to share this information.

A site is created under SPS (http://sps/sites/project). It is designated to replicate to and from each of the locations http://remoteA/sites/project and http://remoteB/sites/project . 3 document libraries are created at http://sps/sites/project, one for each location – Permissions are ‘Read’ all 3 document libraries for entire Active Directory. Head Office doclib has write perms for Head Office staff, Location A doclib has write perms for Location A staff and such for Location B.

The remote SharePoint sites were connected to the portal by using “configure connection to portal” within the WSS. SPS2003 is not asked to search remote sites but only the sites created under SPS, staff at individual locations can search by using WSS (MS-SQL) search. In this way, remote WSS sites are self contained but are also connected to the SPS (visually).

Replicator was setup as a hub and spoke. Each of remote locations replicated to Head Office, then Head Office replicated content back to all. So if someone at Location A added a document, it would be available at Location A, Head Office and then Location B (in that order). 2 way replication setup between Head Office and Location A, &, Head Office and Location B. Location A does not replicate directly to Location B (& other ways around).

Any new document libraries (list, etc) created at any location can be replicated on the fly – there is a configuration setting for this – “select all lists”. If you do not want new libraries to be replicated, uncheck the “select all” box and only select those libraries you want to replicate. This setting is per site.

Any doc lib changed permissions at any locations are replicated.

Conflict resolution can be overridden manually by sending owner, site admin, system generated emails, or system can be configured to accept overrides automatically – this setting is for a virtual server, not individual sites.

This is a good setup and resolution for the problem stated at the beginning.

Cannot view ‘All Web Parts’ on Web Part galleries on SPS


After SPS installation, most likely you will begin customizing the site groups – editing permissions on some (e.g the Members, Contributors, etc) and adding new site groups according to your clients requirements. After this step Area Administrators (or others) may not be able to add all web parts, they see only a subset of all available web parts. Why ? The cause is web part gallery permissions need to be re-set (or re-inherited).

The KB Article is here – http://support.microsoft.com/default.aspx?scid=kb;EN-US;888840