Our entire SharePoint web part listing.
Click on the Web Part to read a more detailed description
Synchronize user information between the SharePoint User Profile database, Active Directory, Contact Lists and WSS 3.0 User Information Lists
The Bamboo User Profile Sync allows you to automatically synchronize a master user database with another user database. You can map properties from the master user database to the target user database and view whether the update was successful as well as an audit trail of how each item was updated. In addition, you can use the Windows Scheduler to automate the sync process. There are five sync types offered with User Profile Sync. They are:
| Bamboo User Profile Sync vs. SharePoint Base Functionality |
SharePoint OOTB | User Profile Sync |
| Choose from the following sync types:
|
||
| Schedule updates to run automatically from one user database to another. | ||
| Flexible mapping of user information from one database to another. | ||
| Audit trail of imported data. | ||
| Ability to exclude certain users or groups. | ||
| Supports SharePoint's Business Data Catalog (BDC) integration service. | Coming Soon | |
| Generate e-mail notification when changes are made to User Profile database. | Coming Soon |
First, configure the proper settings depending on your sync type. Then enter in a user name and password for an account that has proper rights to both user database sources. For example, for the Active Directory to WSS 3.0 User Information List (B) sync type, you need one user ID and password that is both an Active Directory Admin account and SharePoint Site Collection Administrator account. Then define mappings between the master user database and the target user database. After the mappings are defined, then the user data is exported to the appropriate properties according to the defined mappings. This export occurs through a scheduler that runs at your convenience. You can also view a log file to determine whether the export/import of data was successful.
For the Active Directory to Contacts List (D) and Contacts List to WSS 3.0 User Information List (E) sync types, you can define the mappings in the same way as the other sync types, but you must also create a column in the Contacts List that contains the user account name in order to link to the account name in Active Directory or the WSS 3.0 User Information List (depending on the sync type you are using). User Profile Sync requires this link to be able to update the user profile information properly.
During its trial period, User Profile Sync allows you to try each of the sync types offered above. However, depending on the User Profile Sync product (A, B, C, D or E) that you decide to purchase, you will receive a license key that unlocks only that functionality. For instance, if you purchased User Profile Sync B for syncing Active Directory to WSS 3.0 User Information List, then you will receive a license key that allows you to use User Profile Sync only to update information in your WSS User Information List with Active Directory profile information.
Most organizations that use SharePoint also leverage the Active Directory and NT user account management systems. In most cases the SharePoint portal is used to create the initial user profile by importing data from the Active Directory. Next, an import schedule is set up to update the SharePoint user profile to maintain the changes in the Active Directory database. As SharePoint user profile information grows in capacity, organizations frequently need to use it as the primary user information repository. User Profile Sync allows organizations to utilize this familiar set up, but at the same time migrate the profile information back into Active Directory, which then can be shared and used by other applications that interface with Active Directory. It is for this same reason that small to medium organizations using WSS 3.0 (instead of MOSS 2007) may need to sync their User Information List to Active Directory or, if they don't use Active Directory at all, they may need to sync a master User Information List to one or more User Information Lists.
As for using a Contacts List as a user database, many organizations running WSS 3.0 prefer to use a Contacts List instead of the User Information List since Contact Lists are easier to manage, extend and access while also maintaining security. The User Information List is not easy to locate and cannot be easily extended.