locked
Going from 2012 R2 to 2019 Essentials RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi!

    I need some help as to best move from the old 2012 R2 to a new server with 2019 Essentials on it (small clinic, no need for standard server).

    I have the old server running DC, DHCP and DNS, not much else, so that is what I need migrated, but how do I do this best?

    I can find some guides but they all go from Standard to Standard, or Esentials to Essentials, not Standard to Essentials.

    Would be nice if it was not using lots of PowerShell commands as I am not too familiar with them.

    Any help would be very appreciated!

    Monday, June 29, 2020 2:22 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    HI
    since server 2019 essentials has been removed "server essentials experience" role, there is no RWA ,no WSE dashboard ,no wse connector used for win10 computer.

    Steps are same as migration from server 2012r2 standard to server 2019 standard/2016 standard. General steps as below:
    1. Prepare your Source Server for Windows Server Essentials migration
    2. Install new wse 2019, add it to existing w2012r2 AD domain and prompt it to be replica DC.
      migrate full fsmo from w2012r2 std to wse2019.
    3. Move settings and data to new WSE 2019.
    4. Uninstall Connector on client system, the uninstallation operation will not exit system from server 2012r2 standard, so, there is no need to re-join client system to wse2019 AD domain. 
    5. Migrate other server roles DHCP and etc. to new WSE 2019 or your hardware router.
    6. Demote and remove the w2012r2 from the new Windows Server Essentials 2019 network


    Migrate from Previous Versions to Windows Server Essentials or Windows Server Essentials Experience
    https://docs.microsoft.com/en-us/windows-server-essentials/migrate/migrate-from-previous-versions-to-windows-server-essentials-or-windows-server-essentials-experience


    Step-by-Step guide to migrate active directory FSMO roles from windows server 2012 R2 to windows server 2016
    http://www.rebeladmin.com/2016/10/step-step-guide-migrate-active-directory-fsmo-roles-windows-server-2012-r2-windows-server-2016/

    DHCP Server Migration: Migrating the DHCP Server Role
    https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn495428(v=ws.11)

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.



    Tuesday, June 30, 2020 3:17 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    You can follow along here.

    https://docs.microsoft.com/en-us/windows-server-essentials/migrate/install-windows-server-essentials-in-migration-mode

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Monday, June 29, 2020 2:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    HI
    since server 2019 essentials has been removed "server essentials experience" role, there is no RWA ,no WSE dashboard ,no wse connector used for win10 computer.

    Steps are same as migration from server 2012r2 standard to server 2019 standard/2016 standard. General steps as below:
    1. Prepare your Source Server for Windows Server Essentials migration
    2. Install new wse 2019, add it to existing w2012r2 AD domain and prompt it to be replica DC.
      migrate full fsmo from w2012r2 std to wse2019.
    3. Move settings and data to new WSE 2019.
    4. Uninstall Connector on client system, the uninstallation operation will not exit system from server 2012r2 standard, so, there is no need to re-join client system to wse2019 AD domain. 
    5. Migrate other server roles DHCP and etc. to new WSE 2019 or your hardware router.
    6. Demote and remove the w2012r2 from the new Windows Server Essentials 2019 network


    Migrate from Previous Versions to Windows Server Essentials or Windows Server Essentials Experience
    https://docs.microsoft.com/en-us/windows-server-essentials/migrate/migrate-from-previous-versions-to-windows-server-essentials-or-windows-server-essentials-experience


    Step-by-Step guide to migrate active directory FSMO roles from windows server 2012 R2 to windows server 2016
    http://www.rebeladmin.com/2016/10/step-step-guide-migrate-active-directory-fsmo-roles-windows-server-2012-r2-windows-server-2016/

    DHCP Server Migration: Migrating the DHCP Server Role
    https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn495428(v=ws.11)

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.



    Tuesday, June 30, 2020 3:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This migration guide includes the following steps:

    Step 1: Prepare your Source Server for Windows Server Essentials migration. You must ensure that your Source Server and network are ready for migration. This section guides you through backing up the Source Server, evaluating the Source Server system health, installing the most recent service packs and fixes, and verifying the network configuration.

    Step 2: Install Windows Server Essentials as a new replica domain controller. This section describes how to install Windows Server Essentials, or Windows Server 2012 R2 Standard (with the Windows Server Essentials Experience role enabled) as a domain controller.

    Step 3: Join computers to the new Windows Server Essentials server. This section explains how to join client computers to the new server running Windows Server Essentials and updating Group Policy settings.

    Step 4: Move settings and data to the Destination Server for Windows Server Essentials migration. This section provides information about migrating data and settings from the Source Server.

    Step 5: Enable folder redirection on the Destination Server for Windows Server Essentials migration. If folder redirection is enabled on the Source Server, you can enable folder redirection on the Destination Server, and then delete the old Folder Redirection Group Policy setting.

    Step 6: Demote and remove the Source Server from the new Windows Server Essentials network. Prior to removing the Source Server from the network, you must force a Group Policy update and demote the Source Server.

    Step 7: Perform post-migration tasks for the Windows Server Essentials migration. After you finish migrating all settings and data to Windows Server Essentials, you may want to map permitted computers to user accounts.

    Step 8: Run the Windows Server Essentials Best Practices Analyzer. After you finish migrating settings and data to Windows Server Essentials, you should run the Windows Server Essentials Best Practices Analyzer (BPA).

    Several of the migration procedures require that you open a Command Prompt window as an administrator. The following procedures explain how to do this.
    Tuesday, June 30, 2020 3:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    I am so sorry Charles, but you list 8 steps, but I don't see a link or anything to connect to these 8 steps?

    Friday, July 3, 2020 6:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    HI
    can my solution help you ?

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, July 3, 2020 10:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    What are the current issues?

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Friday, July 3, 2020 11:48 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    HI
    Is there any progress on your question?

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, July 7, 2020 3:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi!

    I am sorry to not have answered, I have been on holiday and will be for another week, so I will not know whether it works until then :)

    Friday, July 10, 2020 4:05 PM