The official blog for Windows Server Essentials and Small Business Server support and product group communications.
EPS Team Blogs
[Today's post comes to us courtesy of Ajay Sarkaria, Rituraj Choudhary, Harshal Charde and Sandeep Biswas from Global Business Support]
The purpose of this post is to help you successfully migrate from a previous Windows Server SKU, Small Business Server SKU, or a Windows Server Essentials SKU current in Product Lifecycle to Windows Server 2012 R2 Essentials.
If your business has up to 25 users and 50 devices, you may migrate to Windows Server 2012 R2 Essentials. If the count extends up to 100 users and 200 devices, to use the features empowered by Windows Server Essentials role, you must migrate to the Standard or Datacenter editions of Windows Server 2012 R2 and install the Windows Server Essentials Experience (ServerEssentials) role.
The content on this blog extends from the content found at Prepare your Source Server for Windows Server 2012 R2 Essentials migration. Use the following annotated checklist to keep you on track.
Understand what setup will do for you and what you need to do manually.
Windows Server 2012 R2 Essentials technical training series now available on Microsoft Virtual Academy.
You might find an answer to a question you have, seek advice on your migration plan, or simply see what others have encountered that you might not have considered.
This way you know what to expect. This also allows you to test the hardware and verify you have the necessary BIOS updates and drivers.
If there is only one DC, make sure the SYSVOL and NETLOGON shares are present. Also, check the File Replication Service event log to see if it is in Journal Wrap. The event below is an example of what to look for.
Event Type: Error Event Source: NtFrs Event ID: 13568 Description: The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
If there are multiple domain controllers in the source environment, force an Active Directory replication between them in Active Directory Sites and Services and verify it is successful.
You can also run the Microsoft IT Environment Health Scanner in the source environment to uncover any AD health issues.
Microsoft IT Environment Health Scanner
An unhealthy Active Directory can result in Windows Server 2012 R2 Essentials migration installation failure.
Make sure the Primary group is set to something besides Domain Admins, Enterprise Admins, or Schema Admins. In the properties of the user account, click the Member Of tab, and at the bottom look for the Primary group.
939820 Events 1925, 1006, 1645, 1055, 40961 on a Windows Server 2008-based domain controller or error message: "No authority could be contacted for authentication" when you use Remote Desktop Connection.
If you have a deadline set for an update in WSUS that is past-due, your Windows Server 2012 R2 Essentials setup can fail when the update is automatically installed and the Windows Server 2012 R2 Essentials is rebooted. We recommend disabling WSUS on the source server for the duration of the migration. For this, on the source server, open IIS Manager, and stop the “WSUS Administration” site.
Similar to the point above, your Windows Server 2012 R2 Essentials setup can fail if something outside of it initiates a server restart while it’s in the middle of its setup routine. Things to keep an eye out for:
From now until the Windows Server 2012 R2 Essentials migration setup is complete, do not make any changes on the network. This is not a good time to be doing any of the following:
If you don't have that entry, do a right-click edit on top of the policy on the left pane, navigate to the location you just checked and edit the right to add the missing value.
Depending on the Target Operating System edition, Follow one of the below blogs:
On subsequent posts we will cover documentation and tips to help you recover if you have encountered an issue during or post migration.
Hi,Thanks for the article. I am a little stuck on the order of migration despite reading numerous posts and blogs.I like many others it seems am planning on migrating from SBS 2003 to 2012 Essentials R2, with a 2008 R2 server running Exchange 2010.Now, I have built the Essentials box (but not yet logged in for the first time), and have built the new Exchange server (without yet installing Exchange) and joined that box to the domain....Whats my next step!?!? Run with the Essentials configuration in an existing AD domain, or install Exchange 2010 into the 2003 Domain and migrate that, then run with the Essentials config for existing AD domain?!?! Any further info / guidance would be much appreciated!
The subject of this article seems to be applied to migration of SBS 2003 to Server 2012 R2 Essential. But when I tried to start the migration, I didn't see any way that 2012 can join 2003 domain thru Active Directory Service or Essentials Experience role.
Does anyone able to do it?
Excellent article. I did encounter a problem that seems to be common to happen to others, where the Essentials Configuration Wizard will fail to complete. The fix is to add domainname\ServerAdmin$ to the "Default Domain Controller Policy"
The username needs to be added under COMPUTER CONFIGURATION>POLICIES>WINDOWS SETTINGS>LOCAL POLICIES>USER RIGHTS ASSIGNMENT>Log on as a service. For example if your domain is company.local, you would add company\ServerAdmin$