I am attempting to put in a 2013 server in an environment that has 2007. The pre-req check fails saying one of the edge servers is not on SP3, but it is.

When doing a get-exchangeserver |fl name,admindisplayversion, The internal servers all show 8.3.6

When I do the same thing on the edge server, it shows 8.2 (build 176.2) for itself. That is the only place it shows it is 8.2. Everywhere else, including exsetup, it shows the correct 8.3 version number. I can also see that SP3 RU14 is installed on the edge server.

I have a maintenance window to redo the edge subscription this weekend, however I'm not sure if that will fix anything, since it's the edge server that is not able to identify it's own installed version.

How can I get the AdminDisplayVersion on the Edge server to show the correct SP that is inst

Hi scott,

Thank you for your question.

As you sail, we could update Exchange Edge server to Exchange 2007 SP3, then we could check EMC on Exchange 2007 Edge server.

If the version is still 8.2, we could restarted Exchange 2007 Edge server top check if the issue persist. Or we could run the command : get-exchangeserver |fl name,admindisplayversion to check the version of Exchange server on Exchange Edge server.

If the issue persist, I suggest we could post entire error information of the pre-requirement check to ibsexc@microsoft.com for our troubleshooting.

We could refer to the following link to download Exchange 2007 SP3 CU15:

http://www.microsoft.com/en-us/download/details.aspx?id=45269

we could refer to the following link to learn more about Exchange 2013 pre-requirement:

https://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx

We must install Exchange 2013 CU2 or later on all Exchange 2013 server in the organization.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

In addition to above suggestion, when upgrading from Exchange 2007 to 2013, I would suggest you to walk through Exchange server deployment assistant that is available from Microsoft and provides step-wise instructions by checking all the required prerequisites : https://technet.microsoft.com/en-us/office/dn756393.aspx

To migrate mailbox database between the old exchange server and newly one, you may also consider on this comprehensive application (http://www.exchangemailboxmigration.com/) that provides a very hassle-free environment during the completion of entire process and get this job done more securely.

Thanks for the reply.

2007 SP3 RU15 is installed on Edge01. I can see it in the installed updates. But when I do the get-exchangeserver |fl name,admindisplayversion, it shows as 8.2 (Build 176.2), instead of what is actually installed. 

On internal servers, the correct version is shown, but on the edge server itself, it is displaying an incorrect version. I did a reboot and redid the edge subscription which did not affect anything.

On edge01 I can see that SP3 RU15 is installed.

But when I do a get-exchangeserver, on the edge server, it shows the wrong version.

If I do a get-exchangeserver from any internal server, it shows the correct version.

Then when I run 2013 setup..

I've tried rebooting, I've tried redoing the edge subscription. I have also updated to RU15, and that did not help.

Hi Jim, thanks for the reply.

I am not attempting to see a rollup version. The original question on this thread How can I get the AdminDisplayVersion on the Edge server to show the correct SP that is installed?

I will be opening a ticket with Microsoft Support, as rebuilding the Edge server is something we would like to avoid if at all possible.

Hi Scott,

Exchange 2007 and forward do not reflect the version number either in the value for AdminDisplayVersion, ExchangeVersion, or at this registry key HKLM\SOFTWARE\Microsoft\v8.0\<Role>\ConfiguredVersion as influenced by roll ups. This is a common misconception.

The most conclusive way to get the version of your exchange server, rollup and all, is to check the file version of ExSetup.exe in the BIN folder by the following path:

C:\Program Files\Microsoft\Exchange Server\Bin

We could use the following command to check if Exchange 2007 has correct version:

 GCM exsetup |%{$_.Fileversioninfo}

 I suggest we install a new Exchange 2007 SP3 to replace this specific Exchange server.

We could refer to the following link:

http://blogs.technet.com/b/exchange/archive/2010/03/08/3409469.aspx

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

Hi scott 

We could use ADsiedit.msc and navigate the following path to check if Exchange server version has been written into AD:

Configuration>Services>Microsoft Exchange>domain>Administrative Group>Exchange Administrative Group>Server

1. We find edge01 and right click property;

2. We could find the item of serialNumber and change value into Version 8.3 (Build 389.2);

3. We could check if the issue persist.

Notice: Before we modified it, we should backup AD database or we could call MS engineer for help.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

This issue was resolved by editing in the versionnumber property in adsi edit, on an internal server. We copy/pasted the version number from Edge02, to Edge01. We then forced replication and were able to get Exchange 2013 installed. Oddly the "Serial Number" property was correctly displayed as 8.3 before we made any changes.

ADSI Edit > CN=Configuration,DC=.. > CN=Services > CN=Microsoft Exchange > CN=DomainSpecific > CN=Administrative Groups > CN=Exchange Administrative Group (FYD..) > CN=Servers > Properties of CN=edge01

Hi scott,

We should modify the version of Edge01 into Version 8.3 (Build 389.2), because we have updated Edge01 to Exchange 2007 SP3 CU15.

If there are any questions regarding this issue, please be free to let me know.  

Best Regard,

Jim