Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Targeting a web part to a specific AD group fails

  Asked By: Shonda    Date: Mar 19    Category: Sharepoint    Views: 4638

I know that we are supposed to be able to target a web part to a
sharepoint group, a global audience and an Active Directory security
group.
Yet, I cannot get the web part to find the AD group. (under advanced
settings of the web part config menu)
SharePoint can find the group if I add them as a user, but I cannot get
the web part to be targeted to that AD group.
Is there something I can check?
Am I doing this completely wrong?

Share: 

 

12 Answers Found

 
Answer #1    Answered By: Gina Freeman     Answered On: Mar 19

Help me understand what you mean when you say "find a group" and "target
a group". The web  part looks for audiences, not AD groups. You'll
first need to build the audience  based on the AD group, then associate
the audience with the web part.

 
Answer #2    Answered By: Tyrell Nash     Answered On: Mar 19

I am referring to MOSS by the way..I didn't make that clear in the my first
post..
When you go into a web  part, modify shared web part, advanced , target  audience
you get an option to target the web part  to a global  audience, a sharepoint
group, or a distribution/security group.
I choose dist/sec group  but nothing shows up..I have seen this work in other
implementations, but I can't understand why it doesn't work across the board.

 
Answer #3    Answered By: Silvia Wilkinson     Answered On: Mar 19

Because it isn't perfected, yet. They are working on it, that's all I
can say. Use 1 group, and experiment with direct targeting  of Universal
and Local groups. I should have an update in 2 weeks, and I will post it
here. I am meeting with some folks in Redmond, and am asking this very
simple, yet  painful topic!

 
Answer #4    Answered By: Candy Walter     Answered On: Mar 19

When you say use 1 group..should I create 1 universal, 1 global, and 1 local and
see which one, if any, shows up in the lookup?
Otherwise, I am not sure what you mean by use "1 group".

 
Answer #5    Answered By: Leanne Rios     Answered On: Mar 19

Have you tried creating an audience  in the SSP and
adding the security group  to that audience?

 
Answer #6    Answered By: Zachary Roberts     Answered On: Mar 19

Here is the thing..take a domain group  called domain\technology.
I can add  domain\technology to the portal and it works fine..
But when I target  the webpart to that domain group, it doesn't show up when I
check names..AND if I try to create an audience  with that domain group, it also
doesn't find  it..
There seems to be some disconnect between MOSS and AD..
Any advice?

 
Answer #7    Answered By: Maura Durham     Answered On: Mar 19

Did you try a manual compile after adding the AD group  to the Global
group? This is useful for troubleshooting your problem, maybe?

 
Answer #8    Answered By: Jagat Pandit     Answered On: Mar 19

Nest groups via AD into a single Universal group. Then, target  content
to the Universal group. There is a known bug that you cannot add
multiple AD groups to target a Web part.

This is all over the board in my tests, sorry. I wish I had a better
answer for you. I know companies that have had success with local
groups. Most do not have favorable results with Global Groups.

 
Answer #9    Answered By: Jerod Carrillo     Answered On: Mar 19

Apparently, according to my client, they are working with universal groups..I
can't even get to the AD groups in audience  creation or compilation..
This is very frustrating..

 
Answer #10    Answered By: Hema Pasupuleti     Answered On: Mar 19

I would call Microsoft CSS. You will not have been the first on this
problem. I honestly wish I knew how to help you. sorry. The idea behind
Universal groups is they expanded on the GC, so they worked. This isn't
perfect either, it seems.

post the fix, if you find  it? Many others have similar issues
with no resolution. Thanks!

http://support.microsoft.com/kb/839949 might help a little. It is the
basis for some large companies to move to universal groups in general.

 
Answer #11    Answered By: Candis Kinney     Answered On: Mar 19

A couple of other things to look for:

Make sure the group(s) have explicit access rights to the site i.e.
add the AD group(s) you want to use for targeting  to the site
members or visitors group

Make sure there are no access rights issues in AD. We had an issue
using an AD group  in SharePoint and it turned out there was a
permissions issue with the SharePoint service account accessing the
OU containing some of the users in the group.

 
Answer #12    Answered By: Cora Bradshaw     Answered On: Mar 19

We have had problems with global  groups. I would suggest trying domain
local or Universal. We generally use the latter, but many other things
depend on your group  types. So, don't willy-nilly change them. There
is some *magic* involved with getting new groups to show up. I have no
clue what it is, but eventually, they show up. Maybe someone else on
this list knows how.

 
Didn't find what you were looking for? Find more on Targeting a web part to a specific AD group fails Or get search suggestion and latest updates.




Tagged: