upgrading from Exchange 2003 to 2010 and keeping the edge server with 2007
Hi We want to upgrade our exchange 2003 to 2010 deployment but want to install the exchange 2007 for the edge transport role how can we do that? should we install a 2007 server in the environment to move on or can we go on with 2010 then later install 2007 with edge role and just add it to the organization. We have 3 licenses for 2010 that we want to use for hub and client access for one and another one for unified messaging and one for mailbox. We have one license for 2007 that we want to use for EDGE transport role. Thanks Tony
April 7th, 2011 3:48pm

Hi, You can install the 2007 edge server anytime you want - it is not part of the internal exchange organization. This might help: http://technet.microsoft.com/en-us/library/dd346708.aspx Leif
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2011 5:14pm

The edge server does not require active directory (uses ADAM), so you can deploy it later with no worries.
April 7th, 2011 9:17pm

Hi Although the Edge Transport Server role is isolated from Active Directory on the internal corporate production network, it is still able to communicate with the Active Directory by making use of a collection of processes known as EdgeSync that run on the Hub Transport Server and which, since it is part of the Active Directory, have access to the necessary Active Directory data. The Edge Transport server uses Active Directory Application Mode (ADAM) to store the required Active Directory data, which is data such as Accepted Domains, Recipients, Safe Senders, Send Connectors and a Hub Transport server list (used to generate dynamic connectors so that you do not need to create them manually). But even though you would be able to use the Edge Transport server role as a smart host or an SMTP relay server in an Exchange 2010 organization, you will not be able to replicate configuration and recipient data from Active Directory to ADAM using EdgeSync as this requires an Exchange 2007 Hub Transport server on the internal network. However, this doesn’t hinder you from using the filtering agent that doesn’t rely on the EdgeSync services. I don’t recommend your saying. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
April 8th, 2011 9:48am

Hi Although the Edge Transport Server role is isolated from Active Directory on the internal corporate production network, it is still able to communicate with the Active Directory by making use of a collection of processes known as EdgeSync that run on the Hub Transport Server and which, since it is part of the Active Directory, have access to the necessary Active Directory data. Just to clarify this statement; It is not Edge Transport server that communicates with Hub Transport (or AD for that matter) but rather Hub Transport server that initiates a uni-directional push syncronization towards the Edge Transport server. The Edge Transport server uses Active Directory Application Mode (ADAM) to store the required Active Directory data, which is data such as Accepted Domains, Recipients, Safe Senders, Send Connectors and a Hub Transport server list (used to generate dynamic connectors so that you do not need to create them manually). This is true up till the last statement. Dynamic Connectors are the Hub-to-Hub connectors inside of the Exchange Organization. The connectors between an Edge Transport server and the Hub Transport servers in a subscribed Active Directory Site are static. The Hub Transport server list is used to keep track of all the Hub Transport servers in the subscribed Active Directory Site. All these servers are possible targets for internal mail delivery and are represented in the inbound connector on the Edge Transport server with "--" in the Network Tab. EdgeSync and Send Connectors EdgeSync Replication Data But even though you would be able to use the Edge Transport server role as a smart host or an SMTP relay server in an Exchange 2010 organization, you will not be able to replicate configuration and recipient data from Active Directory to ADAM using EdgeSync as this requires an Exchange 2007 Hub Transport server on the internal network. The first statement is correct but the second is not. There is no difference in Edgesync between Exchange 2010 Hub Transport Server and Exchange 2007 Hub Transport server when it comes to syncronizing against a Exchange 2007 Edge Transport server as a target. You'll have full functionality in Edgesync from 2010 Hub towards 2007 Edge. But if you were to use Edge 2010 with Hub 2010 you'd get incremental syncronizations where as Edge 2007 only understands full syncronizations. Upgrade from Exchange 2007 Transport However, this doesn’t hinder you from using the filtering agent that doesn’t rely on the EdgeSync services. I don’t recommend your saying. I see no technical issues with your plan as to deploy your Edge Transport server as an Exchange 2007 but my personal recommendation would still be to go for Exchange 2010 here as well. It's not really agood situation to have different versions running in coexistence for a long time. It complicates things unnecessarily.Jesper Bernle | Blog: http://xchangeserver.wordpress.com
April 11th, 2011 12:49am

Hi Jesper: Thanks to correct me. I just do the test and you are right. :)Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
April 12th, 2011 11:49am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics