Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Can't seem to use employeeType in query-based distribution lists

888 views
Skip to first unread message

Mark C James

unread,
Feb 21, 2007, 3:55:50 PM2/21/07
to
I've populated employeeType with the relationship of the people in our
network (Employee, Contractor, or Customer).

When I go into Active Directory Users and Computers, create a query-based
distribution list, and make a custom LDAP query of;

employeeType=Employee

and hit the "Find" key, it finds everyone I want.

If I go to the Preview panel, it does not find them. I also see that it adds
to the query. In the Preview panel it looks like this;

(&(!cn=SystemMailbox{*})(&employeeType=Employee))

Now I can also populate extensionAttribute3 with the same data. The query;

extensionAttribute3=Employee

works in both the "find" function when building the query and the preview
panel. Which also expands it to;

(&(!cn=SystemMailbox{*})(&extensionAttribute3=Employee))

We're using a native AD 2003 with Exchange 2003

Ed Crowley [MVP]

unread,
Feb 21, 2007, 5:34:52 PM2/21/07
to
I don't know that it will make any difference but the ampersand in front of
the employeeType is unnecessary.

You might change the query to be just employeeType=Employee and remove the
rest and see if it works. Your system mailboxes shouldn't have that
attribute populated, so they wouldn't match the query anyway.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Mark C James" <Chris...@Indus.com-SrMessagingAdministrator> wrote in
message news:F1BAC993-1DCB-436D...@microsoft.com...

Rich Matheisen [MVP]

unread,
Feb 21, 2007, 11:14:02 PM2/21/07
to
Mark C James <Chris...@Indus.com-SrMessagingAdministrator> wrote:

>I've populated employeeType with the relationship of the people in our
>network (Employee, Contractor, or Customer).
>
>When I go into Active Directory Users and Computers, create a query-based
>distribution list, and make a custom LDAP query of;
>
>employeeType=Employee
>
>and hit the "Find" key, it finds everyone I want.
>
>If I go to the Preview panel, it does not find them. I also see that it adds
>to the query. In the Preview panel it looks like this;
>
>(&(!cn=SystemMailbox{*})(&employeeType=Employee))

As odd as it might seem, that query works (even with the oddly placed
ampersand). To get the ampersand in the right place, surround your
query with parenthesis: employeeType=Employee

However, while the LDAP search works in LDP, it doesn't work when used
in a QBDL.

--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.p...@getronics.com
Or to these, either: mailto:h.p...@pinkroccade.com mailto:melvin.mcp...@getronics.com mailto:melvin.mcp...@pinkroccade.com

Mark C James

unread,
Feb 22, 2007, 8:41:03 AM2/22/07
to
I don't have the option of changing the LDAP query in the "Preview" tab. This
is what it constructs.

It also doesn't matter whether or not I place parenthesis around my custom
query.

Rich's observation is correct. It works in LDP, but not the QBDL.

Does anyone have a remedy or reason as to why this won't work? Seems a
simple and straightforward query......

Rich Matheisen [MVP]

unread,
Feb 22, 2007, 8:36:51 PM2/22/07
to
Mark C James <Chris...@Indus.com-SrMessagingAdministrator> wrote:

>I don't have the option of changing the LDAP query in the "Preview" tab. This
>is what it constructs.

If you surround your query with parenthesis it'll look like everyone
expects it to look.

>It also doesn't matter whether or not I place parenthesis around my custom
>query.

It doesn't function differently, but the query string will be
formatted differently.

>Rich's observation is correct. It works in LDP, but not the QBDL.
>
>Does anyone have a remedy or reason as to why this won't work? Seems a
>simple and straightforward query......

