- The Version Number of the Edge Transport Server Is Not Updated in the Exchange 2007 Management Tools
- Exchange Management Console Reports that Edge Transport Server is having lesser service pack.
- On Exchange 2013 Setup – All Exchange 2007 servers in the organization must have Exchange 2007 SP3 or later installed. The following servers don’t meet this requirement: edgesrv.
Applying Service packs on Edge Transport server wont reflect on Internal Exchange servers . has its one way communication.
Get-ExchangeServer | fT ServerRole,AdminDisplayVersion –AutoSize
Exchange 2013 Setup Error –
All Exchange 2007 servers in the organization must have Exchange 2007 SP3 or later installed. The following servers don’t meet this requirement: edgesrv.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.E15E12CoexistenceMinVersionRequirement.aspx
Setup will prepare the organization for Exchange 2013 by using ‘Setup /PrepareAD’. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Login to Hub Transport Server
Login to Edge Transport Server –
New-edgeSubscription –Filename "C:\Edgeserversubscription.xml"
Login to Hub Transport Server again
Get the xml file into the hub server.
Create a Edge Subscription – Use the existing xml file and import it.
Things should work.
You can run
While importing the Edge Config xml got a error that Clocks are not synchronized. Found time is different from Edge transport and hub transport servers.
Corrected the time.
Re did the Edge Config xml export and import.
It worked like a charm.
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:00
The clock setting for the Edge Transport server to be subscribed and the computer on which you are running this task are not synchronized. Make sure the clocks on all Exchange servers in your organization and your Edge Transport servers are synchronized.
Exchange Management Shell command attempted:
new-EdgeSubscription -FileName ‘D:\EdgeServerSubscription.xml’ -Site ‘Default-First-Site-Name’ -CreateInternetSendConnector $true -CreateInboundSendConnector $true
Elapsed Time: 00:00:00