August 30th, 2005, 03:30 PM
Whatever you do, UAnimosity, don't try to be funny. I set up a simple domain for a doctors office and his remote office. I named the domain Human. The servers were named after viruses/diseases, the workstations after organs.
After all was said and done, a network tech was running through the exchange logs for something and noticed that userx had logged into hiv and was not the primary user. (or something to that effect)
Anyway, the Doctor was not happy about the server name. I had to rename all the servers and workstations. At least I got to keep the domain name.
August 30th, 2005, 05:38 PM
You can use the last two octets of the IP address. Makes it easy and since you have to remember them anyway.....what the heck.
August 30th, 2005, 06:47 PM
interesting naming schemes, especailly that shakespeare one, i thought that was quite well done.
MOst organizations i know dont really a sense of humour when it comes to their network. they're a buisness enviroment and dont really want humour clouding your tasks.
Still, it was a nice try.
August 30th, 2005, 06:59 PM
I like famous guitar players, and pink floyd songs. Keeps me chucklin.
(kr5kernel at hotmail dot com)
Linux: Making Penguins Cool Since 1994.
August 30th, 2005, 09:34 PM
I usually use elements for the workstations (oxygen,nitrogen) and scientists for the servers ( einstein, newton)
August 30th, 2005, 10:44 PM
what we used at my old gov't job was pretty much like what TechGrunt said.
First two-four are city, second two are state, next three describe the machines function, last three are digits because of how many of each machine we had.
sf = san francisco
ca = california
snf = server, novell, file
001 = the first of these machines in the SF location
this scaled to huge proportions... the network had over 2 million machines (servers, workstations and "others") on it
Give a man a match and he will be warm for a while, light him on fire and he will be warm for the rest of his life.
August 30th, 2005, 11:10 PM
I've seen many places do exactly what TechGrunt and Lv4 described.
Star Trek names (Laforge, picard, enterprise, voyager)...then they get into clustered systems...Riker01 Riker02, etc. It get's ugly. Then, you can see the corporate mentailty shift as they start a uniform standard that helps categorize devices and locales.
UNYCOS001 < Unix, New York, Corporate site, Server #001
WNYCOW015 < Windows, New York, Corporate site,Workstation #015
WNYCON095 < Windows, New York, Corporate site, Notebook #095
While it works, if you know the code, it's ugly. I personally like theme's, such as catch and others have mentioned. Great thinkers, artists, musicians...I have a friend who has the horsemen of the apocalypse on his home network...what ever you like.
I would prefer not to see smtpmail1, exchange04, oradb, etc. in server names...but using a letter or two to help a group of employees quickly recognize the function is probably fine. It leaves less to the imagination though.
"Data is not necessarily information. Information does not necessarily lead to knowledge. And knowledge is not always sufficient to discover truth and breed wisdom." --Spaf
Anyone who is capable of getting themselves made president should on no account be allowed to do the job. --Douglas Adams (1952-2001)
"...people find it far easier to forgive others for being wrong than being right." - Albus Percival Wulfric Brian Dumbledore