Having a Naming Convention in place makes administration of Server's, PC's and Laptops more efficient and helps reduce issues in certain areas.
Here's an example of a poor naming convention:-
A new Laptop is purchased that will be used by a remote user in Italy. It is named 'HP-PC'. A few weeks later another laptop is purchased and this is also named 'HP-PC' for use by an employee in Spain. A few months down the line both users move to work from Head Office in France but can't work out why shared documents won't open or why they keep droping off the network. If they'd had unique names this wouldn't occur. It's like having two office phones with the same extension number.
Whilst it might seem trivial it is a basic piece in the jigsaw that is simple to implement if thought out from the start.
Ideas/Options for Naming Conventions
There are many different naming conventions and each has it's own Pros and Cons. What might be suitable for one company may not be suitable for another.
1. Use the serial number or random set of characters (Q12EFR59 etc)
2. Persons Name (David-Laptop, Paula-PC)
3. Sequential naming (e.g. Laptop1, Laptop2, PC1, PC2)
4. Themes (Colours, Animals, Places, Actors, Products....)
5. Order Reference and Date (PO768-19May14)
1. Names must be unique
2. Take into account size of company (e.g. number of users, laptops, PC's etc)
3. Staff turnover
4. Being easy to remember helps IT Admin. The name of a PC doesn't usual affect the user