Windows Server Essentials 2016 Hardware Migration Where Source Cannot Reboot

Drelkor 21 Reputation points
2022-03-17T06:47:40.023+00:00

I have a 2016 Essentials server that, unfortunately, has a bad motherboard. I need to migrate the server over as I am currently unable to apply security updates as when the server reboots, it actually power cycles the power supply and that causes the system to not power up again. If it soft rebooted it would probably be fine but the hard cycle it does on reboot is just fatal to it coming back up. I was, eventually, able to get the server to boot again but it just can’t handle being powered off again as it took around a week of work days trying to boot it repeatedly before we were able to get it to come back up. I attempted to get a replacement motherboard but the cost was more than a replacement server because it was an older machine so I have obtained a somewhat newer (and better) server I would like to migrate the OS and data to. Is it possible to migrate to the destination server if the source server is not capable of being rebooted? I’ve gone through the migration documentation steps a few times and there are several sections where it calls for updates or mentions that the migration tool may restart the server but I just don’t want to risk that it may not come back online. Any assistance that anyone can provide would be greatly appreciated.

Thanks!

Windows for business | Windows Server | Devices and deployment | Set up, install, or upgrade
Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2022-03-23T18:38:12.02+00:00

    After install on new server cancel the Configure Windows Server Essentials
    Start Server Manager, Local Server
    Config static ip address (use DNS of existing essentials)
    Rename computer, and join existing domain

    After reboot Cancel the Configure Windows Server Essentials again
    Start Server Manager, Local Server
    Add Roles Active Directory, DNS
    Do Post Deployment, promo
    Make sure user is EnterpriseAdmin, SchemaAdmin, DomainAdmin groups
    Transfer roles over from old server (logged onto old server)
    (run cmd.exe with elevated)
    https://learn.microsoft.com/en-us/windows-server-essentials/migrate/step-2--install-windows-server-essentials-as-a-new-replica-domain-controller#to-transfer-the-operations-master-roles
    Config network connection properties DNS point to server's own static address
    reboot new server, then this time let the Configure Windows Server Essentials run to completion

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
  1. Anonymous
    2022-03-17T13:04:04.96+00:00

    You can follow along here to migrate to new hardware.
    https://learn.microsoft.com/en-us/windows-server-essentials/migrate/migrate-windows-server-essentials-to-new-hardware

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  2. Anonymous
    2022-03-17T13:37:46.403+00:00

    Well any migration will have a better chance of sucess if the source has been fully patched and domain health is known to be 100%. In your case you can skip those steps and hope for the best.

    --please don't forget to upvote and Accept as answer if the reply is helpful--


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.