Why is the parent post not modded +5 insightful?!?
And who modded it overrated? This is basic LAN management stuff. If you're doing it any other way, you're not doing it properly.
And Flamebait? If you don't know how to name, manage, and track workstations properly you shouldn't be doing it. No-one who has responsibility for naming workstations should need to ask Slashdot about this.
Having said that, reading below people who name workstations on department/section/any physical location, well... I'm astounded.
An organisation of any size needs to track the workstations that they've purchased/leased for replacement, support, and financial purposes. That means that every workstation should be on an asset register somewhere, with a unique number for each asset. It's easiest to track a device using a unique code instead of a serial number for example, because otherwise you need to track every serial number of any peripheral equipment used with the device. A proper asset register will be able to track what peripheral equipment (e.g. extra video card, sound card, specialised whatever) belongs with what workstation.
Whatever unique code is used in the asset register, use that as your workstation name. If you get to choose your own unique code for use in the asset register, how about this:
TYYYYMMnnnn
T = S for Server, W for workstation, C for Comms device.
YYYY = Year of purchase.
MM = Month of purchase.
nnnn = unique number for that month.
When a box moves, update the asset register.
