I'm running a SharePoint 2010 environment and have just set up an audience based on a Windows Security Group.

I've set up the following rule:

Operand: User
Operator: Member Of
Value: Windows Security Group name

When I compile the audience it says the number of members is 0 (zero).

The Windows Security Group in Active Directory has about 7 members already, but they are not shown in the audience.

Does anyone here have experience in setting up SharePoint 2010 audiences based on Windows Security Groups in Active Directory?

Sources used:

  • was there a compilation error when you compiled it? have you specified any audience rules? (if so remove them an re-compile) Commented Jul 2, 2012 at 10:34
  • @AnthonyKasses Thank you for replying. There are no compilation errors.
    – TempaC
    Commented Jul 2, 2012 at 10:53
  • does running the "User Profile Service Application - Audience Compilation Job" manually help? Commented Jul 2, 2012 at 11:12
  • @AnthonyKasses - I manually executed the job "User Profile Service - Audience Compilation Job". The job succeeded but it did not populate the audience. - Do I need to edit the User Profile Service Application Policy setting to include "MemberOf" ?
    – TempaC
    Commented Jul 2, 2012 at 11:32
  • no I wouldn't do that and I think it is a reserved property anyway. Maybe ensure the User Profile Service App is healthy and a successful synchronisation has previously been run. Importantly check you're not filtering out these groups/users via the sync. If you do kick off a sync, the compilation job wont start until FIM has finished. (disclaimer here running FULL syncs .. all the usual warnings with FIM apply). Not sure this will help you but audience compilation is based off the UPS app so it pays to check that first. Commented Jul 2, 2012 at 12:12

1 Answer 1


I realize this is a very old thread but I just wanted to add one more possible reason which I found. In my case, I found compiled audiences did not update because the User Profile Service Application (UPS) Permissions contained old Managed Service Accounts which had been deleted from SharePoint and from AD, but were still registered with full control over the UPS.

I was unable to remove the old accounts from the UPS Permissions screen, because they had already been deleted from the Managed Service Accounts list, so I ended up having to use PowerShell. Once I had deleted all the rogue accounts from the UPS Permissions list, I re-ran the user profile sync and then re-compiled the audience, and the membership of the audience updated correctly.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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