[Today’s post comes to us courtesy of Rong Yu from Windows Server Essentials Team]
Hi my name is Rong Yu, program manager on the Windows Server 2012 Essentials team. Today, I’d like to give an overview of how to migrate to Windows Server 2012 Essentials from another server. One common scenario for migration is that users want to upgrade from a previous version of Windows Small Business Server (Windows SBS) or Windows Server. You may also need to migrate from another server running Windows Server 2012 Essentials in the case of a hardware upgrade.
The online migration guides provide detailed step-by-step instructions for migrating to Windows Server 2012 Essentials. Select the right guide based on your Source Server. We highly recommend that you read through the migration guide that you select before you start a migration. At a high level there are three phases involved in a migration:
If the Source Server is a previous version of Windows Small Business Server or another server running Windows Server 2012 Essentials, you’ll need to complete all data migration within 21 days after the server is set up and repurpose the Source Server afterwards.
If the Source Server is a server running Windows Server Foundation or Windows Server Standard, there is no such a requirement, and you can actually keep the Source Server coexistent with the Windows Server 2012 Essentials server. For example, you may want to continue to use the Source Server as a file server or a secondary domain controller.
In Windows SBS 2008 Standard and Windows SBS 2011 Standard, you must provide a migration answer file to enter into the migration setup; for Windows Server 2012 Essentials, that’s no longer a requirement. Windows Server 2012 Essentials provides an end-to-end user interface (UI) flow during setup to guide users through the migration.
When you enter into the Initial Configuration phase, Windows Server 2012 Essentials provides the option to do a clean install or a server migration from an existing server. Select the migration option.
The next page adds some requirements for starting the migration setup.
After you complete a successful run of the Migration Preparation Tool on the Source Server, you can proceed to the next page of the wizard. The next two pages ask for information about the Source Server and the existing domain.
On the next page you can personalize the new Windows Server 2012 Essentials Destination Server by providing a server name as well as your company name.
On the next page you can configure settings to keep your server up to date. It’s the same page that you see in the clean setup flow.
That’s all the user input needed. The actual installation takes place afterward.
One of the improvements we made for migration in Windows Server 2012 Essentials is on error handling during the domain join phase in setup. In the previous version of Windows SBS, if setup encountered an error when joining to the existing domain, it would just fail. You would have to fix the issue and then restart the whole setup. Windows Server 2012 Essentials will display an error page and allow you to resume the setup after fixing the issue, as shown on the following page.
After the setup completes, you’ll see the following success page.
To complete the post-setup migration tasks, please see the migration guide.
Note: You can also run migration mode setup in an unattended fashion by providing a cfg.ini file. For more information about unattended deployment, see the Windows Server 2012 Release Candidate Essentials Assessment and Deployment Kit and the associated Help topic Create the Cfg.ini file.
Windows Server 2012 Essentials no longer contains a built-in email service. However, as mentioned in the blog post entitled Email Options Supported by Windows Server 2012 Essentials, it supports multiple email options including Office 365, an on-premises server running Exchange Server, and third-party hosted email services.
Migrate to Office 365
If you have chosen to use Microsoft Office 365 as the email solution for your domain, follow the guidance in the Office 365 topic Migrate All Mailboxes to the Cloud with a Cutover Exchange Migration to start the email migration to Office 365. We recommend that you complete the email migration before you install Windows Server 2012 Essentials in migration mode.
Note: Office 365 does not support the use of public folders. For guidance about how to move messages from Exchange Public Folders to Office 365, see Migrate from Exchange Public Folders to Microsoft Office 365.
Migrate to an on-premises server running Exchange Server
If you want to use an on-premises server running Exchange Server as your email solution, you need to install Exchange Server on a second server and then migrate the data from your previous server running Windows SBS. To migrate to Exchange 2010, go to the Exchange Server Deployment Assistant and select an upgrade option based on your Source Server version; you are then provided with detailed setup and migration instructions.
For additional configuration tasks required to enable the integration of Windows Server 2012 Essentials with an on-premises server running Exchange Server, see Integrate an On-Premises Exchange Server with Windows Server 2012 Essentials.
Note: Exchange 2013 Preview is available for download and test. However this version does not support production environments. You’ll need to wait for the RTM version to migrate to Exchange 2013.
Migrate to a third-party hosted email solution
Obviously there is not a standard migration process that works for all hosted email services. If you are using a third-party hosted email solution, you should consult with your service provider and follow the guidance given to migrate your mailboxes from an on-premises server running Exchange Server to the hosted email service.
The general process for migrating to Windows Server 2012 Essentials involves Source Server preparation, an installation of Essentials in migration mode, and post-setup data migration. You should also create a plan for email migration. Due to the complexity of migration, we highly recommend that you create a test environment and then go through the migration process at least once before doing a migration in a production environment.