Knowledge about User Profile in MOSS

Q: How many processes can a User Profile be obtained?

A:

Two. The process from Active Directory to SSP is called Profile Import. The process from SSP to Site Collection is called Profile Sync.

 

Q: Will the profile information of all users in SharePoint be synchronized (sync?

A:

No. The profile information of the user whose tp_isactive flag is 1 in the userinfo table is synchronized only when the user is active.

use WSS_Content_80goselect tp_Login, tp_Title, tp_Email, tp_IsActive from UserInfo

 

Q: What is the situation in MySite?

A:

The user will always be active in their own MySite, so it will always be synchronized.

 

Q: under what circumstances will a user be marked as active?

A:

This situation is a bit complicated. however, it is clear to put it slowly. if a user is directly added to the site collection and granted the contribute or higher permissions, the user will be marked as active and his profile will be synchronized. in other words, the user must be active on the site set, and his profile can be synchronized.

 

If a user is added to the site collection through a group, its flag is not necessarily active.

 

First, if the user is added through the AD group, the user will be set to active only when he has a contritrion a document or resource on the site. if the user is added to the AD group, but he has not added or modified any content on the site set, his profile will not be synchronized. when this AD group has only the read permission, this user will not be synchronized in this group.

 

If a user is added through a SharePoint group, it will always be synchronized. if he is in an AD group and is authorized to include this AD group in a SharePoint group, his profile will not be synchronized. if a SharePoint group contains an AD group, the user in the Ad Group will not be synced unless the user adds or modifies something to the site.

 

Q: Will all attributes be synchronized between site sets?

A:

No. only Replicable attributes are identified. view the location of this flag. On the SSP-> User profiles and properties-> View profile properties page, click an attribute and edit it. In the Policy Settings section, there is a check box called replicable.

In general, replicable attributes include Name, Work e-mail, Responsibilities, About me, Photo, Office Single Value, Title, Work phone, Last name, First name, Department, User name, web site, SIP Address, etc.

Some replicable attributes can be mapped to the attributes of AD. Therefore, any modifications to these attributes will be overwritten during the next synchronization from AD.

 

Q: What is the timer job responsible for Profile Sync? What is the difference?

A:

Two timer jobs are responsible for profile synchronization.

 

First, it is called Quick Profile Sync Job. it is responsible for adding new users to Site Collections. when a user is marked as Active on a Site set for the first time, the Quick Profile Job synchronizes the user's profile information to the Site Collection. in the server farm, the job runs once every minute.

 

The second one is called Profile Sync Job. it synchronously updates the user information that has been added to the site. for example, in a site set, a user is marked as Active, and his profile is also entered. later, the user's profile information is updated (for example, the phone number, email address, or something ). profile Sync Job is responsible for this update at the site set level. by default, this Job runs hourly. when a user modifies his profile information (either through AD or through MySite), the information stored in SSP is first modified every hour, this job runs once and is updated on each Active site set.

 

Q: each site set has its own user profile information. Is this redundant?

A:

Yes. however, this is done to improve performance. the total data is stored in SSP. If there is no redundancy, all requests for user profile information will be stored in an SSP database. in this way, the profile data is distributed to the respective site collection, which can reduce the pressure on a single database for profile requests.

 

Q: Why do I have to mark Sync as Active?

A:

This is also the reason for performance. If all the domain accounts are synchronized, if there are a few more users in the domain, there will be tens of thousands of users, and the performance overhead will be huge.

 

Q: If something goes wrong, some accounts cannot sync their information. What should I do?

A:

Once you understand the Active status, you can first check in the database whether the tp_isActive in the record of the user on a site set is true. if not, you can try to grant this user the contribute or above permission to modify something in the site set. wait an hour. or, Actions-> Site Settings-> People and Groups-> All People group, remove the user and add it back. Remember, the permission must be contribute or later.

 

If you find that the profile information of a user is not synchronized only on a site collection, it may be because the site set is in the ready to move status. Once the site set is in this status, some functions cannot be run any more, and profile synchronization is one of them.

 

You can try to run the following query in SQL

use SharedServices1_DBgoselect ContentDBID, SiteID, Moving from sitesynch (nolock) where Moving=1-----------------------------Assume we got a result entry, --  which contentdbid is 9B6AC78F-BFB9-4976-8D98-70EAE30F0862, --   and siteid is B658959B-CB67-45BC-8F40-BD8AD4B805DD---------------------------use SharePoint_Configgoselect Name, Id from Objects where Id like '9B6AC78F-BFB9-4976-8D98-70EAE30F0862'select Path, Id from SiteMap where Id like 'B658959B-CB67-45BC-8F40-BD8AD4B805DD'

Through these queries, you can locate the name of the content database and the path of the site set.

Then, run the following command to set the moving flag to 0.

Stsadm-o preparetomove-site <SiteCollectionURL>-undo

 

Why is there a moving status? This is because we do not want any changes to this site set when we move the site set. After the move is over, we forget to change it back, and the profile cannot be synchronized.

 

If the preceding step does not work, you must use the following command.

Stsadm-o sync deleteolddatabases 0

This command deletes records of content db that do not currently have synch. This will force SSP to Re-sync these content databases. (SharePoint Profile Import)

Another point is that if the site status changes to unprovisioned, the user profile of the site will not be synchronized.

How can I determine whether the status of a site is unprovisionde? If so, how can we change it back?

Run the following query on the Content Database. The UnProvisioned column in The result set is in the unprovisioned state.

select id, title, fullurl, cast((Flags & 0x100) as bit) as UnProvisioned from Webs

 

The solution is to run a stored procedure named proc_markWebAsProvisioned. pass the id from the previous step as a parameter to the stored procedure. paste the source code of the SharePoint stored procedure here for your convenience.

SET ANSI_NULLS ONGOSET QUOTED_IDENTIFIER ONGOALTER PROC [dbo].[proc_markWebAsProvisioned](    @WebId uniqueidentifier)AS    SET NOCOUNT ON    UPDATE         Webs    SET        Flags = ~(0x100 | ~Flags)    WHERE        Id = @WebId

 

References:

Syncing WSS and MOSS User profile properties with Active Directory

Http://sharepointnotes.wordpress.com/2008/05/05/syncing-wss-and-moss-user-profile-properties-with-active-directory/

MOSS User Profiles not syncing with Site User Info

Http://www.portalsolutions.net/Blog/Lists/Posts/Post.aspx? List = 1fef67f0-70ca-4263-b683-f10c1958687a & ID = 35 & Web = 2a4e9897-6530-44a1-80b5-4fac295c2c26