People picker still showing users from old trusted domain
So we had a 2 way trust with another domain that we took out, and for awhile the users in the trusted domain seemed to be gone when looking up users, but now for who knows how long they are back. When I search for myself or someone that had an account in
the old domain it shows up in people picker. The domain is gone along with the servers. How can we be seeing these old domain users if the domain is gone and trust doesn't exist? If I try to add one of these users I get an error stating "The user does not
exist or is not unique."
I tried a custom filter to try and remove those accounts which have an old email but that doesn't work either:
stsadm -o setproperty -pn peoplepicker-search adcustomquery -pv (&(sn={0}*)(!mail=*irwin*)) -url
http://urllink
Error that I get: (!mail was unexpected at this time.
Any ideas on this??? Why would we still see these users?
Thanks,
Dustin
August 30th, 2011 5:05pm
Hi,
have you tried to reset catalog and start a new profile import ?FabioA
Free Windows Admin Tool Kit Click here and download it now
August 31st, 2011 5:51am
I have not tried that. How do you reset the catalog and how would that reset the people picker search? I do not see any of these users in the profile search when I look at the imported users.
Thanks.
August 31st, 2011 3:03pm
Hi Iceman,
You can refer to
this, hope it
helps.
Thanks,
Pengyu Zhao
Free Windows Admin Tool Kit Click here and download it now
September 1st, 2011 11:49pm
Hi Iceman,
This may caused by the SID being used to tattoo the resource within SharePoint.
You can refer to
this, hope it
helps.
Thanks,
Pengyu Zhao
September 2nd, 2011 6:30am
Hi Iceman,
This may caused by the SID being used to tattoo the resource within SharePoint.
You can refer to
this, hope it
helps.
Thanks,
Pengyu Zhao
Free Windows Admin Tool Kit Click here and download it now
September 2nd, 2011 6:30am
Hi Iceman,
This may caused by the SID being used to tattoo the resource within SharePoint.
You can refer to
this, hope it
helps.
Thanks,
Pengyu Zhao
Hmm.... How did SharePoint save these SIDs if we never imported the user objects from the other domain? I know for a fact we didn't add most of these users to any of the sites so they can't be local. (I know this because I was the only admin
that modified permissions for sites) Does SP capture the SIDs on a previous people picker search in AD and store them somewhere?
How do I go about fixing these if the domain doesn't exist anymore?
September 7th, 2011 4:25pm
Hi Iceman,
This may caused by the SID being used to tattoo the resource within SharePoint.
You can refer to
this, hope it
helps.
Thanks,
Pengyu Zhao
Hmm.... How did SharePoint save these SIDs if we never imported the user objects from the other domain? I know for a fact we didn't add most of these users to any of the sites so they can't be local. (I know this because I was the only admin
that modified permissions for sites) Does SP capture the SIDs on a previous people picker search in AD and store them somewhere?
How do I go about fixing these if the domain doesn't exist anymore?
Free Windows Admin Tool Kit Click here and download it now
September 7th, 2011 4:25pm