Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

When utilizing Active Directory connections across multiple domains (with a two-way trust), is it possible to have resolution (during sync) of the Manager field when the Manager exists in another domain?

Working with the following example users:

  • DOMAINA\Manager1
  • DOMAINB\Manager1
  • DOMAINB\User1

If the Manager for DOMAINB\User1 within AD is set to DOMAINB\Manager1, resolution within the user profile occurs without issue. If the Manager is set to DOMAINA\Manager1, resolution does not occur and the Manager field does not appear within the user profile.

share|improve this question

3 Answers 3

Yes, FIM works with two-way trusts... I suspect this is a configuration or a permissions problem.

Do you have user profile sync connections setup to synch users from both domains? Have you given your user profile synch account the correct read permissions on both domains?

share|improve this answer
    
The UPS account does have proper permissions across all of the domains. There are individual synchronization connections for each domain as well. Each synchronization connection also has a connection filter to remove disabled user accounts (Bit on equals 2). –  ciphertxt Jun 17 '11 at 15:10
    
Acquiring accounts from the individual domains is not any issue. The issue is resolving managers across domains. –  ciphertxt Jun 17 '11 at 15:11
up vote 0 down vote accepted

The lack of manager resolution across domains was due to the use of multiple synchronization connections. When using 1 synchronization connection for the forest, resolution occurred without issue.

share|improve this answer

Make sure that you have enabled netbios names. That was one of the issues I came across when configuring multiple domains and users from other domains being the managers. Doing the following via a powershell did the trick, but unfortunately you have to remove all Synchronization connections after running the script and re-create them to make the setting effective.

NB: Get-SPServiceApplication gives you all the applications and you can use that to get the GUID of User Profile Service Application

$var = Get-SPServiceApplication –Identity {Application GUID}
$var.NetBiosDomainNamesEnabled
$var.NetBiosDomainNamesEnabled = “True”
$var.update()
$var.NetBiosDomainNamesEnabled
share|improve this answer
    
This appears to resolve the issue with parent-child domain manager resolution within the farm. However, child-child domain resolution is still not working. With 3 domains A (Parent), B (Child), and C (Child), users in domain B with managers in domain A resolve successfully. Users in domain B in managers in domain C do not resolve. –  ciphertxt Jul 11 '11 at 13:27

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.