SharePoint: Deep Diving with Cross Forest, Multi Forest Configuration and Additional Info
/* Posted January 22nd, 2009 at 10:00am *//* Filed under C#, Microsoft, SharePoint */
/* */
Deep Diving with Cross Forest, Multi Forest Configuration and Additional Info
From Joel Oleson’s Blog URL: http://blogs.msdn.com/joelo/archive/2007/03/08/cross-forest-multi-forest-configuration-additional-info.aspx:
Background
The people picker works in cross domain or cross forest environment. It works in both-way trust and one-way trust environment.
Out of the box, if the admin does not do any configuration, the people picker will issue queries to all two-way trusted domains and two-way trusted forests to search people & groups.
The people picker uses the application pool account to search the target domains and forests. If the application pool account does not have permission to the target domains or forests, or the admin want to use different account to search the target domains or forests, the admin could should use
How to Configure
Don’t forget to run stsadm.exe –o setapppassword –password
1. Run on every WFE.
stsadm.exe -o setapppassword -password
2. Run on one WFE
stsadm.exe -o setproperty -url ...
What we have found:
Example of command:
stsadm.exe -o setproperty -url “http://MYSHAREPOINTSITE:21212″ -pn “peoplepicker-searchadforests” -pv “domain:mydomain.something.com,USERNAME,PASSWORD”
1. http://MYSHAREPOINTSITE:21212 = Your sharepoint site URL
2. mydomain.something.com = your domain, you can also use forest:BLAHBLAH
3. USERNAME = your username you want to use to connect to the domain/forest
4. PASSWORD = Password for the username you want to use to connect to the domain/forest
Errors you May Encounter:
Error 1:
Command line error.
Usage:
stsadm.exe -o
Solution:
Make sure you use quotes around peoplepicker-searchforests…. in the example text we use quotes around everything.
Example = -pn “peoplepicker-searchadforests”
Error 2:
The Web application at http://MYSHAREPOINTSITE:21212 could not be found. Verify
that you have typed the URL correctly. If the URL should be serving existing co
ntent, the system administrator may need to add a new request URL mapping to the
intended application.
Solution:
1. Try to login as a master account then run the command again (recommended)
2. If the above solution fails, you may need to extend the web app, then run the setproperty command on the new web app.
Error:
Cannot connect to SQL Server. SQLSERVERNAME not found. Additional error information from SQL Server is included below.
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
Solution:
Make sure you are RDP’ed in with an account that has windows access to SQL Server

















comment6, Now no credit check student loans, [url=http://www.maclife.com/user/nocreditcheckstudentloans]Now no credit check student loans[/url], 10749, high risk personal loans, [url=http://www.maclife.com/user/highriskpersonalloans]high risk personal loans[/url], 8-DDD, I like this colin farrell sex tape, [url=http://www.maclife.com/user/colinfarrellsextape]I like this colin farrell sex tape[/url], =))), Buy military loans, [url=http://www.maclife.com/user/militaryloans]Buy military loans[/url], :], Bad Credit Student Loans – Best Decisions, [url=http://www.maclife.com/user/badcreditstudentloans]Bad Credit Student Loans – Best Decisions[/url], 729472,