Recover a Lost Exchange Server 2013 on a windows server 2012r2

Fuentes: https://technet.microsoft.com/en-us/library/dd876880%28v=exchg.150%29.aspx
Fuentes: https://technet.microsoft.com/en-us/library/bb691354%28v=exchg.150%29.aspx

Casi imposible restaurar en el mismo servidor después de un fallo del instalador del Cumulative Update 7

Al final varios pasos y repeticiones llevaron a un estado funcional, pero incapaz de instalar el antispam de symantec messaging

Si estás presuroso por correr el recover, debes primero Ask your self if you deleted the AD Object corresponding to exchange 2013 server, if you d you'll have a infinite type of errors, until you got the 0x80070005 COM Error on FIPS that cannot be fixed.

So if you run the setup /m:Recoverserver after reading all this things. DONT RUN IF YOU DELETED DE AD OBJECT YOU LL HAVE TO FORMAT

On failed recovery setup you must do this:

- Verify that you re using a Member Server not DC

- If you deleted the AD Object you must reinstall de server with same name and join to domain. 

- And DONT FORGET to ADD it to Builtin Exchnage enterprise Servers and Exchange Server in Exchange OU

I have run on a DC the preparation domain tools again

setup /p /IAcceptExchangeServerLicenseTerms

setup /pad /IAcceptExchangeServerLicenseTerms

setup /ps /IAcceptExchangeServerLicenseTerms

Dont forget the RSAT-ADDS-Tools on Prerequisites

Stop and disable all Exchange Services

Reboot

Cleanup IIS application pools

Cleanup Exchange 

Delete all Exchange folders from program files (take care of your edb mailbox)

0x80070005 –E_ACCESS_DENIED

Access denied  by  DCOM security.
The user does not have remote access to the computer through DCOM. Typically, DCOM errors occur when connecting to a remote computer with a different operating system version.
Give the user Remote Launch and Remote Activation permissions in dcomcnfg.  Right-click My Computer-> Properties  Under COM Security, click "Edit Limits" for both sections.  Give the user you want remote access, remote launch, and remote activation.  Then go to DCOM Config, find "Windows Management Instrumentation", and give the user you want Remote Launch and Remote Activation. For more information, see Connecting Between Different Operating Systems

Change Swap to twice of RAM

Register:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine]
"ApplicationBase"="C:\\Windows\\System32\\WindowsPowerShell\\v1.0"
"RuntimeVersion"="v2.0.50727"
"ConsoleHostAssemblyName"="Microsoft.PowerShell.ConsoleHost, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=msil"
"ConsoleHostModuleName"="C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\Microsoft.PowerShell.ConsoleHost.dll"
"PowerShellVersion"="2.0"
"PSCompatibleVersion"="1.0, 2.0"
"CTPVersion"="15"

delete next services (reboot)
FMS
SearchExchangetracing
MSEXCHANGE*
HostConstrollerService

empty IIS and apps (be careful with RPc sites)


create 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\Pickup]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\Setup]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\FIP-FS]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\FIP-FS\SQM]

Adding Subnet to Sites and Directory

Stop Firewall Windows

On DC 

Add Windows 2008 R2 SP1

Rerun 

Delete exchange object 

rerun

setup /IacceptExchangeserverLicenseTerms /SourceDir:C:\temp\exch2013\cu7 /m:Recoverserver /InstallWindowsComponents 

------------------------
ENTRE OTROS ERRORES

I got a windows update settingscontent-ms error, which avoid to start Windows Update Screen (i booted the server after started de "Check for Windows Updates screen"

Here's one way to find what is not working:

cd /d  %LocalAppData%\Packages

dir/a/b/s  *.settingscontent-ms  |  find  "Classic_{36e"  |  clip

Then open a Notepad window and do a Ctrl-o Ctrl-v and Enter

Somehow I think the failure may have more to do with the program which "executes" the .settingcontent-ms  file extension...

C:\Users\Admin\AppData\Local\Packages>assoc .settingcontent-ms
.settingcontent-ms=SettingContent

C:\Users\Admin\AppData\Local\Packages>ftype SettingContent
File type 'SettingContent' not found or no open command associated with it.

What a surprise!  OTOH consistency found in W8's continual obfuscation and unhelpfulness.  ; }

Reset the computer account for the lost server. For detailed steps, see Reset a Computer Account.

Install the proper operating system and name the new server with the same name as the lost server. Recovery won't succeed if the server on which recovery is being performed doesn't have the same name as the lost server.

Join the server to the same domain as the lost server.

Install the necessary prerequisites and operating system components. For details, see Exchange 2013 system requirements and Exchange 2013 prerequisites.

Log on to the server being recovered and open a command prompt.

Navigate to the Exchange 2013 installation files, and run the following command.

1. Setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms
   

2. After Setup has completed, but before the recovered server is put into production, reconfigure any custom settings that were previously present on the server, and then restart the server.

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, RSAT-ADDS-Tools

Install-WindowsFeature ADLDS

u've installed the operating system roles and features, install the following software in the order shown:


.NET Framework 4.5.2


Windows Management Framework 4.0 (included with Windows Server 2012 R2)


Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit