We actually did this on a network that I ran for a while. Servers were birds of prey (kestrel, hawk, eagle), internal servers were flightless birds (kiwi, ostrich, etc.) Mac workstations were waterfowl (mallard, egret, swan, flamingo), laptops were rodents (rabbit, woodmouse, groundhog), fileservers were large herbivores (rhino, hippo, etc.) Linux workstations were types of deer and related species (ibex, impala, moose) and I reserved the entirety of aquatic invertebrates for naming Windows workstations (cuttlefish, octopus, squid, sponge, sea_cucumber) but that might just be personal prejudice. The other aspect of this that worked nicely, is that I reserved names for various floors in the building or remote locations for different geographical areas, so I knew that hippo was a fileserver on the 2nd floor of the main office (Africa) while bison was a fileserver on the 1st floor (North America). This requires a bit of pre-planning since you are allowed more linux workstations in Africa than in South America, but on the plus-side, almost all of those names are your spellchecker, and a lot of them, people have actually heard of which mean fewer errors and questions. It also gives you a simple way to physically identify the host -- I put little pictures on the cases.