• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 44
  • Last Modified:

install failure upgrading exchange from 2013 to 2016

Due to replacing all systems on a site, part of this was to upgrade a exchange 2007 to 2016, due to the fact 2007 couldn't be upgraded directly to exchange 2016 we  Migrated the exchange 2007 to a temporary licenced exchange 2013 the to upgrade the 2013 copy to exchange 2016, unfortunately it seems now  when we try to upgrade the 2013 to 2016 we get a install failure has the exchange 2016 wont recognise the 2013 licence .

we are looking for a solution to solve this problem.
0
Alan Duck
Asked:
Alan Duck
1 Solution
 
timgreen7077Exchange EngineerCommented:
are you attempting to run an upgrade on the actual exchange 2013 server? if that is the case you can't do that. you will need to install exchange 2016 on its own server.
0
 
Alan DuckAuthor Commented:
the 2016 exchange is installed on a different server
0
 
timgreen7077Exchange EngineerCommented:
The product key for Exchange 2013 and 2016 are different. You can still install Exchange 2016 and you have 180 days to use it until you get the correct product key.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Alan DuckAuthor Commented:
true but the exchange 2013 has run passed the 180 days and now the exchange 2016 errors when it gets to the sage when it has to connect to the exchange 2013
0
 
timgreen7077Exchange EngineerCommented:
there is no connection between the 2 server. what is the error you are getting
0
 
Alan DuckAuthor Commented:
I Have re-run the 2016 install and I am getting the following error, File attached
exchange2016.png
0
 
timgreen7077Exchange EngineerCommented:
make sure you have run and setup all exchange 2016 prerequisites.  see link for what must be done in advance.

https://technet.microsoft.com/en-us/library/bb691354(v=exchg.160).aspx
0
 
IvanSystem EngineerCommented:
Hi,

the error that you receive is: Database is mandatory on Usermailbox.

That means that you have some mailbox that does not have Database (homeMDB) attribute filled.
To check, run this command: Get-Mailbox -Arbitration | Select Name, Database
If there is a mailbox with no Database, then use following command to rehome it to some database:
Set-Mailbox <mailbox_name> -Database <DB_name>

Regards,
Ivan.
0
 
Marshal HubsEmail ConsultantCommented:
0
 
Alan DuckAuthor Commented:
We found a number mailboxes had cruption after the Migration from exchange 2007, when we removed the cruption the exchange upgrade work fine
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now