Inplace upgrade Windows 2008 to Windows 2012 with Exchange just unistalled.

We have two server: Apollo and Perseo (temporary server)
Apollo has Windows 2008 and Exchange 2010
Perseo has Windows 2012 and Exchange 2016
We migrated all mailboxes from 2010 to 2016 so we can remove Exchange 2010 from Apollo,

Is it possible to uninstall Exchange 2010 from Apollo and make a Windows 2012 upgrade in place without a format??, then install Exchange 2016 in Apollo and migrate back all mailboxes? We prefer the simple way of in place upgrade, if not, we need to spend a lot extra time moving all the roles to one server and then back to Apollo.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Are either Apollo or Perseo DC's?  And if so, is the DC marked as a Global Catalog?

Are you making a bit level change; e.g. - Apollo has 2008 32-bit, installing 2012R2 64-bit?

marpanetAuthor Commented:
Apollo is DC, also I have another server "Ares" as a DC, Perseo is not DC..
As Global Catalog, I am not so sure if it´s maked.
No bit leve change, all servers are 64 bit.
Apollo is 2008 R2 64bit and going to 2012 R2 64bit.
Lee W, MVPTechnology and Business Process AdvisorCommented:
It's foolish.

Even if you can get this to work, your system is full of legacy settings from Windows and Exchange.  "Simple"?  No, it's complicated and difficult, unsupported, and no professional would do this in my experience and opinion.  Don't do it.  Perform a proper, SUPPORTED migration!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

TG TranIT guyCommented:
Mr. Lee W is correct in warning you against it.

Working with small outfits, there are many "out of the box" attempts such as yours.  I believe Apollo is a beefy box that you don't want to send to early retirement.  Perseo is a less powerful box - not meant to be a permanent home for Exchange.  What you wanted to do can be done - but like Lee W said, you are at the fringe and should reconsidered.  If you want to proceed, you would need to do the following on Apollo:
1.  Uninstall Exchange
2.  Demote it to domain server (remove GC and DC)
3.  Wipe and install clean Win2012 (better & cleaner option than in-place upgrade, but if you want to upgrade, you can try)
4.  DCPromo it up (make sure your forest is ready for W2012, and make sure AD has no records of the old W2008 Apollo)
5.  Install Exchange and move mailboxes
As Apollo is a DC, I definitely would *not* recommend an in-place upgrade (as stated above by Lee).  Your best bet is to migrate the FSMO roles (a two minute process) and ensure that you have a healthy domain.

One you have validated a healthy domain, move any files and/or shares to another server.  Demote your current server, wipe the hard drives and perform a fresh install.

You could also perform an inplace upgrade after the server is demoted, but I would really recommend a wipe and fresh install.  Performing a fresh install would allow for you to address the differences in the operating systems and their requirements whereas an upgrade would present challenges with regards to implementing modifications to the OS configuration that allow for you to take advantage of changes in the operating systems.  One such change deals with the introduction of ReFS (which can be used instead of NTFS) in Server 2012.

As for the Global Catalog aspect, in the Active Directory Sites and Services snap-in, expand your server objects.  Right-click on the NTDS Settings container for the server and select properties.Capture.JPGWhich the properties open, check to see if the Global Catalog box is checked.Capture.JPGNot all DC's have to be Global Catalogs, but you do need at least one active DC marked as a Global Catalog since you have Exchange in your environment.

marpanetAuthor Commented:
Ok, just to see if I am on the right track..
Just moved all FSMO roles to another server "Ares", the other server does has the Global Catalog tick, and took away the Global Catalog on "Apollo", so how can I be sure I wont have an unhealthy Active Directory?
Microsoft has a wealth of information and tools that are used to perform Active Directory Health checks.  The first one you should familiarize yourself with is DCDIAG.

This tool is primarily used to provide a top-down view of the overall health of AD (but can be used to produce granular reports).  When you identify a problem area, that is when you will need to start using more specialized tools; e.g. - FRSDiag for File Replication Service problems.

marpanetAuthor Commented:
I have a question...
I removed the Global Catalog from the "Apollo", and my Exchange server stopped working.....
eventhough "Ares" has the Global Catalog.... do I need to tell Exchange that Ares is the only Global Catalog???
Lee W, MVPTechnology and Business Process AdvisorCommented:
Exchange should locate the new global catalog but it can take 30 minutes or so.
marpanetAuthor Commented:
Ok, this saturday I will remove Global Catalog from "Apollo", restar the server, restard de "Exhange server", and when everything seems working, then I will demote "Apollo"....  I am scared hehehehe
marpanetAuthor Commented:
I found out this... not sure if it is real.... but if it keeps failing, I will try it out:
If nothing else works try this!

Copied from Mr Johnson:

In exchange 2013 there is now a setting that requires you to have at least 50% of your domain controllers global catalog servers.  Without 50% of your DC's being GC's you will get event id 2069, 2060, and 2070 and exchange will fail to find other global catalogs or Domain Controlers in your organization.  Took me 80 hours to fix this problem.  Thought id share and save others some headaches.

 This can be fixed by editing the "Microsoft.Exchange.Directory.TopologyService.exe.config" file

 Look for this line:
 MinPercentageOfHealthyDC = "10"

 Also add this line:
 MinSuitableServer = "1"
Lee W, MVPTechnology and Business Process AdvisorCommented:
Aren't all your DCs also GCs?
marpanetAuthor Commented:
Sorry for the delay...
Because I am new at this "Active Directory" thing..., I encountered a problem where Ares even dough it said it was a domain controller, it wasn’t, a proper replication of the "sysvol and netlong" wasn’t present, so every time I turned off Apollo everything went down.  so now, I corrected the problem and now I can safely demote apollo to perform a clean install.

Thank you very much for pointing me in the right direction.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.