 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Exchange Server / Design / April 2006Site Connectors
We are migrating to a new Exchange 2003 environment at Headquarters. We currently have 2 remote sites that are connected to our Exchange 5.5 server here. If we migrate to a new Exchange 2003 organization and a new Active Directory domain, can we re-create these site connectors on the new server to participate in the old Exchange 5.5 organization to foward mail to them or do these remote sites need to be migrated to Exchange 2003 in our new organization at the same time? Any insight would be appreciated, Jonathan Both can co-exist. If you use a Routing Group Connector to connect to Exchange 5.5 Bridgehead in remote site, it should switch to RPC communication (instead of SMTP).  SignatureBharat Suneja MVP - Exchange www.zenprise.com NEW blog location: www.exchangepedia.com/blog ---------------------------------------------- > We are migrating to a new Exchange 2003 environment at Headquarters. We > currently have 2 remote sites that are connected to our Exchange 5.5 [quoted text clipped - 9 lines] > > Jonathan I created a routing group for our Remote site, and clicked on create new routing group connector, but when I click the Remote Bridgehead tab to add a remote bridgehead the list is empty. Could this be because the Exchange 2003 server and 5.5 are in different organizations? Thanks, Jonathan > Both can co-exist. If you use a Routing Group Connector to connect to > Exchange 5.5 Bridgehead in remote site, it should switch to RPC [quoted text clipped - 12 lines] > > > > Jonathan Are they in different Exchange Organizations? SignatureBharat Suneja MVP - Exchange www.zenprise.com NEW blog location: www.exchangepedia.com/blog ---------------------------------------------- >I created a routing group for our Remote site, and clicked on create new > routing group connector, but when I click the Remote Bridgehead tab to add [quoted text clipped - 25 lines] >> > >> > Jonathan Yes, the Exchange 2003 server is in a new AD domain and in a new Exchange Organization. The Exchange 5.5 remote server is in our old Exchange organization and domain. When we migrate our old Exchange 5.5 server at Headquarters to the new Exchange Organization using ExMerge, we want to make sure we can still forward mail to the remote Exchange 5.5 server. Thanks. Jonathan > Are they in different Exchange Organizations? > >I created a routing group for our Remote site, and clicked on create new [quoted text clipped - 26 lines] > >> > > >> > Jonathan If that's the case, you can create SMTP Connectors for the Exchange 5.5 Org's address space. Use IMS to route messages from Exchange 5.5 to the Exchange 2000 Org's address space. SignatureBharat Suneja MVP - Exchange www.zenprise.com NEW blog location: www.exchangepedia.com/blog ---------------------------------------------- > Yes, the Exchange 2003 server is in a new AD domain and in a new Exchange > Organization. The Exchange 5.5 remote server is in our old Exchange [quoted text clipped - 40 lines] >> >> > >> >> > Jonathan Bharat, Is it a problem if we share the same address space, aeci.org, with the other remote site? It is requiring me to foward mail to a Smarthost, is this the FQDN of the remote Exchange 5.5 server? Thanks, Jonathan > If that's the case, you can create SMTP Connectors for the Exchange 5.5 > Org's address space. [quoted text clipped - 44 lines] > >> >> > > >> >> > Jonathan If you share the address space, you have to determine which Exchange Org is authoritative for the namespace. If it isn't the Exchange 2003 Org, you will need to go change Recipient Policy and mark it as such by unchecking "This Exchange Org receives all email for this address". Once you do that, you can create the SMTP Connector for that address space and insert the fqdn of Exchange 5.5 server running IMS as a smarthost. You can insert fqdn or the ip address - I prefer the former. However, if you do decide to use IP address they need to be enclosed in square brackets - [x.x.x.x]. SignatureBharat Suneja MVP - Exchange www.zenprise.com NEW blog location: www.exchangepedia.com/blog ---------------------------------------------- > Bharat, > [quoted text clipped - 64 lines] >> >> >> > >> >> >> > Jonathan Bharat, Thanks for your reply. Our new Exchange 2003 server will be authoritive for aeci.org namespace which we use and our remote site. Our HQ Exchange 5.5 server run the IMS, and the remote site only has a site connector. The recipient policy on the Exchange 2003 server has aeci.org checked for "Exchange Org receives all email for this address" Is there anyway to foward to aeci.org address not in the Exchange 2003 address list to forward over to the Exchange 5.5 remote site server? Thanks, Jonathan > If you share the address space, you have to determine which Exchange Org is > authoritative for the namespace. If it isn't the Exchange 2003 Org, you will [quoted text clipped - 74 lines] > >> >> >> > > >> >> >> > Jonathan Two ways of doing this. i) As posted earlier, you make the first system receiving the message not authoritative for that domain and create a Connector for it and route the mail to the remote Exchange 5.5 server running IMS. Is your Exchange 5.5 Org running IMS at all? The authoritative Org is responsible for finding recipients in the directory, and if not found, send a NDR back to the sender. If not authoritative, it can look up any routes to that address space, which is where the Connector comes in, and delivers any mail for recipients not resolved in local Org over the Connector to the next hop, thus passing on the authority to deliver those messages or sending a NDR. ii) Alternatively, create a new "secondary" address-space - let's say @exch55.aeci.org, so all recipients in Exchange 5.5 Org have that as a secondary/proxy address. Their default/primary address remains @aeci.org. - next, create Contacts for Exchange 5.5 recipients in the 2003 AD so they get the aeci.org address as primary/default and @exch55.aeci.org as secondary. Now you can create a Connector to the Exchange 5.5 Org for the exch55.aeci.org namespace. Though not explicitly covering Exchange 5.5, these will apply to some extent: - Sharing SMTP address spaces in Exchange 2000 Server and Exchange Server 2003 http://support.microsoft.com/?id=321721 - XADM: How to Set Up Centralized SMTP Domain Sharing in Exchange 2000 Server for Independent Organizations http://support.microsoft.com/default.aspx?scid=kb;en-us;315511 - Supporting Two SMTP Mail Domains and Sharing an SMTP Mail Domain with Another System http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3TransnRouting/4 65d8acd-a879-4565-abcf-0edb2b09502e.mspx SignatureBharat Suneja MVP - Exchange www.zenprise.com NEW blog location: www.exchangepedia.com/blog ---------------------------------------------- > Bharat, > [quoted text clipped - 106 lines] >> >> >> >> > >> >> >> >> > Jonathan Yes, the Exchange 2003 server is in a new AD domain and in a new Exchange Organization. The Exchange 5.5 remote server is in our old Exchange organization and domain. When we migrate our old Exchange 5.5 server at Headquarters to the new Exchange Organization using ExMerge, we want to make sure we can still forward mail to the remote Exchange 5.5 server. Thanks. Jonathan > We are migrating to a new Exchange 2003 environment at Headquarters. We > currently have 2 remote sites that are connected to our Exchange 5.5 server [quoted text clipped - 7 lines] > > Jonathan |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.