Time is up for Exchange Server 2013, and you should be finalizing your migrations. If your migration is still ahead of you or nearing completion, then this post is for you.
We wanted to provide Mic...
Updated Mar 20, 2023
Version 2.0
Blog Post
16 MIN READ
Best Practices for Migrating from Exchange Server 2013 to Exchange Server 2019
Have installed 2019 in our 2013 environment.
(edited with updated info)
Have a major issue.
Outlook 365 is randomly saying it is connected but won't update folders, then will randomly disconnect, then randomly connects and updates folders. When not working clicking Update Folder gives error:
0x8004011d the server is not available.
Mail on my mobile is still working ok and OWA is working fine, just Outlook 365 client is having issues. Mail flow is still occurring, it is just Outlook clients experiencing intermittent issues.
The scp for the new server has been set to webmail.ourdomain.com which in dns points to our 2013 environment. All the virtual directories have been changed to webmail.ourdomain.com where appropriate.
Also running RollAlternateServiceAccountPassword.ps1 -ToSpecificServer exchange2019 -CopyFrom exchange2013 from the exchange2013 server gives this error:
RecordErrors : Cannot convert value "exchange2019" to type"Microsoft.Exchange.Data.Directory.Management.ClientAccessServer"
Running it from the new server gives this error
RecordErrors : The term 'Get-ClientAccessService' is not recognized as the name of a cmdlet, function, script file...
Any ideas anyone?
thanks