I can’t believe that no one has mentioned Tolkien characters. I think at one point, 73% of all machines on the internet were named either “frodo” or “bilbo”.
I can’t tell you what I use for servers in my office or at home currently, but at one point, I had great fun naming machines after vitamins* - vitaminC, niacin, iron, magnesium.
Game elements work: King (PDC), Queen (BDC), Knight (Proxy), Pawn01/Pawn02 (web or file server).
As an avid hiker, I also like summit names: Isolation, Owlshead, Kinsman, etc.
The most appropriate, and hence, least fun method is to assign useful names to the machines. A common method might include the OS, location, and function (or order), for example: NTPORT03 might refer to the third NT machine in Portland. LXATLAWEB01 might refer to a Linux web server in Atlanta. The key is use a name of static length and stick to the format - 2-char for OS, 4-char for location, 2-char for function or order. Whatever works for you. Anything longer than about 8-char will be difficult to use and remember effectively.
[sub]* when I was younger and hosting DDD&D games nearly every weekend, players who couldn’t think of names for their characters were immediately assigned a random vitamin name, such as Riboflavin, the half-elf. :)[/sub]
Using users is a pain in the arse but it really does get to the root of the problem (assuming you keep on top of it) when you have a problem.
If that’s not doable, then name them according to department.
Sales1
Sales2
Acctng1
Acctng2
Shipping
President
VicePres
etc…
This gives you a more definitive idea of where the computer is located. Yes, as you move computers around you will have to remember to rename them on your network but again, if you need to trouble shoot a lost connection you no exactly where that machine is without having to refer to some list.
Dog breeds would be a popular suggestion in this office (we publish pet books), but I’m not going to do that.
I think I’ll probably go with names of elements or something clinical/professional like that (I don’t think porn star names or sexual positions would sit too well with the board of directors.
You as an IT manager or whatever your function is, should make it as easy as possible for an incoming IT manager to figure out.
If you die in an accident, it should make sense. If you are fired (God forbid but we all are expendable) then the computer naming system should make sense.
It doesn’t have to be anything cutsie and fun, but something that any moron could come in and figure out.
I know that sounds bland and possibly inappropriate but make it as easy on you as if you found a better job but liked the place you work for now. That’s my rule of thumb when it comes to a naming convention for computers.
I almost worked as a network admin for Keebler, and most of their production servers were named things like “Ernie”, “Fudgie”, etc. BLEH.
I’ve named systems after the seven deadly sins, which is always good for a hoot. But right now, I name machines according to what they do, which gives you such exciting and thrilling machine names as “FIREWALL01”. Ooooo…aaahhh!
In all seriousness, at work, I generally name computers on who’s sitting at them because it’s a lot easier for me to find that person than remember where their computer might be. If no person is there, I go by function.
Of course if that person is annoying I’ve been known to call their machine insulting names. I remember one christian zealot whose machine I named “SatansDeathMachine.” She never noticed.
Our former IT person was a hockey nut so he named all the computers after NHL team nicknames. I was disappointed to learn I’d been assigned some crummy expansion team’s name.
Hmmm, I would think quite the oppisite actually.
In order to make youself non-expendable, I would say “make the naming system something that you, and only you can understand.” :D:D:D:D:D:D
Mine will be Camenbert, the mail server will be Leerdammer, other workstations will include Castello, Roquefort, Stilton, Wensleydale, Parmesan, Halloumi, Gorgonzola, Caerphilly and of course Cheddar*
