Share via

How do I change the name of my Dell PowerEdge R440 Without conflicting with AD

Garrick Whetstine 0 Reputation points
2026-06-04T16:03:34.15+00:00

I have a Dell PowerEdge R440 on Windows server 2019 Small Business Server. I tried to change the name of it in settings, but I couldn't log in getting the error "The security database on the server does not have a computer account for this workstation trust relationship." I tried a variety of things to fix this, but I don't have the local admin credentials. I've managed to fix by reverting it to a previous image backup.

How do I change the name of the server without running into the same issue again?

The server is a Domain Controller. It's the only Domain Controller

Windows for business | Windows Server | Directory services | Active Directory
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jason Nguyen Tran 18,725 Reputation points Independent Advisor
    2026-06-04T16:46:15.73+00:00

    Hello Garrick Whetstine,

    Renaming a Domain Controller is a sensitive operation, especially when it is the only DC in your environment. The error you encountered happens because changing the name directly in Settings breaks the secure channel between the domain and the controller.

    The supported way to rename a Domain Controller is to use the netdom computername command or PowerShell, which updates both the local system and Active Directory records consistently. For example: netdom computername CurrentName /add:NewName followed by netdom computername CurrentName /makeprimary:NewName. After that, a reboot is required. This ensures the trust relationship remains intact. It’s also critical to have local administrator credentials before attempting this, since domain credentials alone may not be sufficient if something goes wrong.

    Because this is your only Domain Controller, I strongly recommend taking a full backup of both the system and Active Directory before proceeding. If possible, test the rename process in a lab environment first. Another safe option is to promote a temporary second Domain Controller, rename the original, and then demote the temporary one once everything is stable.

    I hope this guidance helps you avoid the same issue again. If you find this answer useful, please hit “accept answer” so I know it addressed your concern.

    Jason.

    Was this answer helpful?

    0 comments

Your answer

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