User Information Management in Sharepoint Server

This article continues with the last section of SharePoint 2007 user groups and users. For user information management in Sharepoint Server, choral also wrote a related article "User Information Synchronization in SharePoint". This article further explains and explains the relevant information.

First, the first image is marked as A, B, C, D, and E in the figure to make it easier to specify the corresponding part of the image, mark a and mark B as follows ):

In a standard Sharepoint Server server farm deployment model, a user's information is stored in multiple places at the same time:

1. Active Directory ("A mark ")
In AD, basic information is stored. ad is usually the location of basic user ID information in the enterprise.

2. Sharepoint Server SSP user profile ("C mark ")
The user profile of the Shared Service (SSP) in the Sharepoint Server Farm also saves user information. The user information in SSP user profile is stored as the user information in the Sharepoint Server Farm. If you need to store certain attributes of a user in a Sharepoint application, we recommend that you store them in the SSP user profile. User profile can be extended. For example, the administrator can add a new "QQ number" attribute.

User Information in user profile is imported from AD by default ("B mark" identifies this process). In SSP user profile management, we can configure this import process, for example, you can specify how long the user information will be completely imported from the ad.

When SSP user profile imports user information from AD, SSP determines which attribute value of the user in AD based on the user profile attribute ing definition, which attribute is assigned to the user profile. For example, SSP imports the value of the "display name" attribute in ad to the "name" attribute of user profile. On the "edit user configuration file attributes" page of SSP management, you can edit (or cancel) This property ing relationship.

How can I modify the user attribute information stored in the user profile? First, the administrator can directly modify the attributes of all users in SSP management. Secondly, each user can modify their user profile information through his/her personal website ("My website.
 

Note 1: Why can't users modify certain attributes? For example, the "name" attribute cannot be modified by default?
In SSP user profile management, the administrator can specify which attributes can be modified by the user and which attributes cannot be modified by the user. For example, if the administrator allows the user to modify the "name" attribute of the user profile:

Then, you can modify the value of the "name" attribute on your personal website:

NOTE 2: If the user modifies the user profile value by himself (or the administrator modifies the value), will it be overwritten into the value of the AD when the user information is fully imported from the ad in the next time?
Yes. For example, we allow the user to modify the value of the "name" attribute of the user profile, but because the default "name" attribute is mapped to the "display name" attribute in the ad, therefore, during the next full ad import ("B mark"), the user's "name" attribute in the user profile is automatically set to the "display name" value in the ad. However, the administrator can cancel this ing relationship. For example, we can cancel the ing between the "name" attribute and the "display name" attribute of the AD:

Changed:

NOTE 3: Can I automatically reverse sync the user information in the user profile back to the Active Directory?
No.

In addition to importing user profile information from AD, Sharepoint also supports importing from other data sources, such as LDAP server. You can also useCodeAdd User information to and from the user profile.

3. SharePoint site ("E mark ")
In each SharePoint site (more accurately, it should be a site set), the information of each site user is also saved. This information is stored in the userinfo table of the content database of each site (it is not a good idea to modify the database table directly, the correct method is to use the spuser object model to access the user information in the SharePoint site ). We can see in the upper-right corner of the page