Ask a question

Jeff Bowman

Installing WSE 2016 onto an existing domain that has a peer DC

Is there a migration guide available that covers these steps:

  1. Installing Server 2022 Standard as a peer DC (to our current WSE 2016 PDCe)
  2. Migrating the FSMO roles to the new DC
  3. Reinstalling WSE 2016 (without the WSE bits)
  4. Syncing the AD and moving the FSMO roles back
  5. Installing the WSE 2016 bits onto the new PDCe
I'm pretty sure I can do it unassisted, but I'd like to have a reference at easy hand to make sure I don't miss anything. The devil is in the details, as we know.
 
Thanks,
Jeff Bowman
Fairbanks, Alaska

 


asked10/08/2022 06:03
44 views
Add Comment
Last Activity 10/10/2022 04:48

2 Answer(s)

  • Mariette Knap
    Add Comment
    Jeff Bowman

    uninstall the Essentials part from the 'old' WSE server

    Hm, interesting. I didn't realize that that was even possible.

    It sounds as though you approve of the approach I've outlined, so that helps. And I see here how to do it.

    But could you explain why it should be uninstalled? That VM and its VHDX are going to be deleted immediately after demotion, so I'd expect that it wouldn't matter.

    Thanks,
    Jeff Bowman
    Fairbanks, Alaska
     

    Mariette Knap

    I am wondering what you are trying to do? Do you need to fix an issue at the current WSE server? Where is the 2022 DC going when you are done?

    But could you explain why it should be uninstalled? That VM and its VHDX are going to be deleted immediately after demotion, so I'd expect that it wouldn't matter.

    You are replicating the AD if you introduce another DC (the 2022) and because of that you must remove the Essentials Experience stuff as it is bound to parts of the AD. The same is valid for the CA, you must uninstall that before you remove the Essentials Experience role.


    replied 10/09/2022 13:47
    Jeff Bowman

    I am wondering what you are trying to do? Do you need to fix an issue at the current WSE server?

    I need to rename our WSE 2016 PDCe, as we're inserting a Hyper-V replica server into the mix and we would like to maintain our incremental naming conventions.

    Actually, come to think of it... after the domain leave I could just rename it, rejoin the domain, promote it and migrate the FSMO roles. I shouldn't need to reinstall at all. Everything's healthy—why throw away all that work?

    Wouldn't you agree?

    Where is the 2022 DC going when you are done?

    It'll stay in place as a failover AD/DNS server.

    Thanks,
    Jeff Bowman
    Fairbanks, Alaska


    replied 10/09/2022 20:18
    Mariette Knap

    OK, no I do not agree. I would do a fresh install of the WSE.


    replied 10/10/2022 04:48

    Reply
    replied 10/09/2022 13:26
  • Mariette Knap
    Add Comment
    Jeff Bowman

    This looks good, thank you.

    So I assume that installing the WSE bits after I've installed the server, joined the domain, promoted it and migrated the FSMO roles is done in reverse of the above, via Server Manager Roles and Features?

    Thanks,
    Jeff Bowman
    Fairbanks, Alaska
     

    Mariette Knap

    Yes, that should work and if it does not send me a note and I will help.


    replied 10/09/2022 15:14
    Jeff Bowman

    Thank you very much, Mariette.

    You're OK 🙂

     

    Thanks,
    Jeff Bowman
    Fairbanks, Alaska
     

     


    replied 10/09/2022 15:18

    Reply
    replied 10/09/2022 15:04
Add an Answer