Changing server computer name

Question

Hi,

One of our server with Windows Server 2008 R2, the DC, is down and I am trying to find solutions to promote our second server with Windows Server 2019 to DC as well to change the server name to match the original DC as someone set up the main server in VMware without passing down the admin and root password or the password is lost. Is it safe to change the server name to match the DC and promote it to DC? Please help me.

Thank you

Answer 1

Ok, if you have no backup to restore from then there's nothing to do but create a new domain. You can name the new server the same (as old one) and create the new domain with the same name but under the hood the domain GUID is different so you'll need to join the members to this new domain.

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

Answer 2

The simplest solution is to seize roles (if necessary)
https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/transfer-or-seize-fsmo-roles-in-ad-ds

then perform cleanup to remove remnants

https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup
https://techcommunity.microsoft.com/t5/itops-talk-blog/step-by-step-manually-removing-a-domain-controller-server/ba-p/280564

The two prerequisites to introducing the first 2019 or 2022 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2019 or 2022 (with the desired computer name), patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health.

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

Answer 3

demoted the new server back to global controller

I'm afraid there's no such thing. So if I understand correctly the only domain controller you had now has failed. If you have no backup to restore from then there's nothing to do but create a new domain. You can name the new server the same (as old one) and create the new domain with the same name but under the hood the domain GUID is different so you'll need to join the members to this new domain.

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

Answer 4

Hi,

Thank you @Anonymous for the reply.

I can't seize the roles since the first server with Windows 2008, it can't be accessed anymore. I managed to replicate it to the new server, Windows Server 2019, before it is down. The problem is its not promoted to domain controller yet that is why I wonder if I can promote it to domain controller safely as well change the server name to match the old server as it gives error notification about DFSR ?

Answer 5

managed to replicate it to the new server, Windows Server 2019, before it is down. The problem is its not promoted to domain controller yet

Can you explain this a bit more? If the 2019 has not been promoted then what did you mean "managed to replicate it to the new server"? Hopefully the 2008 was not the only domain controller.