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

Hello,

i get this error when i  Prepare Active Directory for Exchange:

[01/12/2013 10:11:27.0640] [1] [ERROR] The following error was generated when "$error.Clear();
          #
          # O15# 2844081 - Create PartnerApplication "Exchange Online" in DC and On-Premise
          #
          $exch = [Microsoft.Exchange.Data.Directory.SystemConfiguration.WellknownPartnerApplicationIdentifiers]::Exchange;
          $exchApp = Get-PartnerApplication $exch -ErrorAction SilentlyContinue -DomainController $RoleDomainController | Where { $_.UseAuthServer };
          if ($exchApp -eq $null)
          {
              $exchAppName = "Exchange Online";
              $exchApp = New-PartnerApplication -Name $exchAppName -ApplicationIdentifier $exch -Enabled $RoleIsDatacenter -AcceptSecurityIdentifierInformation $false -DomainController $RoleDomainController;
          }

          # Create application account for Exchange
          $appAccountName = $exchApp.Name + "-ApplicationAccount";
          $appAccount = Get-LinkedUser -Identity $appAccountName -ErrorAction SilentlyContinue -DomainController $RoleDomainController;
          if ($appAccount -eq $null)
          {
            $appAccountUpn = $appAccountName.Replace(" ", "_") + "@" + $RoleFullyQualifiedDomainName;
            $appAccount = New-LinkedUser -Name $appAccountName -UserPrincipalName $appAccountUpn -DomainController $RoleDomainController;

            New-ManagementRoleAssignment -Role "UserApplication" -User $appAccount.Identity -DomainController $RoleDomainController;
            New-ManagementRoleAssignment -Role "ArchiveApplication" -User $appAccount.Identity -DomainController $RoleDomainController;
            New-ManagementRoleAssignment -Role "LegalHoldApplication" -User $appAccount.Identity -DomainController $RoleDomainController;
            New-ManagementRoleAssignment -Role "Mailbox Search" -User $appAccount.Identity -DomainController $RoleDomainController;
            New-ManagementRoleAssignment -Role "TeamMailboxLifecycleApplication" -User $appAccount.Identity -DomainController $RoleDomainController;
            New-ManagementRoleAssignment -Role "MailboxSearchApplication" -User $appAccount.Identity -DomainController $RoleDomainController;

            Set-PartnerApplication -Identity $exchApp.Identity -LinkedAccount $appAccount.Identity -DomainController $RoleDomainController;;
          }
        " was run: "Couldn't find object "mydomain.local/Users/Exchange Online-ApplicationAccount". Please make sure that it was spelled correctly or specify a different object.".
[01/12/2013 10:11:27.0640] [1] [ERROR] Couldn't find object "mydomain.local/Users/Exchange Online-ApplicationAccount". Please make sure that it was spelled correctly or specify a different object.
[01/12/2013 10:11:27.0640] [1] [ERROR-REFERENCE] Id=CommonGlobalConfig___907E0EE000AB4117A05F237A81E53AA2 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[01/12/2013 10:11:27.0640] [1] Setup is stopping now because of one or more critical errors.
[01/12/2013 10:11:27.0640] [1] Finished executing component tasks.
[01/12/2013 10:11:27.0671] [1] Ending processing Install-ExchangeOrganization
[01/12/2013 10:34:25.0119] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[01/12/2013 10:34:25.0119] [0] End of Setup

I remember back in the CU15 to CU21 times M$ caught a lot of slack for their unpreparedness with older .NET versions and Exchange 2013.

I've currently got an Exchange 2013 CU19 with .NET 4.8. Are there any known issues with going directly from CU19 to CU23? Do I need to do anything special or performed a half-step upgrade first (to something in between)?

TIA!

Hi

One phishing email received in our domail .

How to check and block phishing email in exchange server 2013 step by step

Regards,

Satish Chaturvedi

Satish Chaturvedi Mob-9990806001

These events keep showing up constantly in all exchange 2016 DAG servers:

Source:ESE

Event 2001, 2005,2006

Task Category: ShadowCopy

Message: Information Store - exchange DB : Shadow copy instance 74 freeze started

I don't have Windows Server Backup installed. I didn't run exchange backup. I don't have shadow copy enabled.

These events happen day and night and create a nighmare for end users and causing outlook freeze constantly. I don't know where it comes from. Does anyone have an idea where to check?

Alan

Hi,

I have two self-signed certificates, both were created during Exchange installation.

- Microsoft Exchange Server Auth Certificate (assigned to services SMTP)

