An unhealthy Active Directory can result in Windows Server 2012 R2 Essentials migration installation failure .8. On the Source server, check the Primary group of the account you will use to install the Windows Server 2012 R2 Essentials server into the domain.
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.
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.12. In the source domain, disable anything that may install software on machines added to the domain.
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.16. Start the Migration Process
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.