RE: WSS's "Select People and Groups" dialog box not working as expected

Tech-Archive recommends: Fix windows errors by optimizing your registry

{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\lang2052\f0\fs20 Hi Edurado,
\par
\par Have you got any progress on this issue or does the information in last reply help yo some?
\par
\par Sincerely,
\par
\par Steven Cheng
\par
\par Microsoft MSDN Online Support Lead
\par
\par
\par Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
\par
\par \pard\li720 --------------------
\par From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng [MSFT])
\par Organization: Microsoft
\par Date: Fri, 05 Sep 2008 07:43:22 GMT
\par Subject: RE: WSS's "Select People and Groups" dialog box not working as expected
\par
\par
\par Hi Eduardo,
\par
\par Regarding on the user picker part behavior. I think it is due to the slow request/response time for the AJAX auto-complete feature. When the deployment domain has so many objects, the responding time of the AJAX auto-prompt feature also suffer a slow performance issue.
\par
\par Here I've found a blog entry from the dev engineer which provide some detailed configuration and setting feature on the picker part.
\par
\par #Multi Forest/Cross Forest People Picker peoplepicker-searchadcustomquery
\par http://blogs.msdn.com/joelo/archive/2007/01/18/multi-forest-cross-forest-people-picker-peoplepicker-searchadcustomquery.aspx
\par
\par You can try disabled some of the option to see whether it helps some. Or there is a custom query feature available, you can also try using a custom query expression.
\par
\par Sincerely,
\par
\par Steven Cheng
\par
\par Microsoft MSDN Online Support Lead
\par
\par
\par Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
\par
\par ==================================================
\par Get notification to my posts through email? Please refer to http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.
\par
\par Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support
\par Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support
\par professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations
\par that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://support.microsoft.com/select/default.aspx?target=assistance&ln=en-us.
\par ==================================================
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par \pard\li1440 --------------------
\par From: "Eduardo Lopez" <EduardoLopez@xxxxxxxxxxxxxxxx>
\par Subject: WSS's "Select People and Groups" dialog box not working as expected
\par Date: Thu, 4 Sep 2008 13:51:04 -0700
\par
\par
\par Hi WSS community,
\par I have being trying to figure out how the picker.aspx page works, and it
\par looks like is getting all users from the ActiveDirectory where the WSS farm
\par is deployed. That's good, but, for some reason, is not working as expected
\par in my environment with approximately 5000 objects in the directory. Let me
\par give you more details:
\par
\par If I open up pickup.aspx by clicking the Browse icon in the Add users web
\par form, I will get the pickup form that we are talking about, then if I enter
\par more than two letters, say something like "lo" it will sit there and do
\par nothing, just waiting, on the other hand, if I enter only one letter, say
\par something like "l" it will bring immediately a bunch of users where the
\par letter "l" is in any part of their displayName attribute. That's the default
\par behavior that I'm getting.
\par
\par So far I was able to make it behave as I want, but with limited results, let
\par me explain, I updated the "peoplepicker-onlysearchwithinsitecollection"
\par property to 'yes' with the setproperty operation of the stsadm command line
\par tool, then I went back to the lookup form to type lopez and I got my
\par account, which is good, however, I was not getting all lopez accounts only
\par the members of the site where I was opening the lookup form, in this case
\par only my account. I updated again the same property to 'no' and I went back
\par to the same old behavior.
\par
\par What I want to do is to make it work as a real lookup form, for example, if
\par I enter lopez then I should get all lopez users, even if they aren't members
\par of any given WSS site.
\par
\par I have a medium farm, three servers: front end web server, app/search
\par express/job server and the db server, the first two running WSS SP1 and the
\par db server running SQL Server 2005.
\par
\par I'll appreciate any help that can be provided.
\par
\par Regards,
\par - Eduardo Lopez
\par
\par \pard\li720
\par
\par \pard
\par
\par }

Relevant Pages

  • RE: WSSs "Select People and Groups" dialog box not working as expected
    ... \par looks like is getting all users from the ActiveDirectory where the WSS farm ... \par account, which is good, however, I was not getting all lopez accounts only ... \par the members of the site where I was opening the lookup form, ... \par express/job server and the db server, the first two running WSS SP1 and the ...
    (microsoft.public.sharepoint.windowsservices)
  • WSSs "Select People and Groups" dialog box not working as expected
    ... I have being trying to figure out how the picker.aspx page works, and it looks like is getting all users from the ActiveDirectory where the WSS farm is deployed. ... So far I was able to make it behave as I want, but with limited results, let me explain, I updated the "peoplepicker-onlysearchwithinsitecollection" property to 'yes' with the setproperty operation of the stsadm command line tool, then I went back to the lookup form to type lopez and I got my account, which is good, however, I was not getting all lopez accounts only the members of the site where I was opening the lookup form, in this case only my account. ... I have a medium farm, three servers: front end web server, app/search express/job server and the db server, the first two running WSS SP1 and the db server running SQL Server 2005. ...
    (microsoft.public.sharepoint.windowsservices)