- Microsoft Exchange (assigned to services IMAP, POP, IIS, SMTP)

In Exchange Admin Center - Servers - Certificates,

after click Renew for Microsoft Exchange Server Auth Certificate, Expires On was changed to 2025 and everything looked good,

after click Renew for Microsoft Exchange certificate, Expires On was changed to 2025,

but after signing in to Exchange Admin Center again, only empty white screen is displayed.

And also I not able to open Administrator profile or others profile in Outlook.

Guys in Microsoft, it looked like a simple thing - just click Renew.

But now, honestly, I'm going crazy.

I can't find a working solution to this problem.

I beg you, help me.

Please, write me the steps to fix it.

Thank you in advance.

Exchange server 2013 CU23, Outlook 2013, Windows Server 2012 R2

Hi experts

When trying to install another Exchange 2013 server in my test environment I got the following 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 settingshared config DC. Exception: " + $_.Exception.Message);
            }

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

          if( -not $successfullySetConfigDC)
          {
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
          }
        " was run: "System.Exception: Unable to set shared config DC.
   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.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

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

Did I miss anything? Any solution to this ?

Hi all,

Currently running Exchange 2013 - 3 node DAG (2 on site - 1 dr site). 

Since updating to applying the following update we have seen a marked drop in performance from the servers and users are reporting that their overall experience has dropped considerably. 

Security Update For Exchange Server 2013 Cumulative Update 23 (KB4536988)

Servers were originally on CU15 upgraded to CU21 pre December, no issues. Completed the step upgrade between CU21 and .net to get to the correct levels - .net is currently 4.7.2

Once the update was completed we did have the ECP / OWA issues listed in the below article, applied the fixes and no problems there, just the bad performance

https://borncity.com/win/2020/02/15/exchange-server-2013-mail-issues-after-update/

Examples include Outlook dropping connecting, taking increasing time to access folders and mailboxes 

Two servers @ primary site with DAG, majority of users are connecting in through Citrix with mailboxes in online mode. 

Checking the CAS load its appears to only be reporting that a since server has any connections. 

Any advise would be appreciated.

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

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

I have done lots of mess with certs on my exchange environment, as i prepared to migrate 365..

basically, i request help because my outlook is not working (keeps poping for passwords) - pointing to my autodiscoverinternally just not working well.

i have one cas and MB and one MB alone - 2013 exchange (please don't ask why) - had nasty issues due to storage..etc..

when i ran: Get-ExchangeCertificate -DomainName mail.domain.com 

i get two certificates - one purchased online (i want this to be default of all services), and one self-signed one - i would want to remove from reference of -domain (mail.domain.com & autodiscovery.domain.com)

i request for command to force my online cert to over-write the selfsigned one in this case (of owa & autodiscovery).

*** is there a command Enable-ExchangeCertificate -Thumbprint - domain -mail.domain.com, autodiscover.com**

FYI: when i open owa -- i get notified that cert (selfsigned one) is INVALID (by right-clicking on cert info)

thanks

I am trying to install the exchange server 2010 sp3 update and need to find the UCMA Core Runtime. All links to microsoft download are no longer working.

Any help would be great.

Hello All....I need few pointers with respect to Hosted Exchange Environment.

1.  Is Hosted Exchange Supported in Exchange Server 2016?

2.  Any recommendations for Control Panel for both Administrators as well as Customers?

3.  Any link to official/unofficial documentation that I can utilize?

4.  Any blog/article/link to help with the designing aspect?

5.   Any blog/article/link to help with the capacity planning?

6.  Any blog/article/link to help with the hardware sizing?

thanks in advance

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 - I'm at CU9 in a DAG environment at the moment and need to upgrade to the latest. Can I go directly to CU23?

Also I read that any custom xml's would need to be backed up. How would I know which xml's were changed?

Anything else I would have to watch out for?

Thank you for your help!!!

Joe

I'm in the process of migrating from E2013 to E2016. I've tried to start my mailbox moves, but any user I migrate just stays in a "syncing" state. I've left batches running for days and it never changes. The users are only test accounts, so there really is almost no data. I am also only doing 1 user at a time until it is successful.

On the E2016 event log, it shows the migration cmdlet was started successfully. No other events after that. On the E2013, no messages there either.

Running the Get-MoveRequest -BatchName "Pilot" | Get-MoveRequestStatistics cmdlet yields nothing. It just returns to a prompt with no output.

I've had to kill the batches forcefully as deleting them also just hangs in a state of deleting.

I've tried restarting a Mailbox Replication as others have suggested and that doesn't do anything either.

Any ideas?