SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are facing an issue with Audience and the senario follows.

  1. We have two Domains namely Domain_One and Domain_Two in the same forest.
  2. Both are Trusting each other.
  3. Both the domain has its own set of users (Direct OU structue & Not a nested OU structure).
  4. The Domain Local Security Group "Dev-X" is in Domain_One.
  5. Few users from both the domains are member of "Dev-X", say 50users (30domainone users + 20domaintwousers).
  6. SharePoint Applications are hosted in Domain_one.
  7. SSP is hosted in Domain_one.
  8. We have an audience in SSP & it is controlled by the rule "Memberof -> 'Dev-X'"
  9. Audience pulls only Domain_one user details (30domainone users) and it ignores
  10. Domain_two users (20domaintwousers) though they are member of 'Dev-X' group.

What could be the issue & fix, how does SharePoint pulls the user details & how it examines the audience rule?

share|improve this question

I didn't answer when this was first posted because I wasn't sure of the specific details, but my understanding is that When members of Domain_Two belong to a group in Domain_One the reference or link is not the same as it is for the local users so it doesn't make the match.

I had the same issue a few years ago when I had multiple domains and Security groups that contained cross-domain accounts.

share|improve this answer
can you tell me that how did you fix the issue ? do you think the below link may help:… – Karthikeyan Jun 21 '10 at 10:00
In my case I fixed the issue by creating a separate group for the separate domain. – Mike Oryszak Jun 21 '10 at 12:46
Looks like Rock Wang's answer is your best option to try. – Mike Oryszak Jun 21 '10 at 12:50
thank you for your help, let me try the same & will get back to you with the findings. – Karthikeyan Jun 21 '10 at 14:04

This is critical to understanding how SharePoint collects information, from AD, about group membership. SharePoint does NOT import the membership of groups by directly querying those groups. Rather, SharePoint determines what groups a user belongs to by reading the user’s memberOf property. But the memberOf property will not show a user’s membership in local or global groups in another domain, so audiences based on those groups will be missing that user.

share|improve this answer

Below are the possible solutions that I can think of:

A. Control the audience through SharePoint Security group

  1. Create a SharePoint Security group
  2. Add the users into the security group
  3. Create an audience using the SharePoint Security group

B. Control the audience through SharePoint Security group along with AD group

  1. Create an AD group with global scope in each domain
  2. Add the users into the AD groups
  3. Create an Audience & use those AD groups to control the audience

C. Control the audience through AD group

  1. Create an AD group with global scope in each domain
  2. Create an AD group with Local Domain scope in Main domain
  3. Add the other domain groups into the Local Domain group
  4. Create an audience & control through that Local Domain group

Please let me the best solution that you would suggest.

share|improve this answer

Your Answer


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.