So here is a brief of the issue we are experiancing.

We are currently rolling out an entirely new domain using Server 2012 and exchange 2013.  After the initial install of 2 domain controllers Dc01, dc02, and an exchange server; exchange01.  We were getting alot of instability.  Outlook clients kept disconnecting, ecp/owa/powershell at times stopped working, exchange kept losing connectivity to active directory.  After spending a few days working out these issues (we got everything except the outlook client connectivity fixed), we decided to re-install exchange using the method here since our mailbox database was on a seperate partition and we've already created over 150 mailboxes, 250 groups, and 100 contacts:

https://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx

During the installation it failed during the "Mailbox Role: Client Access service".  In the exchangesetup.log the error shown is:

        

[03/27/2015 17:33:36.0515] [1] Processing component 'Client Access Services Configuration' (Configuring Client Access services.).
[03/27/2015 17:33:36.0515] [1] Executing: 
          $BEVdirIdentity = $RoleNetBIOSName + "\Autodiscover (Exchange Back End)";
          get-AutodiscoverVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController | remove-AutodiscoverVirtualDirectory -DomainController $RoleDomainController;
          new-AutodiscoverVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController -WSSecurityAuthentication:$true -BasicAuthentication:$false -WindowsAuthentication:$true;

[03/27/2015 17:33:36.0530] [2] Active Directory session settings for 'Get-AutodiscoverVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC01.domain.lan', Preferred Global Catalog: 'DC01.domain.lan', Preferred Domain Controllers: '{ DC01.domain.lan }'
[03/27/2015 17:33:36.0530] [2] User specified parameters:  -ShowMailboxVirtualDirectories:'True' -Identity:'EXCHANGE01\Autodiscover (Exchange Back End)' -DomainController:'DC01.domain.lan'
[03/27/2015 17:33:36.0530] [2] Beginning processing get-AutodiscoverVirtualDirectory
[03/27/2015 17:33:36.0546] [2] Active Directory session settings for 'Remove-AutodiscoverVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC01.domain.lan', Preferred Global Catalog: 'DC01.domain.lan', Preferred Domain Controllers: '{ DC01.domain.lan }'
[03/27/2015 17:33:36.0546] [2] User specified parameters:  -DomainController:'DC01.domain.lan'
[03/27/2015 17:33:36.0546] [2] Beginning processing remove-AutodiscoverVirtualDirectory
[03/27/2015 17:33:36.0546] [2] Searching objects "EXCHANGE01\Autodiscover (Exchange Back End)" of type "ADAutodiscoverVirtualDirectory" under the root "$null".
[03/27/2015 17:33:36.0561] [2] Previous operation run on domain controller 'DC01.domain.lan'.
[03/27/2015 17:33:36.0561] [2] Previous operation run on domain controller 'DC01.domain.lan'.
[03/27/2015 17:33:36.0561] [2] Preparing to output objects. The maximum size of the result set is "Unlimited".
[03/27/2015 17:33:36.0561] [2] [ERROR] The operation couldn't be performed because object 'EXCHANGE01\Autodiscover (Exchange Back End)' couldn't be found on 'DC01.domain.lan'.
[03/27/2015 17:33:36.0577] [2] [ERROR] The operation couldn't be performed because object 'EXCHANGE01\Autodiscover (Exchange Back End)' couldn't be found on 'DC01.domain.lan'.
[03/27/2015 17:33:36.0577] [2] Ending processing get-AutodiscoverVirtualDirectory
[03/27/2015 17:33:36.0577] [2] Ending processing remove-AutodiscoverVirtualDirectory
[03/27/2015 17:33:36.0593] [2] Active Directory session settings for 'New-AutodiscoverVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC01.domain.lan', Preferred Global Catalog: 'DC01.domain.lan', Preferred Domain Controllers: '{ DC01.domain.lan }'
[03/27/2015 17:33:36.0593] [2] User specified parameters:  -WebSiteName:'Exchange Back End' -Role:'Mailbox' -DomainController:'DC01.domain.lan' -BasicAuthentication:'False' -WSSecurityAuthentication:'True' -WindowsAuthentication:'True'
[03/27/2015 17:33:36.0593] [2] Beginning processing new-AutodiscoverVirtualDirectory
[03/27/2015 17:33:36.0608] [2] Searching objects "Exchange01.domain.lan" of type "Server" under the root "$null".
[03/27/2015 17:33:36.0686] [2] Previous operation run on domain controller 'DC01.domain.lan'.
[03/27/2015 17:33:36.0702] [2] Processing object "EXCHANGE01\Autodiscover".
[03/27/2015 17:33:46.0421] [2] The properties changed on the object '' (CN=Autodiscover (Exchange Back End),CN=HTTP,CN=Protocols,CN=EXCHANGE01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CSTLTL,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=lan) are: "{ MetabasePath[msExchMetabasePath]='IIS://EXCHANGE01.domain.lan/W3SVC/2/ROOT/Autodiscover', ExtendedProtectionSPNList[]={  }, AuthenticationMethodFlags[msExchInternalAuthenticationMethods]='Ntlm, WindowsIntegrated, WSSecurity', AuthenticationMethodFlags[msExchExternalAuthenticationMethods]='Ntlm, WindowsIntegrated, WSSecurity', Id[distinguishedName]='EXCHANGE01\Autodiscover (Exchange Back End)', InternalAuthenticationMethods[msExchInternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated', 'WSSecurity' }, ExternalAuthenticationMethods[msExchExternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated', 'WSSecurity' }, OrganizationId[msExchOURoot, msExchCU]='' }".
[03/27/2015 17:33:46.0421] [2] Saving object "EXCHANGE01\Autodiscover (Exchange Back End)" of type "ADAutodiscoverVirtualDirectory" and state "New".
[03/27/2015 17:33:46.0468] [2] Previous operation run on domain controller 'DC01.domain.lan'.
[03/27/2015 17:33:48.0896] [2] Searching objects "EXCHANGE01\Autodiscover (Exchange Back End)" of type "ADAutodiscoverVirtualDirectory" under the root "$null".
[03/27/2015 17:33:48.0896] [2] Previous operation run on domain controller 'DC01.domain.lan'.
[03/27/2015 17:33:48.0896] [2] Ending processing new-AutodiscoverVirtualDirectory
[03/27/2015 17:33:48.0911] [1] The following 1 error(s) occurred during task execution:
[03/27/2015 17:33:48.0911] [1] 0.  ErrorRecord: The operation couldn't be performed because object 'EXCHANGE01\Autodiscover (Exchange Back End)' couldn't be found on 'DC01.domain.lan'.
[03/27/2015 17:33:48.0911] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'EXCHANGE01\Autodiscover (Exchange Back End)' couldn't be found on 'DC01.domain.lan'.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.GetObjectWithIdentityTaskBase`2.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[03/27/2015 17:33:48.0911] [1] [ERROR] The following error was generated when "$error.Clear(); 
          $BEVdirIdentity = $RoleNetBIOSName + "\Autodiscover (Exchange Back End)";
          get-AutodiscoverVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController | remove-AutodiscoverVirtualDirectory -DomainController $RoleDomainController;
          new-AutodiscoverVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController -WSSecurityAuthentication:$true -BasicAuthentication:$false -WindowsAuthentication:$true;
        " was run: "Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'EXCHANGE01\Autodiscover (Exchange Back End)' couldn't be found on 'DC01.domain.lan'.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.GetObjectWithIdentityTaskBase`2.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[03/27/2015 17:33:48.0911] [1] [ERROR] The operation couldn't be performed because object 'EXCHANGE01\Autodiscover (Exchange Back End)' couldn't be found on 'DC01.domain.lan'.
