Performance Issue with People Picker
Hello, We have a "Task" list and we configured the PeoplePicker for the "AssignedTo" field. We wanted the PeoplePicker to search from one of the groups on the site e.g. SiteUsers group. But since the group contains large number of users approximately more than 15,000 users, the PeoplePicker "Select People and Groups" dialog is taking 5-6 minutes to load. This is because the PeoplePicker displays all the 15K userson the initial load.Can we configure PeoplePicker to display only a few users on initial load?ORCan we confiure it to display no user at all initially?ORAny other suggestions?Thanks,Irtaiza
February 9th, 2009 1:56pm

This article talk about "Limiting the SharePoint People Picker"http://www.synergyonline.com/blog/blog-moss/Lists/Posts/Post.aspx?ID=5 or can userestrict AD users to be added in your entire site collectionstsadm -o setproperty -url [URL] -pn peoplepicker-nowindowsaccountsfornonwindowsauthenticationmode -pv yesConfigure your site colletion to group of users you want...Dont know if this can help...Andr Lage Microsoft SharePoint and CRM Consultant http://aaclage.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
February 9th, 2009 4:33pm

Thanks Andre,But that does not solve our problem. Since there is an issue with setting the "searchwithinsitecollection" that an AD user can be searched using the "Check Names" functionality.http://social.technet.microsoft.com/Forums/en-US/sharepointsearch/thread/16d10442-38e0-4c77-8bd7-30b46270dc10/The other option is also not feasible since all our users will be AD users only and we will be using windows authentication only.Any more inputs?Regards,Irtaiza
February 11th, 2009 2:57pm

Hi Irtaiza, How many domains and DCs do you have in your organization? If you have several domains and have made them two-way trusted. Please try the command line below to set the scope in which you want the people picker to search. stsadm.exe -o setproperty -url <http://server:port> -pn "peoplepicker-searchadforests" -pv "domain:domain1;domain:domain2;domain:domain3; domain:domain4" If this cannot solve the problem, you may need to use the netmon to catch the log on SharePoint Server. It can help confirm if this problem is caused by the query on LDAP. Sometimes the query from a certain DC will cost a long time. Microsoft Network Monitor 3.2 http://www.microsoft.com/DOWNLOADS/details.aspx?FamilyID=f4db40af-1e08-4a21-a26b-ec2f4dc4190d&displaylang=en Hope it will help Lu Zou
Free Windows Admin Tool Kit Click here and download it now
February 13th, 2009 11:21am

What if the query on LDAP is the cause of a problem. How can we rectify the issue? Is there anything we need to on the DC to speed up?
May 12th, 2010 6:39pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics