Dynamic Groups ignoring RecipientContainer

[Eric]

I have just migrated my server from Exchange 2003 to 2007 and decided
to start taking advantage of the Dynamic Distribution Groups. We have
our users separated into an OU for each division. I would like to
make a distribution group that is filtered by the user's Title in each
OU. I am trying the command:

New-DynamicDistributionGroup -Name 'Division Alpha Faculty'
-OrganizationalUnit 'domain.edu/Department/Distribution Groups'
-RecipientContainer 'domain.edu/Department/Divisions/Alpha'
-RecipientFilter {((RecipientType -eq 'UserMailbox') -and (title -eq
'Faculty'))}

When I issue the command it accepts it, creates the group and gives no
error message. But when I go to view the members of the group it
shows all users in the domain that have a title of "Faculty", not just
the ones that are in my target OU.

What am I doing wrong? I would love to get this feature working since
it would simplify a number of groups we have to assign to people.

Thanks...
Eric

[Ed Crowley [MVP]]

The -OrganizationalUnit parameter dictates where the new dynamic
distribution group is created and is not a search filter. There isn't an
effective way to search against the organizational unit because it is not an
attribute on the recipient object.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
.

"Eric" <esc...@gmail.com> wrote in message
news:2e92920e-8b2b-449a...@8g2000hse.googlegroups.com...

[Eric]

What about the RecipientContainer option on the cmdlet? In all the
documentation it states that is used to supply the OU to apply the
filter against. I am starting to wonder if this option doesn't work
when you are using the RecipientFilter option.

Eric

[Ed Crowley [MVP]]

You know, after rereading the documentation I come to the same conclusion as
you do, so I'm suspicious that there's an undocumented incompatibility
between the -RecipientContainer and -RecipientFilter parameters much as you
can't use the other filter-type parameters along with -RecipientFilter.
I'll ask about that to a higher authority and post back if I get anything.

--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
.

"Eric" <esc...@gmail.com> wrote in message

news:c278bbf8-098c-4ddb...@m3g2000hsc.googlegroups.com...

[Ed Crowley [MVP]]

I have a potential answer for you. I am advised by a Microsoft expert that
when you expand the group using the Exchange Management Console it ignores
the -RecipientContainer, but if you actually send to the list it does take
effect. Try sending a message to the dynamic distribution group with a
delivery receipt and see if the results match what you want.

--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
.

"Eric" <esc...@gmail.com> wrote in message
news:2e92920e-8b2b-449a...@8g2000hse.googlegroups.com...

[Eric]

Yes it does work when sending the message. So just no way to get a
list of who its sending to with the Console or PowerShell at this
time. I can live with this as long as the group is not sending to
everyone in the entire domain.

Eric

[Ed Crowley [MVP]]

From what I understand you'll have to accept this behavior. Maybe it'll get
changed at some point in the future.

--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
.

"Eric" <esc...@gmail.com> wrote in message

news:4e6b0df5-2509-4693...@k30g2000hse.googlegroups.com...

[Eric]

Hopefully so... although I found out something interesting earlier
today. We use Hyena to do AD management and I opened one of the
dynamically defined groups and noticed there was a preview tab. When
I selected it I was presented with the correct group members. So at
least I now have a way to proof my groups without sending a message
out.

Eric