msexchquerybasedn attribute as address list DN

I have segregated organizations and address lists on my exchange 2003 server. using the msexchquerybasedn attribute, I am able to restrict OWA and blackberry GAL searches to the AD container that a users account is loacted in.

I have a user that needs to have the ability to view adresses from multiple containers. I dont want to change their msexchquerybasedn attribute to the root container and after some research it appears that i may be able to use the DN of a custom address list to accomplish this.

I went ahead and configured a new address list that would cover all the containers that the user would need to query, but setting the msexchquerybasedn attribute to the DN does not yeild any results when viewing or searching from OWA or from the blackberry. Is there something i am missing when implementing this feature?

any help would be much appreciated.

thank you
LVL 18
Sanga CollinsSystems AdminAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Alan HardistyCo-OwnerCommented:
You should be able to set the attribute to a Container or Address List, so if you create an Address list that houses all the users they need, you should be able to set that as the msexchquerybasedn value.
http://support.microsoft.com/kb/817218 
0
Sanga CollinsSystems AdminAuthor Commented:
That is exactly my problem. when i set the attribute to a container, it works fine. when i set the attribute to an address list it doesnt work. I've tried both the new address list i created and older ones that i had create a few years ago just incase i missed something with the new one.

just to be clear i am not setting the attribute to the DN of a global address list object, just a regular address list object.

thanks for the quick reply
0
Alan HardistyCo-OwnerCommented:
Unfortunately, MS pulled all support for Address List Segregation in Exchange 2003 as it was flaky at best and I tried and failed to segregate my own server numerous times.
It works very well on 2007 / 2010 and I am not sure if the problem you are facing is part of the reason why all support was pulled by Microsoft.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Sanga CollinsSystems AdminAuthor Commented:
I had a suspicion that the implementation would work flawlessly in exch 2007/2010 and that i would have to do some leg work to get it to function in exchange 2003.

After some more tinkering with the address list i created. i went ahead and set the attribute to the address list DN and can now succesfully search that address list from my blackberry device. but running the same search from OWA does not yeild any results at all.

i think i am getting close so i will try a few more things and then post my results here
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.