Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds


  Asked By: Alexandria    Date: Feb 05    Category: Sharepoint    Views: 1451

SharePoint Portal Server (SPS) Audiences are about displaying targeted
information, not securing information. There are currently only two ways
to use an Audience in SharePoint Portal Server:

1. Show or hide an entire Web Part based upon audience.
2. Show the listings using the Grouped Listings Web Part grouped by

People often want to use the second method but the default setting is
for the Grouped Listings Web Part to group by Group not Audience. So it
appears like Audiences is broken. It isn't, the Web Part just isn't as
robust as one would expect it to be. In other ways, the Grouped Listings
Web Part is more advanced that you might expect; for instance, check out
its rollup features.



12 Answers Found

Answer #1    Answered By: Dorothy Farmer     Answered On: Feb 05

I want to create an audience  based on an AD security group, say g_test,
but that security group  has as it members not only users but other
security groups, g_test1, g_test2.

I've created an audience based  on g_test, but it looks like only users
in g_test are audience members and not users in g_test1 and g_test2. Is
this a limitation of SharePoint or am I doing something wrong?

Answer #2    Answered By: Jacklyn Burnett     Answered On: Feb 05

SharePoint wont pick up security groups contained in a SG because when you specify an SG to compile, it is only looking for user objects contained in the allocated SG.

That's my belief on how it operates but some one quote me if I am wrong.

Answer #3    Answered By: Breann Beach     Answered On: Feb 05

I disagree. I'm not sure why it may not be working for Penny, but I have many audiences  that are specified by AD group  memberships where the security group contains other groups. Are you using Windows 2003 native mode, or mixed mode? Are you including groups within other trusted domains or universal groups? My memberships are always in the same domain.

Answer #4    Answered By: Timothy Hall     Answered On: Feb 05

I had a really hard look at all the pointers
you provided and found that the forest was not at a functional level
of Windows Server 2003, and now it works.

Answer #5    Answered By: Ian Powell     Answered On: Feb 05

Has anyone set up there Portal strictly with audiences? We are having
some anomolies with AD security groups and distribution lists,
especially cross-domain (in AD) groups. Any insight, guidance, or
information is greatly appreciated. We are running SPS2003.

Answer #6    Answered By: Osvaldo Winters     Answered On: Feb 05

Word of warning - Don't use Audiences as a security mechanism.

One thing we ran into lately is that you can not use AD groups that are members of each other. It doesn't make a lot of sense to do that in the first place, but mistakes happen. What happens is that SharePoint tries to enumerate the members of each group, and gets caught in a never ending loop.

What types of anomalies are you running into?

Answer #7    Answered By: Kylie Gill     Answered On: Feb 05

The biggest issue we have found, so far anyway, is that when using a
security group  or distribution list, we do not get all the members
of that list. There does not seem to be any rhyme or reason to the
members is does or does not pick up. We are using several AD domains
and have done a full import to the profile DB but haphazardly
are 'missing' members. Some of the groups include other groups but
even if we use a group with only individual members, but across
multiple AD domains, the missing member mystery occurs. I wondered
if the problem was nested groups (as SharePoint sees a Sec Group or
DL as a "user") but through our testing thus far, there is no
consistency to which individuals is does or does not pick up.

We are being courted by an outside consulting firm to change our
implementation from virtual servers for each department to one
server for all, and use audiences  to push information  to the
appropriate people. So far, this doesn't appear to be a viable
solution. Obviously, the powers that be are increasingly convinced
that an audience  implementation is the way to go (because it
requires less hardware in the long run, especially in a campus wide
offering) and it is up to my group to prove the viability of
proposed implementation.

Answer #8    Answered By: Brianna Olson     Answered On: Feb 05

I have created a Sharepoint site on one of our DMZ's. It can access
the DC's through LDAP.

When I try to import profiles it works fine. When I try to create
audiences I am running in to a weird problem. I can create the
Audience through Specific Properties, and even under the Reports
Under. What I can't do is create it based  on groups.

So if I want to add an audience  for A user that is a member of the
Domain Users group, I get an error "The specified domain either does
not exist or could not be contacted"

Any idea why my groups don't work... Anyone know of a way around this?

Answer #9    Answered By: Allyson Burgess     Answered On: Feb 05

Do network packet capture and examine the protocols being used by the Job
Server. It sounds like checking group  membership may be using another port.

Answer #10    Answered By: Anila Bhuva     Answered On: Feb 05

I'm in my Shared Service provider, and I'm trying to add an audience
where the user belongs to a Windows Security group.

Whenever I try to add the group  I get a listing only of SharePoint SPWeb

Is this a normal behavior? How do I get it to find windows security
groups? Can the groups be domain local, global and universal?

I did install stratera's MyMemberships web  part. Did that change

Answer #11    Answered By: Elaine Mack     Answered On: Feb 05

On our intranet we have a group  that is placed on two locations. they
have some news which are specific for each locaion. When they go in I
control the display via audiences, since this could be done without any

But the problem is, when everybody else goes in, they see an almost
blank screen since they are not in one of the two audiences.

My question is, can you somehow make an "or" on audiences? Or "not
equal to" so that everybody else see the news for location 1.

Answer #12    Answered By: Baiju Hoskeri     Answered On: Feb 05

Depending on how your groups are setup, audiences  are created using one of
two patterns, either you satisfy all of the rules for membership or you
satisfy any of the rules. All the rules is like an AND, rule 1, and rule 2,
and rule 3 etc. Any is an OR, rule 1, or rule 2, or rule 3 etc. You could
create an audience  where "if you are a member of group  location 1 or group
everyone else" you can see this; and then "if you are a member of group
location 2 or everyone else" you see that. However, reading what you have
posted I don't think you really mean "everyone else".

Another approach would be to base the group membership on a property value
and set the condition of the value to "not contains" and thereby exclude
anyone who does not match that value.

Didn't find what you were looking for? Find more on Audiences Or get search suggestion and latest updates.