WSS 3.0 - Site collection users can see all other users?http://forums.asp.net/t/1111288.aspx/1?WSS+3+0+Site+collection+users+can+see+all+other+users+Mon, 08 Dec 2008 14:08:35 -050011112881711748http://forums.asp.net/p/1111288/1711748.aspx/1?WSS+3+0+Site+collection+users+can+see+all+other+users+WSS 3.0 - Site collection users can see all other users? <p>I really hope I messed up somewhere.&nbsp; Using the Sample Provisioning UI, I created a basic sharepoint site for a test organization.&nbsp; I am not using host headers and prefer to use each company with their own subfolder below root.</p> <p>&nbsp;For example:<br> <a href="http://collab01/sites/CompanyA">http://collab01/sites/CompanyA</a><br> <a href="http://collab01/Sites/CompanyB">http://collab01/Sites/CompanyB</a></p> <p>I then logged in directly to the website collab01/sites/CompanyA, went to site actions/site settings and under Users &amp; Permissions clicked 'People and groups'.&nbsp; I selected New to add&nbsp;a new user and I then clicked on the address book to search for users.&nbsp; I have two users in different organizations with the same first name.&nbsp; I searched for the first name, and it showed me <strong>both </strong>users!</p> <p>I assume this is incorrect sharepoint hosting action - does anybody know what I missed? Can I not do the above folder structure? How should I do it then?</p> <p>Thanks for all your help guys, first time trying to get hosting up &amp; running!</p> 2007-05-16T19:02:44-04:001784773http://forums.asp.net/p/1111288/1784773.aspx/1?Re+WSS+3+0+Site+collection+users+can+see+all+other+users+Re: WSS 3.0 - Site collection users can see all other users? <p>Hi,</p> <p>I have the same problems but i'm using Web Applications. Each Portal site hase its own hostheader (the website port is default random)<br> I have found a sollution but this is only a workaround. Is it possible to set security on the portal site making use of the group membership. So, user Bill is member of CompanyX. Bill may only search for the users who are member of CompanyX and he may NOT see the users of CompanyY or CompanyZ. We want to use SharePoint 2007 for more companies.</p> <p>My temporary sollution for this&nbsp;is to&nbsp;use the stsadm.exe tool and execute&nbsp;this command in the cmd:</p> <p>stsadm -o setproperty url http://yourportalsite pn &quot;peoplepicker-onlysearchwithinsitecollection&quot; pv yes</p> <p>What this command does is it will denie any search within your portal site. You can only search for members that are allready member of the Site Collection.<br> <br> stsadm.exe is in: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN</p> <p>Kind Regards,<br> John</p> 2007-07-03T13:15:53-04:001855975http://forums.asp.net/p/1111288/1855975.aspx/1?Re+WSS+3+0+Site+collection+users+can+see+all+other+users+Re: WSS 3.0 - Site collection users can see all other users? <p>Thanks very much John, this seems to be a great workaround for us!</p> 2007-08-13T22:17:07-04:002649172http://forums.asp.net/p/1111288/2649172.aspx/1?Re+WSS+3+0+Site+collection+users+can+see+all+other+users+Re: WSS 3.0 - Site collection users can see all other users? <p>Hi, I have a question.&nbsp; </p> <p>in the way you imlemented each company as separeted site collection.&nbsp; can you apply a unique DNS for each company?&nbsp;&nbsp; for example, <a href="http://companya.inf/">http://companyA.inf/</a>&nbsp;for company A.&nbsp; if you did, can you share how did you configured?</p> <p>thanks</p> 2008-09-26T20:14:56-04:002793176http://forums.asp.net/p/1111288/2793176.aspx/1?Re+WSS+3+0+Site+collection+users+can+see+all+other+users+Re: WSS 3.0 - Site collection users can see all other users? <p>Yes, this is possible.</p> <p>You could use the option&nbsp;Alternate Access Mappings and assign DNS names for each site. For example: ad <a href="http://intranet.companyxyz.com/">http://intranet.companyXYZ.com</a> as an AAC in SharePoint. Do the same for the other Application Pools. (your Site Collections are inside these AP's)<br> In DNS you need to add for each host intranet.companyXYZ.com in the companyXYZ.com Forward Lookup Zone.</p> <p>&nbsp;This should be the sollution for your problem.</p> 2008-12-08T14:08:35-05:00