I've been unable to get the Server Essentials Role uninstalled. The PowerShell command starts the process and it looks like it's running fine but at some point (the last time was 57%) it hangs for a long period of time with no activity then fails for a timeout stating that the process didn't complete in the time allotted. I'm not seeing any entries in the Application or System log that indicate a problem. I'm not sure where to go from here. Is it possible just to bypass this step? Should I try running it from the Roles removal? I would think the PowerShell command is the same command that the Roles removal application uses. This server was installed with Windows Server Essentials 2016 and not Server 2016 with the Essentials Role added after the server installation if that makes a difference.
Thanks! I have a couple of other questions. Once I remove the AD Certificate feature will that server continue to function normally? They weren't using any of the remote functions on that server and I'm not sure I ever even ran the remote connection wizard. I'm asking because I would like to press on with anything I can get done during business hours but I don't want to disrupt the server function while I'm waiting for a time window to complete the migration.
I think I can also move the FSMO roles and cleanup the Active Directory and DNS without an issue during business hours as well. Is that correct.
If the Certificate Authority (CA) was utilized solely for the Essentials Experience component of the Source Server, it means it facilitated communication between the Connector software and the Essentials Dashboard. This is unrelated to remote access, which typically requires a certificate from an official CA. Therefore, backing up and removing that role should not pose an issue. However, be mindful that a restart is often necessary after the CA's uninstallation process is complete.
When you transfer the FSMO roles to a new Domain Controller and migrate DHCP as outlined in the kit, but do not assign the old IP address to the Destination Server, you must update the DNS server IP address in the DHCP scope. Conversely, if you change the IP address on the Destination Server to match the Source Server's IP address, no additional steps are required.
Hope this helped...
Perfect. That's just what I needed. I'll need to wait on CA removal due to the reboot requirement. I have a plan of action now. Have a good one!
Hello Lesa,
I recommend proceeding with the subsequent steps in the kit. If everything else progresses smoothly, it's not a significant concern if something remains on the old Windows Server 2016. The crucial step is to back up and remove the CA, then demote the server. Once that's completed, you should be all set. Should you encounter any issues with the demotion, please inform me, and I will take a look.
Kind regards, Mariëtte