People picker is unable to resolve users in a trusted forest if the only domain controller SharePoint can access is read-only.
The idea is that all read requests go to the local read-only DC, but if there are write requests (which should be fewer) those get redirected by the local DC to the remote (slower) read-write DC. So there shouldn’t be a case where you have access to a read-only DC and NO access to a r/w DC. So being completely unable to access a read/write domain controller would be an invalid configuration.
SharePoint will need access to a read/write domain controller in the trusted domain or forest
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
Artikel-id: 970612 - Laatst bijgewerkt: 20 jun. 2013 - Revisie: 1