Exchange 2013 Upgrade - 2007 / 2010 already in environment
Posted on 2014-02-24
We recently started working with a client that has a 200 user Exchange 2007 environment. In doing a discovery in their environment, I found that a VM in Hyper-V was created and Exchange 2010 was installed.
Currently, the client wants to have Exchange 2013 installed into the environment. In normal situations, I would run through the typical process to migrate from 2007 to 2013. However, with the additional VM in the environment with Exchange 2010 installed, I'm a bit wary of this environment.
In checking out the Exchange 2010 environment, there is no mail routing through the environment; in fact, the VM has been powered off. However, in doing the Exchange Profile Analyzer, it did detect that the Exchange 2010 environment was enabled and it wanted it powered online in order to evaluate it.
My current thought is to do a straight uninstall of Exchange 2010 some evening and then verify all is working in relation to mail routing. I don't see any issues with this, as I've done a thorough check to verify Exchange 2010 isn't doing anything, outside of the two mailboxes that the on-site admin created in the Exchange 2010 environment.
Do you think this is the correct route? Just clean out 2010 and hope for the best on the upgrade? Especially since they want to use the same VM for Exchange 2013.
A very strange situation, but I guess the on-site admin wanted to check out Exchange 2010 and installed an evaluation copy into the production environment. Definitely not my first choice of options and I'm not overly thrilled about it.
Anyway, let me know if anyone has any insight on this. If a straight uninstall of Exchange 2010, removing it/connectors/etc. from the environment would have any adverse effect on the Exchange 2007 environment and the installation of Exchange 2013 from there. Thank you!