Removing legacy exchange from network where AD was changed behind Exchange's back
Network with two Windows Server 2008 R2 domain controllers and Exchange 2007. Here is the problem:
There are three servers that handle exchange: one for the information store, one for edge, one for owa. All three servers have been shut down for a week.
NOTE: THESE SERVERS ARE NOT BEING USED. THE COMPANY MOVED TO OFFICE 365 MONTHS AGO AND JUST NEVER GOT AROUND TO REMOVING THEM.
In the past three days, while the servers were shut down, one of the 2008 R2 DC's crashed and needs to be manually removed. After that, a 2012 R2 DC was added to the domain.
Question: Is it acceptable to turn the three Exchange servers back on and gracefully uninstall exchange with all the AD changes made after the install of a 2012 R2 DC (the forest functional level was moved from 2000 to 2008, also) or do we have to crank up ADSI Edit and manually remove Exchange from the domain?
Before anyone says anything, I'm not the guy who did all this. I'm the consultant hired to clean it up. :)
James
ExchangeWindows Server 2012Windows Server 2008Active Directory
The only other "gotcha" I can think of would be public folders. If you had public folders in use in Exchange 2007, IIRC, it will complain and not allow you to remove/dismount the public folder database (and thus not uninstall Exchange) unless you've moved the public folders somewhere else. I think there are probably tools you should be able to use to remove the public folders if that's the case. There used to be a tool called PFDAV Admin that you could use to manage this process, but I don't know if it's available any more. I do have a copy of it in my archives if you need it and can't find it elsewhere.
3. Uninstall the Exchange 2007 Hub Transport server role.
Remove this server from any send connector before.
4. Uninstall the Exchange 2007 Mailbox server role (Information Store).
Remove databases before.