Hiya,

Got a peculiar problem here. Trying to set audience on a link it doesnt work as we want it to. We have the following behavior:

If adding users directly on SharePoint Group no problems. However if adding AD group to SP group, it doesnt work. Member count for AD Group is 0

AD Group is created as Global, however tried placing it in a Domain Local group to see if that changed anything. SP synchs the AD groups fine, however it seems like it doesnt read the members, thus not granting any users access based on AD group membership.

Not sure if this is default behavior or?

Hi,

 

It seems a known issue, but there is no workaround for this.

It worth to reading these threads

http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/8ede2f40-2b11-416b-b426-51c1b6479c33

http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/586494b9-d259-4abf-a857-26137fa30460

 

Hope this helps

 

Thanks!

Stanfford

Jesper, read the first thread posted by Stanfford so you can see the history of my experience with this issue.  To save you some time, the last word I got was that it "may" get fixed/changed in SP2.  I'll forward your example as extra proof - more and more people keep hitting this, and it helps get the change approved, I hope.

Thanks loads for the answers..

As far as I can read it, their aint no solution and there isnt any point opening a case with MS, as nothing really happends..

Well aint that just great!

Basically the short answer is to use SP groups rather than AD groups for now..?

Yes.  In fact, I have specifically pleaded with my tech engineer to find out from the product team what we're supposed to do with audiences.  I already have a workaround for my main problem with SGs, but I have no workaround for how this issue affects audiences.  I've begged for an answer as to why this change was made when it negatively affects audiences and when there is no known workaround or suggestions.  Hopefully, they'll respond.

Never beg :)

I'll keep an eye out for your blog. Presume any respond will be there :)

Never beg :)

I'll keep an eye out for your blog. Presume any respond will be there :)

I reply to my other long thread with this info whenever I get it, so just set an alert on that thread if you're interested.

Target Audience dialogue window does not connect to AD for getting the groups. Instead it connects to the DB where the list of groups and their memberships are maintained. This calculation/manipulation is done during profile import i suppose.

So, in AD connections, if you have not selected the OU which contains these groups then it will not show up in audience dialogue window or if the people who belong the groups are not imported then the count will be zero.

Is there a resolution for this issue yet?  There is a great need to use AD Security Groups for Audience targeting.

Hi Clayton, any news?

Are there any News? We have the same problems

We are experiencing comparable problems on a SharePoint 2013 based platform. Any news if this has been fixed?

Findings per scenario:

Scenario 1: SharePoint group without rights, with active directory group

Webpart does not show up

Scenario 2. SharePoint group with rights, with active directory group

Webpart does show up

Scenario 3. Active directory group directly attached to webpart audience targeting

Webpart does not show up.

This leads up to a preliminary conclusion that SharePoint is not calculation membership if there are no rights / permissions involved. It looks like if SharePoint is only calculating membership when a SharePoint group with attached permissions is involved.

I'm having the same issue on SPO, was there ever a solution for this issue?