I’ve been on a client site today fighting with an Exchange 2010 install problem.
I’ll not bore you with the details of how I got there but I ended up having to build a new server to replace the one I built yesterday(!).
The theory was simple:-
- Install a new Server with the same name as the failed one I was replacing
- Reset the AD computer account & join the new server to the domain
- Install all the prerequisites for Exchange 2010 SP1
- Run Setup /m:RecoverServer to install Exchange with the same configuration as the failed server using the AD configuration.
This is all documented in http://technet.microsoft.com/en-us/library/dd876880(v=exchg.141).aspx
All went well until, unfortunately, the MSExchangeTransport Service failed to start due to network issues. Now you would think that you sort out the issue then run the same command again wouldn’t you?
If you do you are presented with the error “Setup previously failed while performing the action DisasterRecovery. You can’t resume setup by performing the action install”
Searching around I found http://technet.microsoft.com/en-us/library/bb123496(EXCHG.80).aspx which sounded good but if you look in the Registry for the key HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\v8.0 as specified you will find it doesn’t exist for Exchange 2010.
After a lot more time banging my head against the monitor I worked out that the key is actually HKEY_LOCAL_MACHINE\Software\Microsoft\ExchangeServer\v14 and that Exchange setup won’t be fooled by renaming keys as suggested.
I exported the keys and then looked in each “role” folder (MailboxRole, HubTransportRole, etc) and deleted any key labelled “Watermark” and “Action” – these are what the RecoverServer process looks for.
I now can successfully re-run the setup /m:RecoverServer process and get on with configuring the Exchange Server after a very frustrating day.