Prev: Is Exchange required to enable Email to Libraries?
Next: System.Runtime.InteropServices.COMException (0xC004122D): Could not access the Search service configuration database
From: Owen Lamb on 9 Apr 2007 11:36
Presumably you have your web application setup in host header mode. If so,
you can use the STSADM tool to limit each site collection to only view users
from their own collection by executing the following command:

"C:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\12\BIN\stsadm.exe" -o setproperty -pn
peoplepicker-onlysearchwithinsitecollection -pv yes -url
http://sitename.host-header-name.com

Where sitename is the website, and host-header-name.com is the host header
application name.

The only limitation, which I'm currently researching, is that you can still
find local service accounts, such as the account to run the web application
and search service.

"bharwood(a)goiwx.com" wrote:

> I have successfully installed wss 3.0 on win2k3serv and set up a
> couple test
> sites for two SEPERATE test/user/companies. I noticed that when i am
> logged
> into the respected sharepoint sites and i attempt to add a user, my
> complete Active
> Directory is exposed when i use the "look up" feature. How do i
> prevent users
> from test site (A) from viewing AD entries of test site (B) and vice
> versa when adding users?
>
>
 | 
Pages: 1
Prev: Is Exchange required to enable Email to Libraries?
Next: System.Runtime.InteropServices.COMException (0xC004122D): Could not access the Search service configuration database