[log in to unmask]" rel=File-List>
We do something similar, although, we need to keep track of which departments in our building "bought" the computer, so we have:
 
ACCELPCx
FABPCx
NUCFACx
GRADPCx
FACILPCx
POSTPCx
DSPCx
THEOPCx
 
and the number just keeps incrementing.   The only problem is, eventually, all computers end up getting into other groups due to user migration, and basic trickle-down phenomena.  But, we do always know where the machine started.
 
If you are in a Windows 2000 environment, you will have trouble if you have user ids and computer names the same in Active Directory (having a user login=brown and a computer name = brown will cause issues).
 
Katie Clark
Computer Support
National Superconducting Cyclotron Laboratory
Michigan State University
(517) 333-6338
-----Original Message-----
From: MSU Network Administrators Group [mailto:[log in to unmask]]On Behalf Of Javier Ornelas
Sent: Thursday, February 21, 2002 12:40 PM
To: [log in to unmask]
Subject: Re: Windows computer names

John,


What we do here in the HealthTeam, is use HT followed by a number (the first number was 1).  So we named it with our department name (abbreviated) then numbers.  We haven’t had any troubles in 5 years (knock on wood).

 

Javier

 

 

 

-----Original Message-----
From: John Valenti [mailto:[log in to unmask]]
Sent: Thursday, February 21, 2002 12:32 PM
To: [log in to unmask]
Subject: Windows computer names

 

I was just wondering if anybody has come up with a good scheme to name computers?

Naming them after the "owner" doesn't work out too well - that changes too often.
Naming them after the location also doesn't work too well - too much moving.

Any suggestions?
-jav


* John Valenti Systems Analyst, Labor & Industrial Relations *
* 408 S Kedzie Hall, Michigan State University, E. Lansing, MI 48824 *
* (517) 353-1807 fax (517) 355-7656 [log in to unmask] *