I really hope I messed up somewhere. Using the Sample Provisioning UI, I created a basic sharepoint site for a test organization. I am not using host headers and prefer to use each company with their own subfolder below root.
I then logged in directly to the website collab01/sites/CompanyA, went to site actions/site settings and under Users & Permissions clicked 'People and groups'. I selected New to add a new user and I then clicked on the address book to search for users.
I have two users in different organizations with the same first name. I searched for the first name, and it showed me
both users!
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?
Thanks for all your help guys, first time trying to get hosting up & running!
I have the same problems but i'm using Web Applications. Each Portal site hase its own hostheader (the website port is default random)
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.
My temporary sollution for this is to use the stsadm.exe tool and execute this command in the cmd:
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.
stsadm.exe is in: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN
in the way you imlemented each company as separeted site collection. can you apply a unique DNS for each company? for example,
http://companyA.inf/ for company A. if you did, can you share how did you configured?
You could use the option Alternate Access Mappings and assign DNS names for each site. For example: ad
http://intranet.companyXYZ.com as an AAC in SharePoint. Do the same for the other Application Pools. (your Site Collections are inside these AP's)
In DNS you need to add for each host intranet.companyXYZ.com in the companyXYZ.com Forward Lookup Zone.
paulsilverst...
Member
101 Points
96 Posts
WSS 3.0 - Site collection users can see all other users?
May 16, 2007 07:02 PM|LINK
I really hope I messed up somewhere. Using the Sample Provisioning UI, I created a basic sharepoint site for a test organization. I am not using host headers and prefer to use each company with their own subfolder below root.
For example:
http://collab01/sites/CompanyA
http://collab01/Sites/CompanyB
I then logged in directly to the website collab01/sites/CompanyA, went to site actions/site settings and under Users & Permissions clicked 'People and groups'. I selected New to add a new user and I then clicked on the address book to search for users. I have two users in different organizations with the same first name. I searched for the first name, and it showed me both users!
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?
Thanks for all your help guys, first time trying to get hosting up & running!
johnwoo
Member
4 Points
2 Posts
Re: WSS 3.0 - Site collection users can see all other users?
Jul 03, 2007 01:15 PM|LINK
Hi,
I have the same problems but i'm using Web Applications. Each Portal site hase its own hostheader (the website port is default random)
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.
My temporary sollution for this is to use the stsadm.exe tool and execute this command in the cmd:
stsadm -o setproperty –url http://yourportalsite –pn "peoplepicker-onlysearchwithinsitecollection" –pv yes
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.
stsadm.exe is in: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN
Kind Regards,
John
Microsoft Office SharePoint Server MOSS SharePoint
paulsilverst...
Member
101 Points
96 Posts
Re: WSS 3.0 - Site collection users can see all other users?
Aug 13, 2007 10:17 PM|LINK
Thanks very much John, this seems to be a great workaround for us!
ray1135
Member
2 Points
1 Post
Re: WSS 3.0 - Site collection users can see all other users?
Sep 26, 2008 08:14 PM|LINK
Hi, I have a question.
in the way you imlemented each company as separeted site collection. can you apply a unique DNS for each company? for example, http://companyA.inf/ for company A. if you did, can you share how did you configured?
thanks
johnwoo
Member
4 Points
2 Posts
Re: WSS 3.0 - Site collection users can see all other users?
Dec 08, 2008 02:08 PM|LINK
Yes, this is possible.
You could use the option Alternate Access Mappings and assign DNS names for each site. For example: ad http://intranet.companyXYZ.com as an AAC in SharePoint. Do the same for the other Application Pools. (your Site Collections are inside these AP's)
In DNS you need to add for each host intranet.companyXYZ.com in the companyXYZ.com Forward Lookup Zone.
This should be the sollution for your problem.
Alternate Access Mapping Application Pool DNS