Hi everyone,

I have an Exchange 2010 CAS and another Exchange 2010 Database that I want to migrate to a new Exchange server 2016 running Windows Server R2.

Can I use the Windows server 2012 R2 for both CAS and Database?

Please help

Thank you

Hello;

I recently reboot my Exchange server but the Microsoft Exchange Frontend Transport was not able to start until I access to Exchange Admin Center | Mail Flow | Receive Connector and find one of my connector "XXX connector", I did disable it and enable it.  The Microsoft Exchange Frontend Transport is able to start.

I have two Receive Connectors, one is the Default connector - "Default servername" - Hub Transport Role,  the scope of this Hub Transport role is 0.0.0.0255.255.255.0 (this is the default setup), network binding to port 2525.

the second connector is my custom connector - "Company Authorized Server" - Frontend Transport Role.

Currently, I need make sure to Disable / Enable manually the "Company Authorized Server" connector in order to ensure that the  Microsoft Exchange Frontend Transport service can be started.

Is there something I can do to make sure the  Microsoft Exchange Frontend Transport service started properly.

KW - CNE,MCSE,VCP5

Hi,

The cert has expired. I looked into it on the web to find out what this cert  is really for and I found, that these functions can only work between the organizations if the cert is valid:

Free / Busy queries
MailTips
Out of office status
Profile pictures

The environment is an Exchange 2013 - O365 hybrid configuration and we  generally don't use these features, but we still need to migrate some of the local mailboxes to O365. 

Do I need to hassle with this cert to migrate mailboxes or I can leave it as it is? Our fnal goal is to shut down exchange 2013 anyway.

Thanks,

Currently running Exchange Server 2013 RTM Build:  15.0.516.32.  I want to upgrade to Exchange Server 2013 CU23 Build: 15.0.1497.2.  Is there any issue with this upgrade path?  Any gotchas?

I wasnt sure if I should install SP1 first if I could just go from RTM to CU23.

Thanks

Hello

        Could you please Recommend help me about Exchange Database Size ?

        I see in database file edb it about 1 TB , I worry it very large

Thanks

hi 

i have 2 exchange server work at dag configuration.

we are planning  magretion to office365 so i start with the CU

on ex02 (second server) the installion work perfect 

on ex01 i got the next error

i run all the prerequisite before, run preparAD and all.

