Software

Ask something
Discussion Locked

Generic Naming PC's;Computer Network ID

0 helpful
2 replies

by jbullen

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are currently naming our 300 PC's under our control (mixture of Win2k, Win NT, and Win 98) by the primary user of the machines name. We are now having the issue of employee turnover and constantly having to rename the PC for the new user and create a lot of paperwork hassle to track usage, licenses, etc. As such we are now considering the use of generic names, such as CustomerService1, CustonerService2, etc.

Has anyone else tackled this type of issue before? What types of problems (if any) did you encounter by taking this approach? Is it better of to use a name that indicates a function (ie customerservice1) or a totally generic naming system (ie PC1)?

2 replies

by generalist

A mixed approach might work.

If you're dealing with 'big name' workers like the CFO, it might be politically astute to use the user name approach. A minor concession there might have big payoffs later.

At the lower level, generic names like CustServ001, CustServ002, Sales001, etc. works. Just keep them short and remember that Sales100 will come after Sales1 and before Sales2. (That is a good reason to use place holder numbers in your names.)

What you do at the middle level may depend upon logistics and politics. If there is lots of turnover, CustServMgr would work. If the job is relatively static, the user name would work. It could even become a perk.

by gene_grimes

Try using the asset tag number or something similar to that. That way it does not matter who sits at that pc as long as the pc stays put.

This discussion is closed to new replies.