Server Migration (On-premise Exchange Server to O365) and Server Maintenance

Server:

Servers are more or less like a computer, the only difference being no one works on a server sitting behind a monitor. While servers don’t necessarily need lots of processing power or RAM, having it can help deal with heavy traffic and signals coming in and out of the server.

Servers run on a 24x7 basis and because of that uptime is of high importance. Servers shouldn’t shut down as it’s on which most functions depend. If a Server goes down, it could either be because of an attack that compromised it or for scheduled maintenance (which happens during after-hours). You might have received emails or notifications of certain firms (especially banks) when their servers are scheduled to undergo maintenance.

We have talked about the benefits of moving to the cloud earlier, and this will talk about Server Migration from on-prem to cloud in brief.

Server Migration to the cloud:

Migration means transfer of data from one place to the other. Migration can be of data, emails, servers and more. It can usually happen from on-prem to on-prem servers, cloud to cloud servers or on-prem to cloud servers (the most prevalent these days).

Migration includes transfer of roles and responsibilities from one server to the other. Transfer of FSMO (Flexible Single Master Operation) roles present in the Domain Controllers being one of the major parts of this.

In a Managed Server, the cloud service provider will not only give a platform to host your servers and data but also handle all the nitty-gritties for you.

When it comes to a Private Server, the cloud service provider will give a platform to host your servers and data but rest of the functionalities will be managed by you.

Public Server- It gives internal as well as external users to view each other’s IP and gives them access to various application servers.

Why perform Server Migration?

Reasons could be many, one of them being:

• Increased cyberattacks on the on-prem servers

• Better performance and increased efficiency

• Enhanced security and flexibility on cloud

• To replace the servers that have reached end of life

• Slower access to mailboxes and many more

On-prem Exchange Server Migration to O365: Hybrid Migration

If you’re thinking of migrating your on-premise Exchange Servers to Microsoft’s O365, then there are 3 ways to perform it- Hybrid Migration, Staged Migration or Cutover Migration. If you have an Exchange server by Microsoft and if it’s a part of your Active Directory, then your default option to migrate to the cloud coould be a Hybrid Migration. It is anmed Hybrid- because you move some of the Microsoft apps, files or mailboxes to the cloud whereas the rest of the data remains on-premises. This is what is going to be covered in this blog.

Hybrid Migration can either be a minimal or a complete one which leads to creating a relationship between on-prem Exchange servers and Exchange online.

Mainly there are two different approaches for migration of current on-premises exchange environment to Exchange Online (Office 365):

1. Use some 3rd Party paid migration tools: Bit Titan, SkyKick, AvePoint etc. which requires an additional software deployment either on server or users’ workstations for email data migration & reconfiguring their Outlook Profiles.

2. Microsoft Native Hybrid Exchange Migration: Leverage Microsoft native methods for migrating all users’ mailboxes along with exchange configuration to Office 365, without the need for any extra application deployment under users’ devices for reconfiguring their outlook profiles.

Procedure of a Hybrid Server Migration

After having ensured that you have a healthy environment to migrate, then you can proceed with the hybrid migration:

• Firstly, Setup a Directory Synchronization between on-premises Aactive Directory & Azure AD using the Azure AD Connect Tool.

• Secondly, configure a Hybrid Exchange relationship between On-Premises Exchange & Exchange Online. Do this to ensure a seamless migration of users’ mailboxes & reconfiguration of their outlook profiles.

• Provision of migration endpoint & batches for users’ & shared mailboxes, public folders migration in a staged manner.

• Analyze results of configured migration batches, identify any errors/warnings along with their remediation.

• Schedule & Perform DNS Switchover for routing mail flow to Exchange Online

Once all the files are migrated to the cloud, you can gracefully decommission the exisitng on-premise exchange server.

Azure AD Connect

The best part about using the Azure AD Connect tool is that it automatically synchronizes the local on-premise active directory domain with O365. A local copy gets created on Azure Active Directory which will link back to the original copies. The Azure AD Connect Tool is meant to synchronize between the 2 and it plays the prime role in maintaining a Global address list between the on-prem exchange server and the cloud.

It complements Exchange Hybrid and you should expect to use Hybrid if you plan to synchronize your identity to the cloud.

Cut-over and Staged Migration

Cut-over: The simplest form of Migration. The entire content is transferred from one to the other at once. This generally involves using IMAP or RCP.

Staged Migration: Similar to a cutover migration but the migration takes place in stages or phases.

What’s right for you?

It depends on various factors like the version of the exchange server, the amount of data (it’s volume), the number of users, budget, your future approach and strategies, etc.

Server Maintenance

Monitoring and Maintenance includes- Health Monitoring, Backup Management, Timely Patch Management, identifying issues and alerts and remediating them.

Maintenance should be carried out during after-office hours as performing maintenance functions when the work force is functioning can hamper their workflow.

Maintenance and remediation should be carried out when it’s sure that the users would face minimal interruptions.