Error:
The following error was generated when "$error.Clear();
          Install-ExchangeCertificate -services "IIS, POP, IMAP" -DomainController $RoleDomainController
          if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
          {
          Install-AuthCertificate -DomainController $RoleDomainController
          }
        " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.AddAccessRuleCryptographicException: Could not grant Network Service access to the certificate with thumbprint 31596249314B0A6DC7E13E00FAB6765DADA18639 because a cryptographic exception was thrown. ---> System.Security.Cryptography.CryptographicException: Access is denied.

   at Microsoft.Exchange.Security.Cryptography.X509Certificates.TlsCertificateInfo.CAPIAddAccessRule(X509Certificate2 certificate, AccessRule rule)
   at Microsoft.Exchange.Security.Cryptography.X509Certificates.TlsCertificateInfo.AddAccessRule(X509Certificate2 certificate, AccessRule rule)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.ManageExchangeCertificate.EnableForServices(X509Certificate2 cert, AllowedServices services, String websiteName, Boolean requireSsl, ITopologyConfigurationSession dataSession, Server server, List`1 warningList, Boolean allowConfirmation, Boolean forceNetworkService)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.EnableForServices(X509Certificate2 cert, AllowedServices services)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

I have a client that still has on-premise Exchange 2010 servers and wants to finally get rid of them as all of their infrastructure is being moved to Azure. They do not want to migrate those legacy servers to Azure, so what is the best course for finally getting rid of them. I understand that this may not be fully "supported" from Microsoft, but I don't care. I am interested in what will work. 

1) Copy out all email addresses to a file

2) Remove the Hybrid configuration (Note: they put in place a Hybrid config, but never used it. Migration was done using BitTitan. Exchange Hybrid feature was never selected in Azure AD Connect)

3) Delete Exchange databases in ADSIEdit manually. Mailboxes still exist.

4) Remove the DAG and get rid of the cluster

5) attempt uninstall of Exchange servers one-by-one

Will this work? By uninstalling, does it remove any email attributes from AD that we need to be aware of? Stop AD Connect during this?

Thanks,

Good afternoon, all!

I'm setting up a new Exchange infrastructure in our company.  The setup I have is very similar to this posting, except that I have double-checked the IPv6 on both domain controllers and the new 2012 R2 server that Exchange will run on. This server is the first in a planned four-server design: two CAS/Mailbox and two Edge Transport servers. We don't use IPv6 internally yet, so all the IPv6 configs point to link local.  The error after Transport service timed out was:

Error:
The following error was generated when "$error.Clear(); 
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;

          while($currTime -le $timeout)
          {
            $setSharedCDCErrors = @();
            try
            {
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);

              if($successfullySetConfigDC)
              {
                break;
              }
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            }
            catch
            {
              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
            }

            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          }

          if( -not $successfullySetConfigDC)
          {
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
          }" was run: "Unable to set shared config DC.".

I've checked the ping and DNS resolves, the new server is a domain member.  Here's a section toward the end of the Exchange Installation log:

[09/03/2015 18:21:51.0473] [2] Ending processing Write-ExchangeSetupLog
[09/03/2015 18:21:51.0473] [2] Beginning processing Write-ExchangeSetupLog
[09/03/2015 18:21:51.0473] [2] Waiting 30 seconds before attempting again.
[09/03/2015 18:21:51.0473] [2] Ending processing Write-ExchangeSetupLog
[09/03/2015 18:22:21.0462] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller: 'isc1.iscinternational.net', Preferred Global Catalog: 'isc1.iscinternational.net', Preferred Domain Controllers: '{ isc1.iscinternational.net }'
[09/03/2015 18:22:21.0462] [2] User specified parameters:  -DomainController:'isc1.iscinternational.net' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
[09/03/2015 18:22:21.0462] [2] Beginning processing Set-SharedConfigDC
[09/03/2015 18:22:21.0680] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Suitable Directory Servers Found in Forest iscinternational.net Site Default-First-Site-Name..
[09/03/2015 18:22:21.0680] [2] No Suitable Directory Servers Found in Forest iscinternational.net Site Default-First-Site-Name.
[09/03/2015 18:22:21.0680] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Suitable Directory Servers Found in Forest iscinternational.net Site Default-First-Site-Name..
[09/03/2015 18:22:21.0680] [2] No Suitable Directory Servers Found in Forest iscinternational.net Site Default-First-Site-Name.
[09/03/2015 18:22:21.0680] [2] Ending processing Set-SharedConfigDC
[09/03/2015 18:22:21.0680] [2] Beginning processing Write-ExchangeSetupLog
[09/03/2015 18:22:21.0696] [2] 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 No Suitable Directory Servers Found in Forest iscinternational.net Site Default-First-Site-Name..
[09/03/2015 18:22:21.0696] [2] Ending processing Write-ExchangeSetupLog
[09/03/2015 18:22:21.0696] [2] Beginning processing Write-ExchangeSetupLog
[09/03/2015 18:22:21.0696] [2] Waiting 30 seconds before attempting again.
[09/03/2015 18:22:21.0696] [2] Ending processing Write-ExchangeSetupLog
[09/03/2015 18:22:51.0690] [2] Beginning processing Write-ExchangeSetupLog
[09/03/2015 18:22:51.0690] [2] [ERROR] Unable to set shared config DC.
[09/03/2015 18:22:51.0690] [2] [ERROR] Unable to set shared config DC.
[09/03/2015 18:22:51.0690] [2] Ending processing Write-ExchangeSetupLog
[09/03/2015 18:22:51.0706] [1] The following 1 error(s) occurred during task execution:
[09/03/2015 18:22:51.0721] [1] 0.  ErrorRecord: Unable to set shared config DC.
[09/03/2015 18:22:51.0721] [1] 0.  ErrorRecord: System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[09/03/2015 18:22:51.0753] [1] [ERROR] The following error was generated when "$error.Clear(); 
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;

          while($currTime -le $timeout)
          {
            $setSharedCDCErrors = @();
            try
            {
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);

              if($successfullySetConfigDC)
              {
                break;
              }
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            }
            catch
            {
              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
            }

            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          }

          if( -not $successfullySetConfigDC)
          {
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
          }" was run: "Unable to set shared config DC.".
[09/03/2015 18:22:51.0753] [1] [ERROR] Unable to set shared config DC.
[09/03/2015 18:22:51.0753] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[09/03/2015 18:22:51.0768] [1] Setup is stopping now because of one or more critical errors.
[09/03/2015 18:22:51.0768] [1] Finished executing component tasks.
[09/03/2015 18:22:51.0862] [1] Ending processing Install-BridgeheadRole

I suspect there's a problem with the Site Default-First-Site-Name part - I did specify a new Exchange Organization name during the first part of setup.

One other detail - this is a 2008 R2 domain, and the nearest DC had a problem with the Network Location - it thought the adapter was in the Public zone. I thought this might be the problem and fixed that by disabling/re-enabling the adapter, but that didn't help the Exchange install.  The second DC was probably registering the Exchange information.

Two questions, then: first, can I rescue this installation, or would I be faster or better off killing this server and spinning up a new one (this is on VMware 5.5)?  I would much rather fix this one than start again.  And second, what issues might I encounter as a result of this failed installation?  Will the install wizard pick up the changes to the AD schema?  I'm pretty sure that won't be a problem, but I don't know for certain.

Thanks to all for looking!

Gregg

Hi,

running thr HCW I get this error: "Could not convert string to DateTimeOffset: 0001-01-01T00:00:00. Path '[0].LastDirSyncTime' line 1, position 104"

the log reports

2019.09.06 08:30:56.214 *ERROR* 10430 [Client=UX, ExecuteHighlandsServiceRequest=DirSync, Thread=17]
                                      Newtonsoft.Json.JsonReaderException: Could not convert string to DateTimeOffset: 0001-01-01T00:00:00. Path '[0].LastDirSyncTime', line 1, position 104.
                                         at Newtonsoft.Json.JsonReader.ReadDateTimeOffsetString(String s)

Any idea? :(

thanks

Hello,

Wanted some assistance in figuring our an error I keep getting when trying to migrate our Public Folders from Exchange 2007 to Exchange 2013.

Currently I am running the step: Start-MigrationBatch PFMigration

The Job fails with error:

I have to say our 2007 PF are in the child domain, and exchange 2013 is in our root domain. Both are hitting same GC server. Not sure why the error occurs as the GC server is running normal .

I am trying to understand the ecp virtual directory external URL. If I don't set it and leave it empty, does it mean outside my network (from internet) that it can't be accessed? Currently i have both internal and external set up as 'mail.mycompany.com'. From both Internet and intranet, it can be accessed using https://mail.mycompany.com. If I remove external url from Exch Admin Center, does it mean it can't be accessed from Internet? How does it know the connection is from Internet or from intranet?

THanks.

Alan

I've been trying to uninstall a corrupted version of Exchange 2013 so I can start over from scratch. The errors from the automated uninstallation process indicated I needed to disable the arbritration mailbox. When I attempt to do so, I get the following error message:

C:\Windows\system32>Get-Mailbox -Arbitration -Database "Mailbox Database 0124449876" | Disable-Mailbox -Arbitration
 -DisableLastArbitrationMailboxAllowed
Couldn't disable the arbitration mailbox "ARKINCPAS.COM/Users/SystemMailbox{1f05a927-6399-4267-b6cd-a201193a0ffb}"
because it is associated with existing recipients for which membership restriction of approval is required or the
moderation feature is enabled. Please disable the approval feature on those recipients before performing this
operation.
    + CategoryInfo          : NotSpecified: (ARKINCPAS.COM/U...d-a201193a0ffb}:ADObjectId) [Disable-Mailbox], Recipien
   tTaskException
    + FullyQualifiedErrorId : E2BF0ACA,Microsoft.Exchange.Management.RecipientTasks.DisableMailbox
    + PSComputerName        : arkinserver01.arkincpas.com

I did not install Exchange 2013 on the C drive. Could that be the source of my problems?

Zachary Arkin

After a recent reboot of an Exchange 2013 server, I can no longer get into OWA or ECP. 

When rebooting, the server gave me the option to 'Update and Reboot' which I did.  It appears that CU9 was installed according to recent updates however I did not manually apply the update.

After reboot, all Exchange services and a few other services were set to Disabled.  Using another Exchange server I was able to determine what the startup type should be, set it accordingly and was able to get mail working however I still have some problems.

OWA will display logon screen but says 'bad request' after entering credentials.  ECP gives the following

=============================================================
Could not load file or assembly 'Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Stack Trace:

[FileNotFoundException: Could not load file or assembly 'Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.]
   System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName, ObjectHandleOnStack type) +0
   System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName) +153
   System.Type.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) +63
   System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) +124
   System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase) +76

[ConfigurationErrorsException: Could not load file or assembly 'Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.]
   System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase) +12425356
   System.Web.Configuration.Common.ModulesEntry.SecureGetType(String typeName, String propertyName, ConfigurationElement configElement) +69
   System.Web.Configuration.Common.ModulesEntry..ctor(String name, String typeName, String propertyName, ConfigurationElement configElement) +62
   System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList) +299
   System.Web.HttpApplication.GetModuleCollection(IntPtr appContext) +1262
   System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +133
   System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +304
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +404
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +475

[HttpException (0x80004005): Could not load file or assembly 'Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12618692
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12458309
=====================================================================

I tried to uninstall CU9 but after reboot all services were disabled again.  Now that mail flow is working, I wanted to get some other ideas before experimenting and making things worse.  This appears to be an IIS issue but I welcome ideas, or better yet, solution, on how to get things working again.

Thank you.

Hi All,

We have on on-prem. Exchange server 2013 server, with DAG configured on the same. when we assigning POP and IMAP services on wildcard certificate it showing below error.

"This certificate with thumbprint ********* and subject '*.yourdomain.com' cannot used for POP SSL/TLS connections because the subject is not a Fully Qualified Domain Name (FQDN). Use command Set-POPSettings to set X509CertificateName to the FQDN of the service."

due to this we are facing certificate error popups at client end where we have configured POP and Imap a/c.

Please help us to resolve this issue.

Regards, Prashant

Exchange Server 2013 CU update error.

Error code 0XC0070424 (1060): The specified service does not exist as an installed service.

Error code 0X8000500D (20493): This property can't be found in the cache.

Please  provide the solution

Satish Chaturvedi Mob-9990806001

How to upgrade Cumulative Updates 22 for Exchange Server 2013 step by step

Regards,

Satish

Satish Chaturvedi Mob-9990806001