i lost one of my CA 2013 servers

installed  new server with same name and config upon unning Setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms

but getting this message

Our environment has Exchange 2013 On-line with CU6

I'm having a few issues doing a cutover migration from our internal on-premises Microsoft Exchange to a hosted Exchange on Office365.

I'm trying to do the "Prepare for Migration" step covered here:https://support.office.com/en-ca/article/Perform-a-cutover-migration-of-email-to-Office-365-9496e93c-1e59-41a8-9bb3-6e8df0cd81b4#CreateEndpoint I'm trying to install Outlook Anywhere and have Office365 be able to access our emails.

The problem that I'm having is related to the certificates installed. Our internal on-premises Exchange FQDN is of machine.company.local, not machine.company.com, and it's using the self-signed certificate that it generated.

Steps I've attempted:

1. Install a .com version of our third party certificate. This creates the 12014 errors:

MSExchangeTransport 12014 - " Microsoft Exchange could not find a certificate that contains the domain name machine.company.local in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector Default TOINTERNET with a FQDN parameter of machine.company.local. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.

Additionally, Office365 can't connect to our internal exchange server.

How would I go about this?

On another note, will Microsoft be okay with a third-party signed .local certificate?

Hi

i have installed an exchange 2013 cohabitation with exchange 2010 for migration. outlookanywere,ecp,owa, autodiscovery...etc are configurered

when i try to connect to the eac or owa internaly its work, but when i try to do externaly https://mail.mydomain.com/ecp?exchver=15

i have error 302, 301 to many redirections

how can i fix this

thanksin advance

Hello,

I have an odd situation where we are preparing 2 exchange 2013 servers to migrate 2010 servers to 

so currently:

2x Exchange 2010 (with dag)

2x Exchange 2013 (with dag).

Now it's behaving extremely odd when it comes to ECP for the 2013 servers.

randomly it works and doesn't work.

i generally try it from localhost on both 2013 servers, and individual server ip's from lets say 4 or 5 places.

all same login, and admin user is inside mailbox db DAG cluster.

now the problem:

it randomly pops up auth.owa error 500 

when i say random i truly mean random, sometimes everything 100% works, i am able to login 100% from all servers.

then i check back lets say 2 hours later.. some obtain auth.owa errors while others work.

What i tried:

- I rebuild OWA (first with reset, then with remove and re-add method) on both 2013 servers.

- removed killbit file from 2013's

- rebuild exchange 2013's (just exchange it self).

- checked heartbeat monitor boxes and removed the null values.

----------------------------------

It's safe to say i am kind of lost on what to try next. 

i am also mistefied why it randomly works, i know it's internally loadbalanced, but shutting down 1 of the 2013 servers did not get rid of this strange behavior.

is it possible that the exchange 2010 servers play a part in this issue?

Any ideas, any help is very much welcome!.

Regards,

Marco

Key4ce - IT professionals: www.key4ce.eu

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.

Hi,

Is that possible to get all the CMDLets result from Exchange 2010 that had been applied. Please assist.

Hi all,

we traid to install Exchange CU6 as a upgrade from Exchange 2013 SP1. The Setup Fails like this:

E:\Sources\Ex2013CU6>setup /m:upgrade /IAcceptExchangeServerLicenseTerms

Welcome to Microsoft Exchange Server 2013 Cumulative Update 6 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Languages
Mailbox role: Transport service
Client Access role: Front End Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Management tools
Client Access role: Client Access Front End service

Performing Microsoft Exchange Server Prerequisite Check

                                                              FAILED
 An unexpected error has occurred and a Watson dump is being generated: Object r
eference not set to an instance of an object.

     Object reference not set to an instance of an object.

The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

[09/15/2014 13:53:00.0941] [0] **********************************************
[09/15/2014 13:53:00.0956] [0] Starting Microsoft Exchange Server 2013 Cumulative Update 6 Setup
[09/15/2014 13:53:00.0956] [0] **********************************************
[09/15/2014 13:53:00.0956] [0] Local time zone: (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna.
[09/15/2014 13:53:00.0956] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[09/15/2014 13:53:00.0956] [0] Setup version: 15.0.995.29.
[09/15/2014 13:53:00.0972] [0] Logged on user: LOC\administrator.
[09/15/2014 13:53:01.0019] [0] Command Line Parameter Name='mode', Value='Upgrade'.
[09/15/2014 13:53:01.0019] [0] Command Line Parameter Name='iacceptexchangeserverlicenseterms', Value=''.
[09/15/2014 13:53:01.0019] [0] Command Line Parameter Name='sourcedir', Value='E:\Sources\Ex2013CU6'.
[09/15/2014 13:53:01.0285] [0] RuntimeAssembly was started with the following command: '/m:upgrade /IAcceptExchangeServerLicenseTerms /sourcedir:E:\Sources\Ex2013CU6'.
[09/15/2014 13:53:01.0300] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0, wasn't found.
[09/15/2014 13:53:01.0300] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14, wasn't found.
[09/15/2014 13:53:01.0300] [0] Copying Files...
[09/15/2014 13:53:01.0316] [0] Starting copy from E:\Sources\Ex2013CU6\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[09/15/2014 13:53:02.0816] [0] Finished copy from E:\Sources\Ex2013CU6\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[09/15/2014 13:53:02.0816] [0] File copy complete. Setup will now collect additional information needed for installation.
[09/15/2014 13:53:02.0831] [0] Assembly dll file location is C:\Windows\Temp\ExchangeSetup\Microsoft.Exchange.Setup.Console.dll
[09/15/2014 13:53:06.0613] [0] Setup is choosing the domain controller to use
[09/15/2014 13:53:07.0003] [0] The MSExchangeADTopology has a persisted domain controller: LOC-srv1201.LOC.local
[09/15/2014 13:53:11.0253] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use LOC-srv1201.LOC.local
[09/15/2014 13:53:11.0253] [0] Setup is choosing a global catalog...
[09/15/2014 13:53:11.0331] [0] Setup has chosen the global catalog server LOC-srv1201.LOC.local.
[09/15/2014 13:53:11.0347] [0] Setup will use the domain controller 'LOC-srv1201.LOC.local'.
[09/15/2014 13:53:11.0347] [0] Setup will use the global catalog 'LOC-srv1201.LOC.local'.
[09/15/2014 13:53:11.0347] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LOC,DC=local'.
[09/15/2014 13:53:11.0347] [0] Exchange organization container for the organization is 'CN=LOC,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LOC,DC=local'.
[09/15/2014 13:53:11.0394] [0] Setup will search for an Exchange Server object for the local machine with name 'LOC-SRV7210'.
[09/15/2014 13:53:11.0738] [0] Exchange Server object found : 'CN=LOC-SRV7210,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=LOC,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LOC,DC=local'.
[09/15/2014 13:53:12.0128] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
[09/15/2014 13:53:12.0128] [0] The following datacenter roles are unpacked:
[09/15/2014 13:53:12.0128] [0] The following roles are installed: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
[09/15/2014 13:53:12.0144] [0] The local server has some Exchange files installed.
[09/15/2014 13:53:12.0175] [0] Server Name=LOC-SRV7210
[09/15/2014 13:53:12.0238] [0] Setup will use the path 'E:\Sources\Ex2013CU6' for installing Exchange.
[09/15/2014 13:53:12.0238] [0] Setup will discover the installed roles from server object 'CN=LOC-SRV7210,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=LOC,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LOC,DC=local'.
[09/15/2014 13:53:12.0238] [0] 'BridgeheadRole' is installed on the server object.
[09/15/2014 13:53:12.0238] [0] 'ClientAccessRole' is installed on the server object.
[09/15/2014 13:53:12.0253] [0] 'MailboxRole' is installed on the server object.
[09/15/2014 13:53:12.0253] [0] 'UnifiedMessagingRole' is installed on the server object.
[09/15/2014 13:53:12.0253] [0] 'CafeRole' is installed on the server object.
[09/15/2014 13:53:12.0253] [0] 'FrontendTransportRole' is installed on the server object.
[09/15/2014 13:53:12.0253] [0] The installation mode is set to: 'BuildToBuildUpgrade'.
[09/15/2014 13:53:13.0425] [0] An Exchange organization with name 'LOC' was found in this forest.
[09/15/2014 13:53:13.0425] [0] Active Directory Initialization status : 'True'.
[09/15/2014 13:53:13.0425] [0] Schema Update Required Status : 'False'.
[09/15/2014 13:53:13.0425] [0] Organization Configuration Update Required Status : 'False'.
[09/15/2014 13:53:13.0425] [0] Domain Configuration Update Required Status : 'False'.
[09/15/2014 13:53:13.0441] [0] The locally installed version is 15.0.847.32.
[09/15/2014 13:53:13.0441] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V15'.
[09/15/2014 13:53:13.0535] [0] Setup is determining what organization-level operations to perform.
[09/15/2014 13:53:13.0535] [0] Because the value was specified, setup is setting the argument OrganizationName to the value LOC.
[09/15/2014 13:53:13.0581] [0] RootDataHandler has 1 DataHandlers
[09/15/2014 13:53:13.0581] [0]      Languages
[09/15/2014 13:53:13.0581] [0]      Mailbox role: Transport service
[09/15/2014 13:53:13.0581] [0]      Client Access role: Front End Transport service
[09/15/2014 13:53:13.0581] [0]      Mailbox role: Client Access service
[09/15/2014 13:53:13.0581] [0]      Mailbox role: Unified Messaging service
[09/15/2014 13:53:13.0581] [0]      Mailbox role: Mailbox service
[09/15/2014 13:53:13.0581] [0]      Management tools
[09/15/2014 13:53:13.0581] [0]      Client Access role: Client Access Front End service
[09/15/2014 13:53:13.0613] [0] Validating options for the 7 requested roles
[09/15/2014 13:53:13.0613] [0] UpgradeModeDataHandler has 17 handlers and 17 work units
[09/15/2014 13:53:13.0675] [0] Performing Microsoft Exchange Server Prerequisite Check
[09/15/2014 13:53:13.0925] [0] **************
[09/15/2014 13:53:13.0925] [0] Setup will run the task 'Start-PreConfiguration'
[09/15/2014 13:53:13.0941] [1] Setup launched task 'Start-PreConfiguration -Mode 'BuildToBuildUpgrade' -Roles 'LanguagePacks','BridgeheadRole','FrontendTransportRole','ClientAccessRole','UnifiedMessagingRole','MailboxRole','AdminToolsRole','CafeRole'' 
[09/15/2014 13:53:15.0472] [1] [ERROR] Object reference not set to an instance of an object.
[09/15/2014 13:53:15.0472] [1] [WARNING] An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an instance of an object.
[09/15/2014 13:53:16.0144] [1] [ERROR] Object reference not set to an instance of an object.
[09/15/2014 13:53:16.0144] [1] [ERROR] Object reference not set to an instance of an object.
[09/15/2014 13:53:16.0175] [0] [ERROR] Exception has been thrown by the target of an invocation.
[09/15/2014 13:53:16.0175] [0] [ERROR] Object reference not set to an instance of an object.
[09/15/2014 13:53:16.0175] [0] [ERROR] Object reference not set to an instance of an object.
[09/15/2014 13:53:16.0175] [0] CurrentResult SetupLauncherHelper.loadassembly:444: 1
[09/15/2014 13:53:16.0175] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[09/15/2014 13:53:16.0175] [0] CurrentResult main.run:235: 1
[09/15/2014 13:53:16.0175] [0] CurrentResult setupbase.maincore:396: 1
[09/15/2014 13:53:16.0175] [0] End of Setup
[09/15/2014 13:53:16.0175] [0] **********************************************

Hi,

I'm planning for a migration and was looking for any advice anyone may have based on their experiences. Here is our existing setup:

• One Exchange 2007 (all roles on one box, and its on a Windows 2003 DC; this is not SBS)
• Two  Windows 2003 DCs (as per above, as you can tell the need for this migration)

The goal is to:

• Introduce a new dedicated Exchange 2013 server (as a VM)
• Introduce 2 new Windows 2012R2 DCs (both physical)

I'm aware that the Exchange has to be at least SP3 for coexistance. From the compatibiltiy list it shows that Windows 2003 DCs are supported.

Should I make the 2012 R2 servers the DCs before installing Exchane 2013? The part I'm not quite sure about is how to go about this since Exchange is running on the 2003 DC and if it will break anything by trying to make another.

bl

Dears,

i am having exchange 2007 installed on 4 servers , 2 mailbox and 2 hubcas servers and will migrate 2 exchange 2013 with highly available solution with 2 mailbox DAG and 2 cas servers in a network load balance.

i want to know if i could begin the migration with only one mailbox server and one cas server and later on add the other mailbox and other cas server

Hello guys,
We have exchange 2007 SP3 servers, Exchange 2013 CU3 with all
rules (no DAG) server and Office 365 .
Exchange 2013 CU3 servers were
installed initially only for office 365 migration needs. They configured as
hybrid servers.
No, after the migration I would like to install Exchange 2013
servers with DAG.

I am going to install 2 new servers with only Mailbox
role on Windows 2008 R2 enterprise.
Also, I will upgrade current Exchange
2013 CU3 to CU7.
Later after making sure everything is ok, I am planning to
remove mailbox role from these hybrid servers. Unfortunately, in order to do it,
exchange should be removed and re-installed with only client rule.
Will it
remove or change significantly hybrid configuration? Is there any manual how to
remove\reinstall exchange without changing hybrid config?

Second question: Are any issues with CU7 and it's better to stay with CU3? I prefer to upgrade since all the users who still not migrated to Office 365, are located on Exchange 2007. So it will be easier to do it now than later after migration

Please assist

Hi Guys,

I got this error message keeps popping up in the event viewer like every minute.. i have no clue what is this error message is for. can anyone give me some idea or point me to the right direction

Exchange 2013 running 2 node DAG. the error message is found on the passive node.

"The Microsoft Exchange Migration Workflow service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service."

Thanks

We have an odd issue when trying to move mailboxes to Databases with Exchange 2013 Build 847.32 on all servers affected. 

We have 2013 successfully deployed within the UK (3 servers, with a DAG) we are looking to deploy an additional 2 servers in the US across an MPLS WAN. The US has it's own DAG in the US and its own MAPI network (this MAPI network is tested routable to the UK) DAG own replication network not routable, and simply a cross over...

The Migration Arbitration mailbox is located within the UK DAG, it exists as do the other Arbitration mailboxes and everything works fine moving mailboxes across DBs in the UK...

As soon as I try and move a mailbox in the US between the two server (or even on the same server within the US) it comes up with the following error after about 20mins: Worth stressing that all migration within the UK DAG work perfectly fine... 

Error:MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionMdbOffline: Unable to make connection to the server. ‎(hr=0x80004005, ec=1142)‎ Diagnostic context: Lid: 41192 dwParam: 0x1 Lid: 63464 Lid: 34792 StoreEc: 0x6AB Lid: 51176 StoreEc: 0x80040115 Lid: 48104 Lid: 39912 StoreEc: 0x80040115 Lid: 41192 dwParam: 0x2 Lid: 55272 Lid: 34792 StoreEc: 0x6BE Lid: 51176 StoreEc: 0x80040115 Lid: 48104 Lid: 39912 StoreEc: 0x80040115 Lid: 41192 dwParam: 0x0 Lid: 49064 dwParam: 0x1 Lid: 37288 StoreEc: 0x6AB Lid: 49064 dwParam: 0x2 Lid: 38439 EMSMDBPOOL.EcPoolConnect called [length=48] Lid: 54823 EMSMDBPOOL.EcPoolConnect returned [ec=0x476][length=20][latency=796] Lid: 53361 StoreEc: 0x476 Lid: 51859 Lid: 33649 StoreEc: 0x476 Lid: 43315 Lid: 58225 StoreEc: 0x476 Lid: 39912 StoreEc: 0x476 Lid: 54129 StoreEc: 0x476 Lid: 50519 Lid: 59735 StoreEc: 0x476 Lid: 59199 Lid: 27356 StoreEc: 0x476 Lid: 65279 Lid: 52465 StoreEc: 0x476 Lid: 60065 Lid: 33777 StoreEc: 0x476 Lid: 59805 Lid: 52487 StoreEc: 0x476 Lid: 19778 Lid: 27970 StoreEc: 0x476 Lid: 17730 Lid: 25922 StoreEc: 0x476

I assume this is looking for the Migration Arbitration mailbox in the UK, across the WAN and is failing but all other features seem to work fine... In fact if I try to migrate using the Shell on a US server, it works fine so this seems to be limited to the Console...

WAN connectivity is fine, I have done a TCP any any on the ASAs to make sure there is full communication and everything else works fine... 

Any ideas as to why it seems to be failing to see the Arbitration mailbox? I t is also worth mentioning I have re-run the ADPREP /Alldomains to ensure there is no corruption within the Arbitration mailboxes...

I have probably missed something very simple somewhere but for the life of me can't think where... 

Any help gratefully received... 

As an Exchange administrator, I am sure you are familiar with the kinds of the 9646 event error report in the application log. They can appear many times per day or only happen once a week. Although, it seems there is no user impact about this error, but the Boss may have concerns about the potential issues about this error.


[Symptoms]
============



 

[Cause]
=========
Connection and usage limits have been placed on the Exchange store to prevent a single application or a single user from using all the available connections to the Exchange store.

[Solution]
===========
Firstly, you need to check the application log and see if the user do have the requirements to raise the store limitation for them.

For Example, some VIPs may need to keep the mailbox open on multiple clients like Outlook, OWA, Mobilities, or they have requirements to share their mailboxes to secretaries. Then you may need to raise the MaxObjsPerMapiSession value for them in order to avoid this event error report.

1.Start Registry Editor (regedit).
2.Navigate to the following registry subkey:

\\HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem

3.Right-click ParametersSystem, point to New, and then click Key. A new key is created in the console tree.
4.Rename the key MaxObjsPerMapiSession, and then press Enter.
5.Right-click MaxObjsPerMapiSession, point to New, and then click DWORD (32-bit) Value. The new value is created in the result pane.
6.Rename the key to <Object_type>, where <Object_type> is the name of the registry object type that you're modifying. For example, to modify the number of messages that can be opened, use objtMessage. Press Enter.
7.Right-click the newly created key, and then click Modify.
8.In the Value data box, type the number of objects that you want to limit this entry to, and then click OK. For example, type 350 to increase the value for the object.
9.Restart the Microsoft Exchange Information Store service.

However, for some instances, the in question user may tell you that only Outlook is in use and there is no other live MAPI sessions he know. Based on my experience, this issue can occur due to third-party add-ins on Outlook or some third-party search indexing software on the Outlook client. To verify this issue, you can run Windows in Clean Boot mode (better to temporarily remove the searching software) and run Outlook without add-ins by “Outlook /safe”.

In summary, the 9646 Event reports are just the notification about the status of each Exchange Client that connect to the mailbox store. The user impacts may not be huge and you can choose different countermeasures according to the conditions.

More details:

http://support.microsoft.com/kb/842022
https://technet.microsoft.com/en-us/library/ff477612(v=exchg.141).aspx

Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hi,

we have two separate forests (and two separate MSX orgs). We want to migrate to Exchange Online. The information I find states that we need to establish a trust-relationship between the ADs of both forests. Also it states that we run AAD Sync only in one forest and connect it to the other. I also read that Hybrid Configuration Wizard might fail, if we do not do what was written above.

So, I am wondering why would I need a AD trust? I would also want to know if you can't do the following in our case:

• Leave both environments as is  
• run aad sync in both environments (there are only unique objects in the Ads)
• run HCW against one Org and do all the steps manually on the other Org (Org relationship)
• (if we decide to use ADFS, we could install it also in each forest separately)

Would this work also (X500 addresses would be written and updated, move requests would work, F/B, etc)?

Is there more detailed information available? Technet isn't really precise here (https://technet.microsoft.com/en-us/library/jj873754%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396)

Thanks for all input!

Emil

Hi,

I plan to disable ECP from Internet access. I try to use Set-ECPVirtualDirectory -Identity "CAS01\ecp (default web site)" -AdminEnabled $false it give error

The version of Internet Information Services (IIS) that is running on server 'CAS01.masb.com' can't be determined.
This error can occur due to network connectivity issues. Check the availability of your network and try again.
Parameter name: Server
    + CategoryInfo          : InvalidArgument: (CAS01\ecp (Default Web Site):ADObjectId) [Set-EcpVirtualDirectory], Ar
   gumentException
    + FullyQualifiedErrorId : [Server=MAILBOX02,RequestId=42d5f0b8-9e83-49d7-a308-68f87ac7e643,TimeStamp=12/3/2015 10:
   42:53 PM] [FailureCategory=Cmdlet-ArgumentException] 5636C4E3,Microsoft.Exchange.Management.SystemConfigurationTas
  ks.SetEcpVirtualDirectory
    + PSComputerName        : cas01.masb.com

We mange to set it on CAS02.

May I know how to solve this issue on CAS01. We already set CAS03 for internal use only

Thank you

Best regards,

See Keong

Hi Everyone,

I'm trying to migrate a few mailboxes from a database called "primary" to "archive". I can migrate a single user through powershell, however I cannot migrate users through the GUI. When the "syncing" starts, it reverts the total from "2" to "0" and makes it appear as though I never added any users to the batch job. The job then completes "successfully"

I can see the users in the job before I hit start. Any idea why my job goes blank?

I'm running exchange 2013 CU6

Hi All ,

How  generates a report with mailboxes that has exceeded the mailbox database quota limit in Exchange 2013 ?

Thank you 

Our current Active Directory domain consists of 3 Windows 2003 domain controllers.  The FFL and DFL are Windows 2003. In the domain, we have a member server running Exchange 2003 Server for messaging and another Windows 2008 member server running MOSS 2007.

We have been given a budget for an IT refresh and would like to upgrade to the latest versions of these products where possible.  I have read various blogs that advise that an Exchange 2003 messaging environment is not supported in a Windows 2012 domain.  My dilema is where to start  I want to upgrade Active Directory to 2012 and also Exchange to Exchange Server 2013.  Is there a recommended approach to this without breaking the system?

Thanks