SBS 2011 to Server 2012 with Exchange 2013

Posted on 2013-11-15
Medium Priority
Last Modified: 2013-11-25
So we had a 2003 domain and exchange server migrated to sbs2011, we are now attempting to migrate from SBS 2011 to Server 2012 with Exchange 2013.

SBS 2011 has SP1 installed
Exchange 2010 SP3 RU 1 - installed
Forest and domain 2008 R2
No Edge Servers

Here's our problem:
Exchange 2013 does not recognize that exchange 2010 SP 3 is installed.  

Does anyone know why it does not see that exchange 2010 SP3 is installed, let alone even after RU 1 has been installed as well?

Many thanks for the help.
Question by:SLPowers
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3

Expert Comment

ID: 39651447

Most probably this issue occurs when one of your server in the organization hasn't been upgraded to exchange 2010 SP3, this issue mostly occurs when you have an edge server where you need to upgrade that as well but in our situation we don't have an Edge Transport server. Seems to be somewhere in AD the version has not been updated.

Run get-exchangeserver and verify the service Pack and build number and confirm that it is upgraded to exchange 2010 sp3 as you mentioned RU1

Now go to registry and verify the configured and unpacked version of Mailbox,Hub and CAS role in the existing exchange 2010 SP3

If they are also upgraded then try running EXBPA once most probably you will get some information on this error message.

If all the above is fine then reboot the server once and try one more time.

Imran Shariff

Author Comment

ID: 39651526
When I run Get-exchangeserver it says the admin version is 14.1, but EMC states that it is SP3. (I don't recall the exact numbers, but i did confirm that they reflected SP3 via the version)

I will look into the registry shortly.  Does the above give any further thoughts of how to proceed?

Assisted Solution

Exchange_Imran earned 2000 total points
ID: 39652177

I have exchange 2010 environment in my lab setup and exchange 2010 is upgraded to exchange 2010 SP3, when i hit the below command this is what the result i get.

[PS] C:\Windows\system32>Get-ExchangeServer |fl Name,ServerRole,Edition,AdminDisplayversion

Name                : Exchange2010
ServerRole         : Mailbox, ClientAccess, UnifiedMessaging, HubTransport
Edition               : Standard
AdminDisplayVersion : Version 14.3 (Build 123.4)

The Admin version has to display the Latest Service Pack with the build number

In your issue Looks like Exchange 2010 SP3 is partially installed that is why Exchange management Console displays 14.3 where shell displays 14.1

There few more ways to verify you exchange 2010 Service Pack and build Number, go to the below registry


In the right pane you will see two two String Values "Configured Version" and "Unpacked Version"

If the configured version and unpacked version shows 14.3 on all the Server roles then it is upgraded to exchange 2010 Sp3

Second Way:

Open the Bin directory, by default it will be in this location

C:\Program Files\Microsft\Exchange Server\v14\Bin

Go to the properties of any dll files click details tab and verify the version, if this shows 14.3 then exchange is upgraded to exchange 2010 Sp3

Third Way:

Run EXBPA, this will clearly says that the exchange is upgraded correctly or not.

After confirming, if exchange 2010 Sp3 is not properly installed rerun the setup to fix this issue.

Imran Shariff
Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.


Author Comment

ID: 39653426
Excellent information, Thank You!  I have reviewed the .Dll's and they give 14.3 (1234)
The Registry states 14.3 (1234) on all Server roles.
The PS command state 14.1 for the admin. ( I have read that this can be different, and is only the minimum version required to administer exchange)
EXBPA states the version is 1937866970

I believe that the setup should be run again, unfortunately when i run it, it states that SP3 is installed, and will only allow me to add Roles (only role left is unified messaging)  

If I attempt to run a repair through Programs and feature I receive the following error:
"The LP Versioning file has an invalid Value."
If you look at the setup log it states the files is not there.
However, The file is in the Bin directory, and from all accounts it has the date when SP3 was installed on it.

So my new question now becomes, if i must repair the SP3 installation, how do i get past the LP versioning error.  I have run the LP update utility and it completed successfully, I have attempted to get the SP1 LP and use it (I know it was a long shot) It's looking for it in a directory that it apparently is not in.  I have run the setup /lp: and pointed it to the LP files in the Extracted SP3 update directory still without success.

Any Idea's?  This is running on a hyper-V machine so it's a little cumbersome for me to stick an Iso as an additional drive with the original SBS 2011, especially since it was installed via a VHD.

Thank You in advance for the additional assistance.

Accepted Solution

SLPowers earned 0 total points
ID: 39658198
Okay so I got Microsoft involved.  Here is what they did.  (BTW get-exchangeserver version does need to be 14.3)

Open ADSI Edit.
Hammer down through Domain\Administrative groups\exchange administrative group\servers\(exchange Server Name)

Right click on the CN=(Exchange server name) and select properties

You will need to edit the Attribute "serialNumber" in the Modify Attributes button.
If it still says "Version 14.1 (Build 30218.15)  or anything other than "Version 14.3 (Build 30123.4) Then Exchange 2013 installer will fail  with the an error that basically states "Exchange 2013 does not recognize that exchange 2010 SP 3 is installed."

Another thing to do inside of Admin CMD Prompt is: repadmin /syncall /adeP

This command will verify the Domain Controller Topology.

Everyone who commented was right on the money, check everything they said to check.  It just happens that this is suppose to be my particular problem.  Now to fix DC replication issues that they found as well.

Expert Comment

ID: 39658725
Good to hear that the issue is resolved.

Imran Shariff

Author Closing Comment

ID: 39671137
Each of these proved to be good places to look and verify information, even MS checked them.  The Serial number solved it for me, and when I did the get-exchangeserver command it was updated to 14.3

Author Comment

ID: 39676517
Additionally, so that it is posted somewhere on the web.  If Exchange 2010 is installed with the wrong Organization.  There is a way to solve it using the LegacyDN tool.  You may need to use a combination of it plus the following command:

 Eseutil /mh "Exchange Database file name.edb"

After which all the mailboxes will be in a disconnect state, and must be reconnected to the appropriate user.  47 users didn't take but 15-20 minutes for me, but if you're in an enterprise scenario...you may want to take the standard advise and uninstall then re-install.

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

There are times when we need to generate a report on the inbox rules, where users have set up forwarding externally in their mailbox. In this article, I will be sharing a script I wrote to generate the report in CSV format.
New style of hardware planning for Microsoft Exchange server.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the adminiā€¦
Suggested Courses

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question