I thought it was, too. :-(

Mark C James

unread,
Feb 23, 2007, 8:45:49 AM2/23/07
to
Without parentheses, the preview query looks like this;

(&(!cn=SystemMailbox{*})(&employeeType=Employee))

With Parentheses, the preview query looks like this;

(&(!cn=SystemMailbox{*})(&(employeeType=Employee)))

Still the same result, no names coming back. To quote Spock in an old James
Blish novel; "Spock must die"; "A difference that makes no difference is not
a difference at all".

Rich Matheisen [MVP]

unread,
Feb 23, 2007, 8:32:20 PM2/23/07
to
Mark C James <Chris...@Indus.com-SrMessagingAdministrator> wrote:

>Without parentheses, the preview query looks like this;
>
>(&(!cn=SystemMailbox{*})(&employeeType=Employee))
>
>With Parentheses, the preview query looks like this;
>
>(&(!cn=SystemMailbox{*})(&(employeeType=Employee)))
>
>Still the same result, no names coming back. To quote Spock in an old James
>Blish novel; "Spock must die"; "A difference that makes no difference is not
>a difference at all".

I didn't say it made a difference, I said it would look like everyone
expects it to look. Now /that's/ a difference!

jesseinfra

unread,
Nov 23, 2009, 3:16:12 PM11/23/09
to
I am having the same issue.. did you ever figure this out or develop a work around?

Chris.Jame wrote:

I don't have the option of changing the LDAP query in the "Preview" tab.

22-Feb-07

I don't have the option of changing the LDAP query in the "Preview" tab. This
is what it constructs.

It also doesn't matter whether or not I place parenthesis around my custom
query.

Rich's observation is correct. It works in LDP, but not the QBDL.

Does anyone have a remedy or reason as to why this won't work? Seems a
simple and straightforward query......

"Rich Matheisen [MVP]" wrote:

Previous Posts In This Thread:

On Wednesday, February 21, 2007 3:55 PM
Chris.Jame wrote:

Can't seem to use employeeType in query-based distribution lists


I've populated employeeType with the relationship of the people in our
network (Employee, Contractor, or Customer).

When I go into Active Directory Users and Computers, create a query-based
distribution list, and make a custom LDAP query of;

employeeType=Employee

and hit the "Find" key, it finds everyone I want.

If I go to the Preview panel, it does not find them. I also see that it adds
to the query. In the Preview panel it looks like this;

(&(!cn=SystemMailbox{*})(&employeeType=Employee))

Now I can also populate extensionAttribute3 with the same data. The query;

extensionAttribute3=Employee

works in both the "find" function when building the query and the preview
panel. Which also expands it to;

(&(!cn=SystemMailbox{*})(&extensionAttribute3=Employee))

We're using a native AD 2003 with Exchange 2003

On Wednesday, February 21, 2007 5:34 PM
Ed Crowley [MVP] wrote:

I don't know that it will make any difference but the ampersand in front of
I don't know that it will make any difference but the ampersand in front of
the employeeType is unnecessary.

You might change the query to be just employeeType=Employee and remove the
rest and see if it works. Your system mailboxes shouldn't have that
attribute populated, so they wouldn't match the query anyway.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Mark C James" <Chris...@Indus.com-SrMessagingAdministrator> wrote in
message news:F1BAC993-1DCB-436D...@microsoft.com...

On Thursday, February 22, 2007 8:41 AM
Chris.Jame wrote:

I don't have the option of changing the LDAP query in the "Preview" tab.
I don't have the option of changing the LDAP query in the "Preview" tab. This
is what it constructs.

It also doesn't matter whether or not I place parenthesis around my custom
query.

Rich's observation is correct. It works in LDP, but not the QBDL.

Does anyone have a remedy or reason as to why this won't work? Seems a
simple and straightforward query......

"Rich Matheisen [MVP]" wrote:

EggHeadCafe - Software Developer Portal of Choice
Team Development Concepts with Visual Studio.NET
http://www.eggheadcafe.com/tutorials/aspnet/ed58ca34-d824-4644-91fd-33e808ca2492/team-development-concepts.aspx

0 new messages