Answered by:
2007: Issue with servers in different domain than users

Question
-
Hi,
When setting up Project Server 2007 SP2 sometime ago, we installed both WSS and Project Server onto one server in Domain A. The SQL Server that we connect to is also in Domain A as well as the service account we used for the installation.
We have provisioned a PWA instance using the same account we used for the installation. Our total of 200+ Project Server users all have accounts in Domain B. Up to this day we haven't had any issues with authentication or anything. All the users from Domain B can access both the PWA sites as well as the SharePoint Project Workspaces without any problems.
A few days back we created a new Site Collection in a new Content DB on the very same environment. The customer wanted to start using SharePoint for broader collaboration than what is currently used within Project Server. Now we face the issue that we cannot add any users to the new Site Collection or any of its subsites. Whenever we try to add any user through the people picker, it won't find any of the users in Domain B -- something that continues to work just fine whenever we create new Project Workspaces in the other Site Collection.
Has anyone of you seen this before? Do we need to configure anything in particular to make this scenario work? Also, I would appreciate any links to TechNet articles or similar on this topic as I wasn't able to find anything as of today.
Thanks for your help!
Marc
Monday, March 14, 2011 3:59 PM
Answers
-
Hi,
It sounds like the PeoplePicker is not looking at Domain B, there are a few STSADM commands that you may wish to investigate that enable you to scope the ad groups / domains the people picker will use http://technet.microsoft.com/en-us/library/cc263460(office.12).aspx
Hope this helps,
Alex Burton
www.epmsource.com | Twitter
Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page- Proposed as answer by Christophe FiessingerMicrosoft employee Tuesday, March 15, 2011 2:42 PM
- Marked as answer by Gary Chefetz, MCITP, MCT, MVP Thursday, May 19, 2011 9:57 AM
Tuesday, March 15, 2011 11:00 AM
All replies
-
Hi Marc,
Are you getting any error in ULS Logs or Application Event Logs?
Did you check with AD team to further discuss this issue as you are not able to find out any users in Domain B through the people picker in New Site Collection?
Warm Regards Badal RatraTuesday, March 15, 2011 6:40 AM -
Hi,
It sounds like the PeoplePicker is not looking at Domain B, there are a few STSADM commands that you may wish to investigate that enable you to scope the ad groups / domains the people picker will use http://technet.microsoft.com/en-us/library/cc263460(office.12).aspx
Hope this helps,
Alex Burton
www.epmsource.com | Twitter
Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page- Proposed as answer by Christophe FiessingerMicrosoft employee Tuesday, March 15, 2011 2:42 PM
- Marked as answer by Gary Chefetz, MCITP, MCT, MVP Thursday, May 19, 2011 9:57 AM
Tuesday, March 15, 2011 11:00 AM -
Thanks guys. I'm currently reading through the articles you've posted around stsadm peoplepicker etc. and will post any progress here.
In parallel, I'm trying to get a better understanding of the domain and forest architectures that they have in place.
Wednesday, March 16, 2011 9:10 AM