Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

SPS2003 Profile Nightmare

  Asked By: Damaris    Date: May 07    Category: Sharepoint    Views: 636

Does anyone have a script or mechanism to report on all the profiles
stored in SPS2003? Our AD user objects that have been deleted over time
still show up in SharePoint. I would like to audit them and remove them
if at all possible. I guess I first need a list of the profiles that
exist. Also I see many errors in the gatherer logs for the profile
import that reference the accounts that are missing from AD it is trying
to sync. Is this log available to me outside of the sps obj model?

Any insight on how anyone has accomplished this is welcomed..

Share: 

 

3 Answers Found

 
Answer #1    Answered By: Caleb Gordon     Answered On: May 07

I would be interested as well. Whoever does a web part for this would
make a killing. This is definitely a nightmare. Does anyone know if this
has been corrected in MOSS 2007, out of the box?

 
Answer #2    Answered By: Irving Hurley     Answered On: May 07

yes, a webpart or even a 3rd party slide-on application to manage this.

I would love a big button to click simply labled "true-up" that would
remove all "orphaned" profiles, associated mysites, and possibly the
disjointed wss site collection acl entries for all my bastardized user
profiles. This would be of such value.

I can't imagine however, that there are'nt admins/devs out there who
have dealt with this in some ingenious way over the lifespan of the
product.

Anyone else ever deal with this issue before?

 
Answer #3    Answered By: Tiana Whitaker     Answered On: May 07

I reserve the right to be completely wrong in my recollection of this
problem But hope this will help in understanding.

When a profile  crawl occurs, 3 consecutive "Full" crawls have to occur
before the profile is "Marked for delete". If any incremental crawl
occurs, it resets the counter, and the profile will not be marked for
deletion until 3 consecutive "full" crawls.

At that point, you still have to go into Manage Profiles, and manually
purge those profiles  (Don't have a SPS2003 server up and running right
this moment to help me recollect)

I believe some improvements were definitely made to this for MOSS, but
don't have a clear enough understanding at this point to let you know if
the story is better or not.

Always keep in mind, that for SPS2003, Profiles and Web Security were
two completely different things.

A Site Collection records unique security information about a user, and
each site collection contains a separate record in the UserInfo table
about that user, per site collection.

This information has nothing to do with the Profile.

So in the case of a MySite, the MySite (a root web in a site collection)
has unique information about user  A.

User A may also have a profile record that was either a) imported from
AD, or b) created when the user clicked on the "MySite" link in the
portal. Regardless of which method the profile was created, it simply
has a URL field in it that redirects people to their MySite link (Or
rather, any URL that may be set to redirect users to their "Personal"
web site...it doesn't have to be a SharePoint MySite). But this is the
only association to the SharePoint mysite.

You are correct though, that if say a user is deleted, there are many
things you have to do to clear that users "Existence" out of the portal
such as (but not necessarily limited to)

1) Removing the users unique security information from all site
collections in the farm

2) Deleting their MySite if one exists

3) Deleting their Profile record if one exists.

I had some features in SPSUserUtil to help with this matter, but can't
remember how extensive it was, and most of the Profile/MySite fixup
stuff was for the "Clone" operation, and not "Delete" operation.

 
Didn't find what you were looking for? Find more on SPS2003 Profile Nightmare Or get search suggestion and latest updates.




Tagged: