Suitable Naming Conventions For Workstations? 688
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?"
Worst ask slashdot ever (Score:3, Insightful)
And that's saying something.
Honestly, can you even think of a stupider question? How is this even an issue? Just name each machine with an ID and put the information in a spreadsheet somewhere. It's not a complicated problem.
A computer name is not a database (Score:5, Insightful)
Re:Easy... (Score:5, Insightful)
I laughed out loud. Using the IP address as the hostname? Genius.
Re:Worst ask slashdot ever (Score:3, Insightful)
Simply name it after the the DATA DROP ID. You can locate the machine
and when you change PC's, just change THAT machine name to correspond
with the drop location.
Yeah, put it in a 'spreadsheet'. Most 'spreadsheets' are merely
searchable lists... go figure, I guess people forget what a
spreadsheet IS.
Re:Worst ask slashdot ever (Score:5, Insightful)
Renaming PCs = BAD. You get away with it up to a certain size, but once you start implementing apps like a job tracking system, software licensing tracking, etc it just bites you in the arse... HARD.
Re:Like an ID for a database record (Score:3, Insightful)
Exactly. We have an 'asset tag' - a number written on the case with a sharpie. (Works perfectly fine for us!) The computer's name is just "PC" followed by the (zero padded to three digits) computer number. Thus, I'm on PC079.
(With us, when a person changes department or office, their computer follows them. Thus there's no sane reason for us to encode the office or department name into the computer's name.)
Re:Like an ID for a database record (Score:3, Insightful)
Use asset tags. They are unique (at least should be) all other data are stored in database else where, sub-records keeping rest of the information like software loaded, key#, ...
*IF* BIG IF,you have more than 1 company under the same roof, add a simple company id, but really not needed, that is really a column in database.
Watch out for asset tags greater than 8 or 10 characters, depending. Can be problem with secondary machines and naming issues, like workstation ids IBM equipment (10 char unique / 8 char local machine plus 2 auto-assigned characters to insure uniqueness). This way tracking a machine "foot print" on a foreign location machine will be easier, instead of random assigned ids.
Changing hands shouldn't be a problem (Score:5, Insightful)
The machine should be reimaged when it changes hands, so resetting the name will add about 5 seconds to the setup process. Not a big deal.
Re:Worst ask slashdot ever (Score:5, Insightful)
If you rename the PCs you're forever trying to keep up - or dealing with false information, which is worse than no information...
Re:don't name by person just makes it harder to do (Score:4, Insightful)
In the tightest companies I have worked for, they name workstations and servers with meaningless random generated alphanumeric sequences.
I guess they consider it more secure, making it harder to figure out the network topology. Also, since the names are meaningless, there is never a need to rename the machine really, unless they would want to confuse even more want to be hackers.
Re:I think I'm in the minority here... (Score:3, Insightful)
Re:service tag (Score:2, Insightful)
Pre-fixing or post-fixing the name with something significant to it's location (such as department number) can be a lazy-man's replacement for a spreadsheet, but may require a rename when the computer's re-purposed.
Store the owner's name in the database (if one exists) if it's valid to the location. Even if the person leaves or gets fired, half of the department may know his name better than his job description.
Re:Changing hands shouldn't be a problem (Score:5, Insightful)
Whatever naming scheme you choose, ensure that you can leave the names alone once they're assigned. Renaming PCs is bad and creates additional workload for no good reason.
One Word (Score:3, Insightful)
One word: TinyURL.
Re:don't name by person just makes it harder to do (Score:5, Insightful)
That's a lot of work when someone changes a cubicle.
Re:Worst ask slashdot ever (Score:3, Insightful)
Dumb idea.
If you can't find the machine unless IT tells YOU what drop its on, I suggest you find a new line of work. Besides, wifi in the work place makes this a limited option. Machines move from desk to desk without the involvement of IT. Happens every day.
Machine name should be unique and fixed for the life of the machine in the corporate world.
Some things are tied to machine name, (some software licenses, etc) and windows objects when you put two machines with the same name on the same network. So EITHER when you set up the new one, OR when you re-purpose the old one you run the risk of knocking someone off the net in the middle of something important.
Just use your corporate property tag number. (You do have one of those don't you?) This can be tracked thru your property system to purchase documents, departments, and dates.
In the absence of a property system use its mac address. These things hardly ever change anymore, as the days of failing nics is pretty much past, and it makes the machine traceable on your network (if you REALLY can't find it any other way).
Resist the urge for cutsie or personal names, or names that reflect function or even location. These leads to trouble when people leave, or machines move.
Re:Worst ask slashdot ever (Score:3, 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.
Re:Worst ask slashdot ever (Score:3, Insightful)
This, as many above, seems to suggest that the names are arbitrary identifiers only used for administrative purposes. But is some real situations, all those computers are UNIX boxes, and users need to log in into specific ones (yes, even workstations), and remember which one is which. A 20 letter+digit white noise name is very unlikely to be remembered properly.
Re:Worst ask slashdot ever (Score:4, Insightful)
What do you do when a machine is relocated? (Score:3, Insightful)
You have to rename it.
Which is silly.
As with people, machines should have a unique name, all the rest of the information about the machine should be in a database of some kind (a list in a text file would do).
Then when you move the machine, assuming that your DHCP, DNS and WIntel servers are up to scratch, yo have to do precious little but relocate the machine (and update your database).
With your naming scheme you have to rename the machine in addition to updating any database you may have.
Re:Worst ask slashdot ever (Score:3, Insightful)
Exactly, this is why we name our PCs after the DELL service tag, if we are in doubt we can just call up DELL, they know everything about the machine that matters.
Identifiers are not descriptions (Score:3, Insightful)
It is a common mistake, but do not attempt to insert descriptions into identifiers. You wouldn't name your child "Dribble-gums-nursery-2" and expect then to be still comfortable about it when they reach their teens. But call then something meaningless like "Kevin" and there's no problem. Computers are no different.
If you create an identifier that attempts to describe the computer, rather than just give it a unique name, you can be sure that by the time it comes to decommissioning it the identifier will be misleading. Things will have changed. It will have a different location, a different OS, a different owner, or a different spec.
Re:Our old sys admin (Score:2, Insightful)
Come on guys, it's possible to understand a joke and then make a serious comment about some aspect of it.
Re:service tag (Score:2, Insightful)
What's hard about "hostname"? (Score:4, Insightful)
because if you're going to rename a server, you might as well rebuild it
What, "hostname $new_name" is too hard to type? I mean, you don't hardcode the machine name in application config files and rc scripts, do you?
Do you?
Re:Changing hands shouldn't be a problem (Score:3, Insightful)