[03/27/2015 17:33:48.0911] [1] [ERROR-REFERENCE] Id=ServicesComponent___a8409d9e1e024948a9cf2805368de7dd Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[03/27/2015 17:33:48.0911] [1] Setup is stopping now because of one or more critical errors.
[03/27/2015 17:33:48.0911] [1] Finished executing component tasks.
[03/27/2015 17:33:48.0943] [1] Ending processing DisasterRecovery-ClientAccessRole
[03/27/2015 17:33:48.0958] [0] CurrentResult console.ProcessRunInternal:198: 1
[03/27/2015 17:33:48.0958] [0] CurrentResult launcherbase.maincore:90: 1
[03/27/2015 17:33:48.0958] [0] CurrentResult console.startmain:52: 1
[03/27/2015 17:33:48.0958] [0] CurrentResult SetupLauncherHelper.loadassembly:452: 1
[03/27/2015 17:33:48.0958] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[03/27/2015 17:33:48.0958] [0] CurrentResult main.run:235: 1
[03/27/2015 17:33:48.0958] [0] CurrentResult setupbase.maincore:396: 1
[03/27/2015 17:33:48.0974] [0] End of Setup
[03/27/2015 17:33:48.0974] [0] **********************************************

I'm guessing based of this log, exchange did not have everything in active directory that was required which is why we were having problems in the first place.  

My question at this point is, what are our options.  Are we looking at a full rebuild of everything, clean out active directory for exchange and install exchange fresh, or can we just re-install exchange and run the ad prep/schema process to rebuild the exchange part of active directory.

Thanks in advance for any assistance.

Also, I should mention.  I do have the option to go back to a state where all services (ecp,owa,powershell, etc) work except autodiscover.  If there is a way to just rebuild the active directory objects for the autodiscover back end that is missing.

Hello

check with adsiedit for entry like:

Maybe not the answer you're looking for, but if you have a good backup of AD (which I hope you took) prior to the intro of Exchange you could do a restore of AD to that point and start Exchange all over again.  Sounds like you've got a lot of time into this already, and to keep t/shooting it will take even longer.  At what point is the t/shooting no longer worth it?

Sneff-Not sure where I need to look for this.  But I don't see it.

Bondoo- thats a good point.  I think I'm going to try that, we do have backups of our DC's while they were in working order.  I'll try restoring those and doing another recovery install of exchange.  Hopefully that will work.  I'll let you know how it goes.

Thanks a ton, always good to have fresh ideas.

Hello

open adsiedit--> connect to configuration and go to:

CN=HTTP,CN=Protocols,CN=EXCHANGE01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=lan

Sneff- I looked there, I don't see any HTTP entries, I think this might be part of the problem.  This is all I see under Configuration:



I'm going to try Bondoo's suggestion and restore AD then try again.

Thanks for your suggestions.

Hello

but double klik to services and ....

yeah, still not there, sorry

Looked in these directories also, no HTTP anywhere.

use double klik to open map and go under, like browsing in file server maps. :)

CN=Microsoft Exchange = double klik to Microsoft Exchange and...