I am working for a company with multiple plants (6 plants) which one of them is HQ. Each of these plants has its own windows 2003 AD installed. We are planning to install an exchange 2010 in each of these forests. There are a number of major requirements that must be met:
1- Company insists on using a unique single domain name for email addresses of the users in all 6 plants.
2- Users in all 6 plants need to have access to a unique GAL.
Plus I am confused how to implement a single mail relay for all of these organizations.
I will be appreciated if anybody help me with giving some idea how to implement this scenario.
Thanks in advance Bijan
< Message edited by kiani_b -- 9.Aug.2011 3:58:48 AM >
What do you mean by "Users in all 6 plants need to have access to a unique GAL" What do you define as unique? Each plant has their own GAL or they all share a central GAL?
The mail relay is also quite simple...
Is the HQ plant going to act as the central / control for all the forests? IE, do you want to route all mail through the HQ server(s) or each site routes out their own mail?
Posts: 6812
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
Six foests, one SMTP address space and one GAL. Right here, right now you are going to employ an external consultancy to get that done for you. There are quite a few packages on the market to get that done for you. The Exchange is the "easy" part. You have every site with a dummy email address space to send between each other with the right address presented to the outside world. Yeah, the easy part !!
The challenging part is getting six forests syncing properly with each other.
Whereabouts are you? If you're in the US Edgile and eNsync are two orgs you really need to consider.
Thank you travis.sheldon also thank you mark for your advice,
Users - in all plants - exactly need to share a central GAL and have one SMTP address space. Also I want to route all mails through the HQ server(s). The AD forests are completely independent from each other. There is only a 2-way trust between each plant AD forest and HQ AD forest.
< Message edited by kiani_b -- 9.Aug.2011 12:39:38 PM >
Posts: 6812
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
http://www.quest.com/collaboration-services/ would maybe a good place to start if you want to try this yourself. What might be useful as well as the GAL sync is also the free/busy availability. Lots of people find that pretty useful, maybe you too?
The routing through a central location is the easiest part. All of the remote systems get a Send Connector and you specify the "smarthost" to send through the IP of the central server.
The Quest solution will help you have those dummy secondary address spaces.
Is it permanent to use a third-party application for the mentioned purposes? I mean doesn't exchange 2010 have the capabilities to address the mentioned needs by itself and without any third-party?
Posts: 6812
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
The address list thing has absolutely nothing to do with Exchange. Way back in the day the Exchange 5.5 directory was in dir.edb but ever since Exchange 2000 the source has been Active Directory. All replication has to between Active Directories and Microsoft sell a solution to do this so yes, you can do this without "3rd party" solutions but you do have to have A solution. Microsoft have one (complex) and other people have one (somewhat easier).
Once things get themselves into Active Directory they are exposed in Exchange.
Exchange was specifically made to be the messaging & calendaring solution. It is not a collaboration solution (SharePoint) and is not a directory synchronization solution.
As you said, FIM and also ILM are complicated and give me much more features that I do not really need. I used an application named GALSYNC (a Germany made app) and it solve the problem of GAL. With this application I created the contacts of all users of all plants in HQ exchange organization and configure external address as primary and dummy internal address as secondary addresses for these contacts so messages that are coming to HQ exchange from internet, simply are routed to their destination through their corresponding connector.
No the only problem is that I don't know how configure the HQ exchange to route messages to internet by external domain name and not dummy internal domain name?
Mark I have all the issues solved, except 2 thing: Messages which are sent to internet from within 1 of the sites through HQ site (as mail relay) do not reaches the destination and instead HQ exchange send an undelivery notification with the following error message:
"you do not have permission to send to this recipient SMTP:550 5.7.1 unable to relay." and also I do not know how to make sure the messages are sent by their external addresses and not their dummy internal addresses. Would you please help me with these errors?
Best regards Bijan
< Message edited by kiani_b -- 18.Aug.2011 2:31:34 AM >
It can be fixed either by "GALSync" app or galsync feature of FIM. I have tested both of them. Now I have 2 other issues which I have mentioned them in previous post to Mark.
As you say, FIM and ILM also complicated and give me many more features that I do not really need. I used a program called GALSync (Germany made the app) and it solves the problem with the GAL. With this application, I have contacts to all users of all plants in HQ exchange organization and configure the external address as a dummy internal addresses primary and secondary addresses as contacts for these so that messages coming in HQ currency of the Internet is simply routed to their destination with their corresponding locations.
It is not the only problem is that I do not know how to configure Exchange to route messages to the headquarters of the external Internet domain name and not a doll in a domain name?
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2010] >> General >> A unique domain name for email addresses and a unique GAL for multiple organizations 
A unique domain name for email addresses and a unique G... - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
