Renaming computer on Active Directory

[talksr]

Hello there.

One of the sites I work at has RM CC4. One of the more useful features I have found with CC4 is the ability to rename a domain connected computer without having to log into it locally, remove it from the domain, log in again, change the name, reboot and then re-join to the domain.

 

Does anyone know if and how this is possible on a vanilla install of Server 2008, 12 or 16? With Windows 8 or 10 stations.

 

It can be really handy if, for example, a station is moved to a completely different area, or if the naming conventions are changed.

Edited January 13, 2017 by talksr

[ChrisH]

Remote powershell or a remote tool to run netdom such as Psexec or something?

[GuyJD]

Yep I rename mine with with this Powershell line

 

Rename-Computer -ComputerName {current name} -NewName {new name} -DomainCredential {domain\username} -force -passthru

 

Obviously replace the bracketed text with your local details

Edited January 13, 2017 by GuyJD

[talksr]

Yep I rename mine with with this Powershell line

 

Rename-Computer -ComputerName {current name} -NewName {new name} -DomainCredential {domain\username} -force -passthru

 

Obviously replace the bracketed text with your local details

 

Thanks! Will give this a try.

[simpsonj]

Yep I rename mine with with this Powershell line

 

Rename-Computer -ComputerName {current name} -NewName {new name} -DomainCredential {domain\username} -force -passthru

 

Obviously replace the bracketed text with your local details

 

That's brilliant! Thanks

[talksr]

Works a treat. Thanks!

 

N.B. This failed several times initially because of a failure to establish a WMI connection to the computer. This was rectified by disabling the firewall on the computer in question.

[GuyJD]

Works a treat. Thanks!

 

N.B. This failed several times initially because of a failure to establish a WMI connection to the computer. This was rectified by disabling the firewall on the computer in question.

You can put an exception in the firewall for WMI via group policy, that should stop any further issues and keep the firewall protection in place.

[Michael]

Normally (top of my head), it'll disable the old computer object in AD and create a new object, but I'm not 100% sure top of my head if this is still the case?