It’s a good idea to use a computer name that is both
DNS-compatible and NetBIOS-compatible so that all types of
clients see the same name for your computer. (And yes, we’re
going to have to live with NetBIOS for a while still—too many
applications, including Microsoft applications, simply don’t
work properly without it.) To do this, keep the name to 15
characters or fewer and don’t use asterisks or periods. To
obtain the best application compatibility, use dashes instead of
spaces and underscores.
Beyond that, you should use a naming convention that has
some internal consistency. We’ve seen all sorts of naming
conventions, from the literary obscurities of naming them after
romantic poets or science-fiction characters, to Norse or Greek
gods, to colors (with the server fronts all painted to match the
color name of the server). But honestly, we like names that
actually help identify functionality, location, address,
hardware, domain, or some combination of these. So our EXAMPLE
network here includes computers with the following names:
hp160-sbs2011 (The computer is
running as a virtual machine on a Hewlett-Packard DL160SE
G6, and it’s the main SBS 2011 server.) xmpl-rds-05 (It’s running as a
virtual machine in our Example network, its primary role is
Remote Desktop Services, and its IP address is
192.168.0.5.) hp160-win7-01 (It’s running on
that same Hewlett-Packard DL160SE G6, it’s a Windows 7 VM,
and it’s the first one we created.) hp160-v32-03 (It’s running on
that same Hewlett-Packard DL160SE G6, it’s a 32-bit Windows
Vista VM, and it’s the third one we created.)
We know it’s a boring way to name things, but we think
it’s a lot easier to understand than trying to remember that
Zeus is the main SBS server and Athena is the second server running SQL Server.
|