Slashdot Mirror

← Back to Stories (view on slashdot.org)

Suitable Naming Conventions For Workstations?

Posted by kdawson on from the tune's-my-own-invention dept.

spectre_240sx writes "We've discussed server naming a fair amount in the past, but I haven't seen much about workstations. Where I currently work, we embed a lot of information in our workstation names: site, warranty end date, machine type, etc. I'm of the opinion that this is too much information to overload in the machine name when it can more suitably be stored in the computer description. I'd love to hear how others are naming their workstations and some pros and cons for different naming schemes. Should computers be logically tied to the person that they're currently assigned to, or does that just cause unnecessary work when a machine changes hands? Do the management tools in use make a difference in how workstations are named?"

3 of 688 comments (clear)

  1. Re:Like an ID for a database record by Kamokazi · · Score: 5, Informative

    Asset tags systems work well for this. It's what we use. Easy for RA requests too..just ask the user to read their asset tag number (if you don't have it memorized because it's the 5,689th time this dumbfuck has called you asking how to move a file from one folder to another.) and you can punch it in and connect.

    --
    As our way of thanking you for your positive contributions to Slashdot, you are eligible to disable Slashdot 2.0.
  2. Re:don't name by person just makes it harder to do by digitalunity · · Score: 4, Informative

    Place I worked at previously had an even much simpler method: the hostname is the cubicle number followed by the image build number.

    It made a lot of physical services such as repairs and upgrades much faster and really, there is just too much information about a user and machine to even consider using the hostname to store it all.

    --
    You can't legislate goodness. Let each to his own destiny, by will of his freely made choices.
  3. Re:don't name by person just makes it harder to do by SignOfZeta · · Score: 4, Informative

    My old university/job used a three letter department code, and then the last six digits of the asset tag. You'd get systems like ITS-26301 and MTH-31415.

    This is pretty solid, especially because:

    1. Machines rarely if ever change departments. Even the laptops. Entire departments can change buildings without issue; sociology moved across campus, and we were like, "Wait, when did you guys get the fuck over here?"
    2. The first four digits of any asset tag (in the foreseeable future) are fixed, so just prefix it with 7802 and look it up in the online database (or Mac OS X dashboard widget made by yours truly, for the two other people in IT who have and use Macs) for more information than one cares to know.

    Your mileage may vary.