Link to home
Start Free TrialLog in
Avatar of SLPowers
SLPowersFlag for United States of America

asked on

SBS 2011 to Server 2012 with Exchange 2013

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.
Avatar of Exchange_Imran
Exchange_Imran

Hello,

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.

Regards
Imran Shariff
Avatar of SLPowers

ASKER

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?
SOLUTION
Avatar of Exchange_Imran
Exchange_Imran

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
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.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Good to hear that the issue is resolved.

Regards
Imran Shariff
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
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.