Exchange Server - Exchange 2007 and Multiple Global Address Lists
Asked By AJ
26-May-07 05:35 AM

Hello All
I am trying to set up a hosted Exchange 2007 environment where I can
run multiple orgs on one exchange server hiding one from the other. I
have pretty much acheived what I want to so far but I am stuck now!
I am trying to configure Exchange to provide the relevant global and
offline address list to the user based on the comany they belong to
and hide all the others. I have created a new OAL for each company
which filters based upon company name and have also created a new
Global Address List using the Power Shell for each organization using
the cmdlet below:
New-GlobalAddressList -Name "Contoso GAL" -IncludedRecipients
MailboxUsers -ConditionalCompany Contoso
It was my understanding from the above command that a global address
list would be created and mailbox users belonging to Contoso would be
added. After this was created and updated I was expecting the client
to utilise this Global Address List, however it doesn't appear to be
working like and I can see everyone from the client. I am basically
seeing the default global address list.
Is there a command I can use to tell the client to utilise this new
global address list?
TIA
AJ
Active Directory
(1)
ADSI
(1)
ConditionalCompany
(1)
IncludedRecipients
(1)
GlobalAddressList
(1)
OAB
(1)
MailboxUsers
(1)
AspxExchange
(1)
Dave Goldman [MSFT] replied...
You can not use the global address list at all. If you are going to self
host you need to *totally* segment your address lists. You can not try to
split up one address list for two groups as this will not work.
You can have only one Default Global Address List, multiple address lists
and multiple OAB's.
You also need to change the OAB that is associated with the mailbox store so
your users download that OAB and not the default, which is the default :)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Dgoldman
http://blogs.msdn.com/dgoldman
Download OABInteg from here:
http://gotdotnet.com/Community/UserSamples/Download.aspx?SampleGuid=A2338E73-F521-4071-9B1D-AAF49C346ACD
John Love replied...
My Company is doing the same thing. I found a really good tutorial on msexchange.org. Basicly though you have to use ADSI Edit, which is unsupported by M$, and if you use it incorrectly you can screw up your Active Directory. You have to limit permissions to the address lists you create with ADSI Edit. The Tutorial on msexchange.org for Hosted Exchange gives really good intructions on how to do this.
Support given as is, YMMV, all risk is on you.
Tushar Shah replied...
change.org. Basicly though you have to use ADSI Edit, which is unsupported b=
y M$, and if you use it incorrectly you can screw up your Active Directory. =
You have to limit permissions to the address lists you create with ADSI Edit=
. The Tutorial on msexchange.org for Hosted Exchange gives really good intru=
ctions on how to do this.
I find the documentation on googling for what you wanted.
http://telnetport25.wordpress.com/2008/06/04/exchange-2007-service-pack1-and=
-address-list-segregation-part-1-getting-started/
Well, Support IS NOT GIVEN for any customers at MS for Address List
Segregation for any version below E2k7 SP1.
Read the answer to the Question: "Why is Exchange 2007 Service Pack 1
a requirement."
http://blogs.msdn.com/dgoldman/archive/2008/02/17/exchange-2007-address-list=
-segregation-document-updates.aspx
http://blogs.msdn.com/dgoldman/archive/2008/02/19/exchange-2003-address-list=
-segregation-document.aspx
Jay PK replied...
Hi,
My Company alos doing the same, Could you please send me the link for the tutorial?
is it for Ex2007?
thanks in advance.
Remove Active Directory from Exchange 2003 server Exchange Server We are in the process of installing an asynchronous installing exchange and moving everything back. OUCH! Has anyone any experience in just demoting the Active Directory from the Exchange server, and then running an ADPrep (or possibly editing the Exchange schema with ADSI edit) to 'fix' Exchange? I am just thinking that the 'right' way seems like a appreciate any insight that anyone has on this subject. Thank you! -KC Exchange Setup Discussions Active Directory (1) ADPrep (1) OUCH (1) You cannot demote an Exchange server that is a Domain choice but to set up a new box and migrate everything to it. keywords: Remove, Active, Directory, from, Exchange, 2003, server description: We are in the process of installing an asynchronous
move certain mailboxes to our new exchange 2010 server. I get the error message: Error: Active Directory operation failed on {Domain Controller Name}. This error is not retriable. Additional information: Insufficient access rights to perform the operation. Active directory response: 00002098: SecErr: DSID-03150E8A, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0 The user has insufficient access have moved just fine. Where should I begin troubleshooting this problem? Thanks. Exchange Admin Discussions Active Directory (1) SecErr (1) Mailboxes (1) Excahnge (1) Helo (1) Mailserver (1) Databases (1) INSUFF (1 same problem, did you find any solution? For me it was AD permissions. Go to ADSI and find the mailbox in question. Properties > Security > Advanced. Check the box to allow inheritable move certain mailboxes to our new exchange 2010 server. I get the error message: Error: Active Directory operation failed on {Domain Co
am getting an error when running the Mail Flow Troubleshooter against Edge Server synchronization with Active Directory, the message reads as below. EdgeSync replication issues were found with ADAM instance One or more inconsistencies were found with Active Directory Application Mode (ADAM) Instance on server blah.blah.co.uk. This is an indication that EdgeSync has not successfully replicated critical configuration information from Active Directory to this ADAM instance. Not sure where to go with this one, if I run Edge server but gets stuck at that point. Thanks in advance, JV. Exchange Admin Discussions Active Directory (1) EdgeSync (1) Troubleshooter (1) Inconsistencies (1) Firewall (1) ISA2006 (1) OK, so I have
have updated to exchange 2007. However I still have some exchange 2003 objects in my active directory. Is it safe to completely remove these objects which are all in: CN = First Administrative Group under the configuration / services container in active directory. There is one server in this group, however the server was uninstalled using the exchange 2003 install program so I'm not sure why its still in active directory. Its presence in AD is causing errors when I run best practices scans. Is there Bill Exchange Admin Discussions Exchange Server 2003 (1) Exchange Server 2007 (1) Microsoft Exchange (1) Active Directory (1) Exchange Server (1) Outlook 2007 (1) Outlook (1) LegacyExchangeDN (1) You should be able
Completely remove Exchange 2003 from Active Directory Exchange Server We have basically completed a transition from Exchange 2003 to Exchange 2007. Due had to shut down the Exchange 2003 Server (we are a single server environment - running Active Directory 2003) and all seems to be running just fine with the '03 server being shut How can I get rid of the above errors and completely remove Exchange 2003 from Active Directory? Any help is truly appreciated Exchange Setup Discussions Microsoft Exchange (1) Active Directory (1) MikeDub (1) Exchagne (1) C1814489636D (1) Connectors (1) I can't tell you how