Discussion Locked

Best Practice For namig computers

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

Hello all. I have a quick simple question that I'm sure all of you seasoned veterans have a quick answer to. I'm still pretty fresh to the Admin field, and I want to know what are the best ways to name computers on the net work. Should I just do a simple: xxx1, xxx2, xxx3. Should I break it down by departments. Should I do it by the name of the users or the phone ext. What are some of the best, most efficient ways that you all have found to name computers.

Thank you for all of your help.

15 replies

by lost_one

If you use a Users name for the computer name you will have to change it each time you move the computer to a new user, same goes for phone ext. If you break it down by departments in the future you may need to change the computer name if it move to another department.

I use WS-xxx and for the servers I use a non-discriptive name. This way the computer name should never have to be change.

by z23micro

At just three simple network sites, I've had considerable time wasted because of worker changes and relocations. I'll never use names or extensions again.

by charliespencer

We use DTxxxx for desktops and LTxxxx for laptops. All we're interested in is assigning a unique name to the device so they can connect to our domain, and so we can track the machine in inventory. I've seen others that begin with an alpha character that indicates the hardware model.

Avoid using departments, usernames, phone numbers, or any other information that could change during the expected life of the machine. Avoid creating a complex system where each character indicates various hardware specs (RAM, drive size, monitor size, video card, etc.); these get too complicated. Track this info in a separate inventory appliation or spreadsheet.

by killianj

We use a variation on Palmetto's suggestion. We use DT/LT + asset tag number, assgining this to the machine name - in the computer desciption we will often indicate the assigned user's name, or kiosk location.

For servers, we use FS/PS/WS+tag number, to indicate File Server, Print Server, Web Server, etc... I got sick of trying to come up with really cute names or name themes - and it was always an issue when talking to management or executives. Functional is good - KISS

by loefvinc

We currently use asset tag prefixed with some location information for the machine name. It's better than most of the naming standards I have seen in the past. Each is unique and quickly matched to the machine type/model/make,etc.

by jdmercha

We have distributed responsibility here. Different people do the computer setups for different departments. And different departments use different naming conventions. We use deptname-serial#.

In our case the department will never change and the serial number provides a unique identifier.

by dmambo

Where I work, the depsrtments and different sites are responsible for submitting the asset requests and paying for PC's. So we use characters for site, dept, OS, and the sequential numbering. We also label each machine with the machine name so users have it handy when dealing with help requests.

If machines find their way to a different dept, they are renamed.

by aaronpctech

It makes me feel good that I can always count on the Tech Republic Crew to lend me a hand when Im in need. I think I will follow your suggestions as far as DTxxx and LTxxx. THe guy who was here before me named everthing by phone ext which is getting to be quite annoying.

Thank you all for all of your suggestions. No doubt I will be asking more questions :)

by d50041

We use SYS for workstations, FS for file servers and DC for domain controllers. All followed with a number, this could be based on how many systems (nodes) you might track. But whichever you choose, do use KISS. File servers could use org names , such as FSacctg for an accounting file server, or DCMain for a domain controller in the Main St. location. More than one? then FSacdctg1 and FSacctg2. Mkae it easy to remember and obvious when using admin tools.

by jonathan

I'm happy to see at least one reply referring to the function or use of the device. Yes, a workstation is a workstation, and you can name them all AnnoyingUser01-99, but it is helpful to include the dept. such as Market01, Manufac19, etc. Servers are much easier to deal with if the names describe functional use, and location is an excellent idea else, e.g. ExchangeBldg2, Domain1Corp, FileServerSpringSt, etc.

by david

The use of asset numbers, etc is unwise in an educational K-12 setting, as in our environment 'assets' can be moved around. Therefore, if your CMDB isn't updated correctly you may not be able to locate it when a user requests service. We use a functional naming convention of Campus, School, Room/Lab, PC number, eg: Sydney Campus, Middle School, Lab A1, PC 3 would be SMSA0103. All devices have an 8 character naming convention. Hope this helps.

by john.funk

We happen to use Dell computers, and each of them comes w/ a 7 digit "service tag". We name each of our computers at this location "SC-xxxxxxx". We do this so that, if we ever need to service a PC, it is very easy to find out what its service tag is (rather than physically looking on the back or the side of the PC). In a normal office environment, it's not a big deal. But in a warehouse environment, where some PCs are hard to get to, it is very helpful to do it that way. I also agree w/ a prior post about putting labels on the PCs. We put the computer name on the monitor, and on the front of the PC. (This also helps if a user has problems, and you need to remotely control their machine. You can ask them what their computer name is, and it is right there on the monitor for them.)

Also, it helps to keep a cooresponding spreadsheet, listing each PC, its name, and its location. (Well, we put a WHOLE LOT of other information on it, but I think you get the idea.)

Our server naming structure is different, but sounds like you mainly need help w/ the standard office PCs.

Hope this info helps.

by claudio.vilchis

I work for a college and the way we chose to name our computers is to use the inventory tag number plus a location code.
we use the name of the building plus the office number plust the tag number this comes to 15 characters.
The reason we chose this was that when dealing with about a thousand plus computers it is easier to find computers on the network.

by omoore

I work in a college and can not use the asses tags because the pcs are moved around too often.
What I may do is use a combo of Asset tag and Building name + plus room.
There for I can identify a pc in need, instead of going place to place when there is a problem.

by granholmk

When I started to the government agency we had full manual systems for IP and names. All computers were named for the user, very cumbersome.

I developed a system the used a short 3 or 4 letter abv. for the department followed by an 4 digit number increasing by 1 at a time.

Servers are prefix named FS for Novell, NT for Windows, LNX for Linux, and so on. The the server name contains an abv. for the city of its location and a building abv. Special servers my have it purpose labeled like NT-WEBAPPS for a generic web applications box, and with a number for which server it may be.

This discussion is closed to new replies.