The primary concerns are that:
1. New computers have a consistent but unique name
2. Rebuilt or upgraded computers (whether physical or virtual) or computers that have OS reinstalled are given the same name as the name as the original computer with a new number appended . Eg: Customer-PC-01 becomes. Customer-PC-01-02
New computers should NEVER have a number appended to an old name. For example, if you are replacing XYZ-CO-06, and the last computer installed is XYZ-CO-17, the new computer should be XYZ-CO-18. Do not use XYZ-CO-06-02. This is confusing.
If a computer has the OS reinstalled or is rebuilt and it's the same physical computer, then add a number to the old name. So in this case, XYZ-CO-06, if rebuilt, would be called XYZ-CO-06-02.
If the name the customer has given the computer doesn't make sense, ask customer for permission to change it. If you are not a tech, please confirm (with a GGIT tech) that it will not effect any network shares, etc. before renaming.
Do not change the name in a way that demeans the customer or makes it seem as if we don't know the customer's name, just for the purpose of saving a few letters. (Actual real-life examples from previous techs: changing McGoff to Goff or Pestcoe to Pest).
The Windows limit on the number of characters in a device name is 15. If you rename a computer via RMM, the RMM agent may accept more than 15 characters, but the actual resulting host name will be truncated. It is best to choose hostnames with no more than 12 characters, in case we ever need to append a new number to the name (e.g., Custum-PC-01 > Custum-PC-01-02).
For Hyper V Hosts - Special Considerations