Title: Naming conventions (quasi-OT)
I'm assuming with this every person has their own workstation? Or how would it be named for shared workstation..
 

Thank you and have a splendid day!

 

Kind Regards,

 

Freddy Hartono

Group Support Engineer

InternationalSOS Pte Ltd

mail: [EMAIL PROTECTED]

phone: (+65) 6330-9785

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Za Vue
Sent: Thursday, May 25, 2006 2:10 AM
To: [email protected]
Subject: Re: [ActiveDir] Naming conventions (quasi-OT)

All workstations are named according to building, room, and staff's initials.
Chemistry Building Room 5 and  user John Doe-> CB-005JD

-Z.V.

Brian Desmond wrote:

{I,A}Unit#{W, L, M}#########

I/A is specific to us, it differentiates subnet and function

Unit # is the location (four digit number)

W = Workstation

L = Laptop

M = Macintosh

######### = 9 digit asset tag

If I need to figure out a user’s PC name I just ask for the asset tag number and I can figure the rest out.

This works for 95K machines in 750 facilities

Thanks,
Brian Desmond

[EMAIL PROTECTED]

c - 312.731.3132

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Brian Cline
Sent: Wednesday, May 24, 2006 1:35 PM
To: [email protected]
Subject: [ActiveDir] Naming conventions (quasi-OT)

I'm curious to see how some of you (especially at the larger corporations) name your domain-joined computers. At my company we've got about 110 computers in roughly , and for the longest time they've been named after the logon name of the user who primarily operates the PC. (Not a fan of that method myself.)

However, when naming or renaming a PC there are cases (such as preparing a replacement PC for a user) where there's already one with the desired name. Our network admin has a horrible habit of putting random numbers at the end when he runs into this problem, rather than using ADUC to remove a ghost computer object (or renaming the existing one when a new one is being prepared for said user). Of course this constantly frustrates me as I can never correctly guess a user's PC name when trying to remote control it during a support call.

I've had several ideas in the past, the most favorable being naming them by location then department, then numbering them (for example, CHS-DISP-01 would represent the first dispatcher PC at our Charleston terminal), and automagically renaming the "My Computer" icon on the user's desktop at startup time to reflect the computer name. This way we'd never have to worry about renaming a computer when an employee is terminated, and when I've got a user on the phone I can simply ask them to read the computer name to me. But I was curious to see how you guys go about naming your PCs and how you deal with problems similar to this.

--
Brian A. Cline
Internet Applications Developer
G&P Trucking Company, Inc.
Direct:      803.936.8595
Toll Free:  800.922.1147 x8595

Reply via email to