A former company I worked at used names of food. Lettuce, Bacon, and Spaghetti, are some notable ones that come to mind. Phillip Partipilo Parametric Solutions Inc. Jupiter, Florida (561) 747-6107
_____ From: Damien Solodow [mailto:[EMAIL PROTECTED] Sent: Monday, April 14, 2008 11:12 AM To: NT System Admin Issues Subject: RE: Naming convention for Servers My preference has always been to use names with some kind of theme (animals, gems, etc) and to make sure they are pronounceable and something that can be spelled. It's much easier to tell the Helpdesk that what they're looking for is on "sapphire" then on "inusfsrv01" From: Sherry Abercrombie [mailto:[EMAIL PROTECTED] Sent: Monday, April 14, 2008 11:07 AM To: NT System Admin Issues Subject: Re: Naming convention for Servers Farm animals, now that's funny. Back in the day of Novell servers around here we had one named HAL. On Mon, Apr 14, 2008 at 9:57 AM, Rankin, James R <[EMAIL PROTECTED]> wrote: Which means you can keep contractors like myself happy by calling your Exchange 2007 server "EXCHANGE2007", instead of UKZZ3242B1 However I quite like the idea of my current company, whose Citrix farm servers are named after farm animals. -----Original Message----- From: Kurt Buff [mailto:[EMAIL PROTECTED] Sent: 14 April 2008 15:53 To: NT System Admin Issues Subject: Re: Naming convention for Servers Mr. Happy Hacker will defeat this obscurity in about 30 seconds with nmap, or other port scanning tool of choice. On Mon, Apr 14, 2008 at 7:16 AM, Clayton Doige <[EMAIL PROTECTED]> wrote: > > > > > The only reason you might want to stay away from a naming convention is > security. If a hacker gets on your network and can enumerate your servers > they will see E2K3FE or SQL05CRM (for example) and know what they are > hitting, thus making it easier for them to find what they are after. > > > > > > From: Rishi Kumar [mailto:[EMAIL PROTECTED] > Sent: 14 April 2008 14:39 > > To: NT System Admin Issues > Subject: Naming convention for Servers > > > > > I have a general question that I'd like to put up for discussion. > > > > I work for a medium size company with about 50 servers. > > > > Most of our domain controllers and exchange servers have random > names..(These are not real) but something like George, Gertrude, etc. > > > > I am one of TWO system admins. or let's say 3 sys admins, including my > supervisor. > > > > I have been pleading to start using a naming convention for the last several > months as it is now getting confusing to remember which sever performs which > function and which office it is located. (We have 7 different office > locations throughout the country). > > > > Is there really a good reason to NOT have a naming convention? > > > > > > > > > > **************************************************************************** ******** > This footnote confirms that this email message has been scanned by > PineApp Mail-SeCure for the presence of malicious code, vandals & computer > viruses. > > **************************************************************************** ******** > > > > > > > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ -- Sherry Abercrombie "Any sufficiently advanced technology is indistinguishable from magic." Arthur C. Clarke _____ If this email is spam, report it here: http://www.OnlyMyEmail.com/ReportSpam <http://www.onlymyemail.com/view/?action=reportSpam&Id=ODEzNjQ6NjAyMzkyOTA3O nBqcEBwc25ldC5jb20%3D> ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
