Change Name of Server Running Windows Server 2022

Adrian Bruno 20 Reputation points
2023-10-20T13:41:58.94+00:00

Greetings and salutations fellow posters. My company recently upgraded one of our servers to the Core version of Windows Server 2022 and we have been unable to change its name in HyperV Manager. For whatever reason, the server appears with the domain name attached in HyperV Manager despite it not having the domain name on the server itself. It is attached to the domain, and we believe the name became attached because of Server 2022 itself. For example, our servers are labelled as follows:

  1. HYPV01-XXX
  2. HYPV02-XXX

The one that needs its name changed is listed as:

  1. HYPV08-XXX.DOMAINNAME.PRI

We simply need to remove the "DOMAINNAME.PRI" portion from the name of the server, but we cannot find a way of doing so. Any insight on this issue is greatly appreciated.

Thank you,

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,636 questions
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2023-10-23T14:16:16.8833333+00:00

    It appears to be some setup configuration on the new one to where the Select Computer browse dialog does not find the host name but instead only returns the FQDN which is how you see it listed in Hyper-V manager.

    Some ideas here with that one

    https://serverfault.com/questions/44030/local-dns-not-resolving-host-name-but-will-resolve-fqdn

    but getting off in the weeds here. You could close up this one here and start a new thread to discuss this new problem. Please don't forget to close up the thread here by marking answer if the reply is helpful--


5 additional answers

Sort by: Most helpful
  1. Anonymous
    2023-10-20T18:26:45.58+00:00

    I don't think that's it exactly. This appears to be a DNS (or configuration) problem where this particular host wasn't able to be found by host name when you browsed to add it (Connect to Server dialog) but instead found only the FQDN and so hyper-v manager is happily using that name.