Perform Outlook tests on the network including creating a new Outlook profile, scheduling a meeting and viewing free/busy information for attendees, accessing public folders, and sending/receiving internal and external email.Review your server event logs for any unusual errors.Verify that backups for the existing and new Exchange servers are running successfully.Use the Remote Connectivity Analyzer to test external access such as Outlook Anywhere and ActiveSync.Run the Test-ExchangeServerHealth.ps1 script.If you start a migration, then notice the problems, troubleshooting is more complicated because you will be unsure whether the problem has been caused by the migration or not. The reason for performing a health check now is to determine if there are any existing problems that you might not already be aware of. Health Checkįirst, it’s advisable to perform a general health check of the existing production environment. Before any services are cut over, there’s some preparation tasks to perform. ![]() ![]() This stage is referred to as coexistence. The Exchange 2016 migration for Not Real University is getting to the stage where they can start cutting over client access and transport services to the Exchange 2016 Mailbox server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |