Star Trek & Using Industry Terminology.... (Score 1)

In the various companies I've worked in, Star Trek played the biggest role in naming servers... Dax was a Sun box that simply never died... Worf handled the firewall at one place... Picard was a Netware 4.11 that had the root NDS partition, McCoy was used to bring back to life or test broken equipment... Troy monitored the network, and seemed to have this psychic ability to know when to page us at the worst possible time.... Scotty was the central backup server - it was never fast enough, and when we pushed for faster throughput, it 'couldn't handle that keena speed!'....

At my current position, I work for a geotechnical company - so all the servers are named after rocks... Granite is the primary server, basalt, felspar, dolomite, etc... Using names that are known in our industry helps... The users don't need to know what server is doing email, web, database, etc... I prefer transparent networks, so the users don't get in a knot on where to find things... I name printers after trees simply because they are spitting out dead cousins..... Workstations are named after their primary user, use or location.... I even go as far having logical drive mappings - U:\ for users, T:\ transfer, P:\ applications, etc. It's all the same in the different offices... Since some employees work in multiple offices, they don't have to learn a new network topology...

If you're interested, I wrote a few years back a Netware Directory Service Suggested Naming Standards for NDS objects.... NDS Naming Guidelines

Maybe worthwhile, YMMV...

.mark