Do you name your Virtual Machines with a standardized naming convention?

Updated by Brady Stroud [SSW] 1 year ago. See history

123
<introEmbed body={<> When your Hyper-V environment is spread across multiple hosts and contains many Virtual Servers, it can get very confusing to find the one you are looking for amongst them all. This is why you should use a standard naming convention for all your Virtual machines. </>} />

❌ Figure: ![Bad Example - How do you know what machine is what?](/uploads/rules/name-your-virtual-machines-with-a-standardized-naming-convention/naming-badexample.jpg)

The standard we use for Production Virtual Machine naming is as follows: NetBIOSName-ServiceName. For example: Falcon-SCVMM.

The standard we use for Development Virtual Machine naming is as follows: DEV-NetBIOSName-ServiceName-DeveloperInitials. For example: DEV-demo2010a-SP2010MSInfoWorker-JL.

✅ Figure: ![Good Example - It is easy to tell which VM is which when they are named to a standard](/uploads/rules/name-your-virtual-machines-with-a-standardized-naming-convention/naming-goodexample.jpg)

Acknowledgements

Matthew Hodgkins
Related rules

Need help?

SSW Consulting has over 30 years of experience developing awesome software solutions.

We open source.Loving SSW Rules? Star us on GitHub. Star