We have some servers that were upgraded in-place from 2008 R2 to 2012 R2. While they were running 2008 R2 alternate computer names were added to them with netdom computername <computer> /add:<alternate-name>
. Now we're in the process of killing the 2012 R2 servers and moving their functionality to new 2022 servers, the problem we're facing is that the alternate computer names cannot be removed from the 2012 R2 servers. Running netdom computername <computer> /remove:<alternate-name>
results in:
Unable to remove <alternate-name> as an alternamte [sic] name for the computer.
The error is:
The system cannot find the file specified.
The command failed to complete successfully.
%errorlevel%
is 2.
We cannot add the alternate names from the 2012 R2 servers to the new 2022 servers until the alternate name is removed. Removing the computer object in AD allows the alternate name to be created in 2022, but the servers are being gradually decommissioned so this would be a last resort.
I've verified that it's the in-place upgrade is causing the error by
- Installing a new clean 2008 R2, not domain joined or anything.
- Adding an alternate name, confirming that the remove works.
- Running in-place upgrade, confirming that the remove of the name added in 2008 R2 doesn't work.