Okay, so I think I've got a bit of a mess here.  After initially trying to install Exchange 2013 RTM, (and set up a DAG), on two Windows 2012 (VMware) servers, I then attempted to install CU9, (which failed),From there, I ended up getting things to the point that I decided that since this is a new production Exchange environment, (all email data still on current Exchange 2007 Server,) I'd just scrap the whole thing and start over from the ground up.

I had everything ready to go again and I just decided to install CU9 right out of the gate, (which is probably what I should have done the first time).  I received an error that Exchange was in an inconsistent state and that I would need to install using the recovery mode:

"Error: Setup previously failed while performing the action "DisasterRecovery". You can't resume stup by performing the action "Install"."

From there, I open a cmd prompt "with admin" and run Setup.exe /Mode:RecoverServer /IAcceptExchangeServerLicenseTerms

This also failed.  Among the errors in the log file was "An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Active Directory server  is not available. Error message: Active directory response: The supplied credential is invalid.."

It's now to the point that I can't even "uninstall" this failed installation of Exchange 2013 CU9.  I now get "Error: Setup previously failed while performing the action "DisasterRecovery". You can't resume setup by performing the action "Uninstall"."

I'd like to try to not have to start all over with my VM's, (because, to be honest, I don't think I'll get a clean install even after doing this.  I suspect there's something in my AD that's "leftover" from the previous setup.  I made everything the same with my new VM's, (Names, disk, memory, CPU, etc...)

Thinking I may need to open a case with MS on this one.  Any ideas?

Thinking I may need to open a case with MS on this one.  Any ideas?

Probably not a bad idea; it might take some dissection of AD to get you going again.  Is restoring AD to a previous point in time an option?

I don't know what the repercussions of doing that would be, but I don't think it's something I want to do.

Understood. I would suggest opening a ticket with MS support then. They should be able to resolve this for you. Whatever the outcome, it's always a plus when community members share their resolutions so others can benefit. Good luck.

Stupid question incoming...did you run /PrepareAD and /PrepareSchema in the same AD site that is running the FSMO roles BEFORE trying to implement CU9?  CU9 will require it unless you are coming from CU7.  Even though in theory it should happen automatically if you have the correct permissions, I ran into an issue, which was resolved by preparing the AD and Schema ahead of time.  Just an idea.  Good luck.

• Edited by slrobb 9 hours 31 minutes ago grammar