MOSS People Picker cannot search AD users from other domains

Online project management, task software, and free collaboration workspace: AJAXWorkspace
AJAXWorkspace is a free online workspace that offers task tracking software, team collaboration, online calendar, document sharing, and file management for project management and teamwork.

This post is contributed by my colleague, Abi. I would like to share out here since it is very usefully.

If you have MOSS users in different AD domains, and for dunno wat reason you can’t seem to search these users in the MOSS’s PeoplePicker, run a stsadm command to add the information about the those domains where the user is located.

In summary:
“We went to SSP and clicked on User Profiles and Properties under the “User Profiles and My Sites” section and then clicked on View Import Connections and then added domain1.company.com to the Import Connections list and I started a full import. It completed in about an hour and imported users from the domain1 domain.

The problem we run into is that when I go to add them to a site to give them access, we are unable to find the users by using People Picker. We only find users from the domain0 domain which the moss server is on. ”

I found out that by default People Picker can only find people in the resource domain - the domain that MOSS servers are in. For other domains/forests, you’ll need to run the following command:

Stsadm.exe –o setproperty –pn peoplepicker-searchadforests –pv <list of forests or domains> -url <webapp>

Official MS site:

Some examples:

Posted in SharePoint.

2 Responses to “MOSS People Picker cannot search AD users from other domains”

  1. MOSS People Picker cannot search AD users from other domains « yyTech Blog on .Net, SQL, SharePoint, Collaboration and tech tips. Says:

    [...] Read the rest of this entry (moved to http://www.bronios.com) » Posted in SharePoint. Tags: People Picker, SharePoint. [...]

  2. Adil Says:

    I have this problem of people picker. this is the prob in brief:

    we initially had single server deployment with 8 web app on WSS 3.0.
    due to load, we now moved them to a new farm with 3 servers with following configuration:
    1. all having wss 3.0 SP1
    2. all patched with search server express 2008
    3. search and query bieng served by server3

    also not worthy here is that due to budget constraint and stuff, we dint had load balancing so we are doing context switchin with
    4 app on server1 and 4 app on server2..
    each of this app is turned off in IIS in other server and each app has own IP and DNS.
    so the NIC of each server has 4 IPs

    backup restore happened like a charm. the expected context swithcing happens like a charm. but now people picker goes in infinite “query bieng processed” and never fetches anything

    this problem has become a red flag as this the 4th day and i could find nothing that worked.

Leave a Reply