The Exchange Edge Transport server version is incorrect in EAC or ECP after upgrade

Applies to: Exchange Server 2019Exchange Server 2016 Standard EditionExchange Server 2016 Enterprise Edition More


After you upgrade a Microsoft Edge Transport server to a new version, you notice the following situations:

  • In Exchange Admin Center (EAC ) or Exchange Control Panel (ECP), the version information for the Edge Transport server isn't updated as expected, as shown in the following screen shot. 



  • On another server that is running Exchange Server and that is not an Edge Transport server, you run the Get-ExchangeServer cmdlet in Exchange Management Shell by using the following command:

    Get-ExchangeServer edge | FL Name, AdminDisplayVersion

    After you run the command, you notice that the AdminDisplayVersion output is incorrect.


This issue occurs because the Edge Subscription XML file that contains the version information is not updated when you upgrade the Edge Transport server.


To resolve this issue, resubscribe the Edge Transport server. To do this, follow these steps:

  1. On the Edge Transport server, run the New-EdgeSubscription cmdlet in Exchange Management Shell to create and export the Edge Subscription file, as follows:

New-EdgeSubscription -FileName "c:\EdgeServerSubscription.xml"

  1. On the Mailbox server, import the file that is generated in step1, and then complete the resubcription process. To do this, run the following commands in Exchange Management Shell:

[byte[]]$Temp = Get-Content -Path "C:\EdgeServerSubscription.xml" -Encoding Byte -ReadCount 0
New-EdgeSubscription -FileData $Temp -Site "Default-First-Site-Name"

Important You have to resubscribe the Edge Transport server to the same Active Directory site that it was originally subscribed to.

Note You do not have to remove the original Edge Subscription. This is because the resubscription process overwrites the existing Edge Subscription.



To learn more about Edge Subscriptions, see the following Exchange TechNet topics: