I generally like the naming scheme described by saigman. Any computer naming scheme should also incorporate a mechanism to obscure the purpose and location of the computer to people who are not involved with support while making computer identification easy for the support people. The scheme described by saigman begins to address this issue but then fails when it identifies the business department that uses the computer.
Generally I would say that any computer name that includes the name of the user or the department that uses the machine is a security problem. This is particularly true with M$ software. Anyone browsing the network can see the names of employees, which computer they use, and which computers are associated with each department. This makes identifying targets of malicious activity very easy.
In saigman's name scheme the first part of the name is a code for the office where the computer is located. That's good. The code is meaningful to IT support personnel but its meaning is not immediately clear to anyone else.
The second part of saigman's name scheme is a problem because it clearly identifies the department using the computer to anyone. It does this by using generally meaningful codes to identify each department. If the scheme was changed to have a numeric code for each department then the meaning would not be immediately clear to network neighborhood browsers.
Then, within each department the desktop computers could just be numbered. So, overall a desktop computer name could typically be something like 010202. Even though the long term employees might figure this naming scheme out it is still valuable since it obscures the pc function, owner, etc. from guest computer users or anyone else who has no business knowing the names of network resources and nodes.
This also applies to servers. I hate to see a server named 'payroll' or 'hr'. Talk about putting a target out in plain view!
So I believe that computer names should be meaningful to IT support personnel but should ALSO be meaningless to everyone else. This way even a computer guru with bad intent would spend a lot of time trying to find an appropriate target. It only makes sense to do whatever you can to slow the bad guys down. The longer it takes them to find a target the longer it will take for them to perform their mischief.
And it's an employee privacy issue. The fact that John Doe works at your company is private information. Employee names should not be made easy to harvest. Employee names should not be used for naming network resources. Also, I am totally against businesses that publish the email addresses of their employees unless those email addresses are just the names of departments or functions, such as support@xyz.com or sales@xyz.com. Making employee names available to a everyone on the network or, in the worst case, everyone on the Internet, is a violation of the employees' privacy.