Best practices for computer names on a large network?
May 20, 2008 5:53 PM Subscribe
I need to come up with a conventional naming scheme for 200+ computers in my organization. Help!
posted by joshrholloway to computers & internet (27 answers total) 3 users marked this as a favorite
I came on board with my organization almost six months ago. When I first arrived, there was no standardized way to name computers. They vary from things that slightly make sense to things that make no sense at all. Now IT has decided to set forth a conventional naming system for at least all the workstations on our network, and we're kind of butting heads over what it should be.
We had actually decided on a convention about a month ago and began using it, but it quickly became cumbersome and we ran into some issues. The convention we were using is as follows:
* aaa = three-letter code for the computer's location
* b = floor number of the location
* yyy = three-letter code indicating the OS of the computer
* z = version number of the OS
* xxxxxx = primary user's last name and first initial
So, for example, my computer under this system is named fpp1osx5-hollowayj. As you can imagine, we ran into issues on the Windows boxes with the machines and therefore our inventorying software truncating the NetBIOS names to 15 characters.
Some things we have considered are locations, floors, departments, OS information, user information, etc. We don't know what's best to include and what's most useful to us or even our end users. I know you don't work where I do so you can't come up with the perfect system for us, but I'd love to know what has worked for you in the past.
Thanks in advance for your input!