We use room-os-id. So ours is ict1-xp01 or lib1-xp03. Admin machines are done by the function, ie bursar, finance, attendance, reception. Hope that helps.

We use room-os-id. So ours is ict1-xp01 or lib1-xp03. Admin machines are done by the function, ie bursar, finance, attendance, reception. Hope that helps.
I've always been interested in how others name their workstations and servers... Good thread choice
The way we do it is rather simple, kind of like how Gibbo does it, its "Room Number"-"Incremental Number" for student workstations.
For staff machines we tend to go "Room Number"-"Users Name" as staff usually have their own fixed work areas/desks.
For servers we use "OC"-"Server Name". For example OC-STAFFMAIL1 or T200-01.
The idea behind the use of "-" in the machines name is so VB scripts can quickly identify the location of a workstation by looking at what comes before the "-". In the past this has been extremely useful for login and startup scripts where something can't be done using Group Policy![]()
Last edited by Zimmer; 10th December 2008 at 12:39 AM.
We have two seperate campus's so we need a pretty organised AD.
Every room has its own OU, so within those OUs, the station name would be, for example:
"A100-01" and "B100-01"
A= Lower Campus
B= Upper Campus
100= Room Number
01 = incremental
Laptops are usually just the make and model with an increment.
ie.
"ERGO-MXL-05"
We use Domain-Room-Machine Number (starting from the door going clockwise) for PC's and Domain-LT-Description for Laptops.
Reason for using this is that printers are set via the logon script based on which room the machines are in or for laptops it gives them a variety to choose from.
Here's how we do it.
Workstations: room-number (room 1.15 pc 1 = 115-01).
Laptops: we use the serial number and record who has what in active directory.
Servers: depends if it's a domain controller or not (dc-01-<shortened schoolname> or sv-01<shortened schoolname>).
Pretty much the std RM conventions here:
Workstations
Sitecode-WK-RoomNumber-MachineNumber
(eg XXX-WK-R48-04 machine 4 in room 48)
Notebooks/Laptops
Sitecode-NB-DepartmentBatch-MachineNumber
(eg XXX-NB-SC3-04 notebook 4 in batch 3 belonging to science)
Staff Notebooks
Sitecode-NB-StaffInitials-MachineNumber
Machines grouped in AD according to loacation and laptops grouped according to room/department - make/model (eg StaffLaptops/nx7300 for hp nx7300 allocated to staff)

We use [site code-department-number] e.g. mil-ks2-1, mil-ks2-2 etc
As we use Spiceworks for our inventory, and there is a field for asset numbers, we record those there.
If the machine is moved and renamed, the history and asset number is still present.
I forgot about teacher laptops- they are named in the following way
ltft-user intials
hope this helps in what you where looking for.
I like this idea.
Anyway ours is the usual room name and pc 3 digit number or description
IT1Teacher
IT2005
TE2020
SCI013
STWK004
And we also use a script that takes the first 3 characters of the name to determine which network printer is installed. That way each department can only print to printers that it owns and there is no (well less anyway) moaning about who buys the cartridges
We use (legacy LEA naming):
TAW (Telford and Wrekin) 900 (Zone 900 Nodal site - us) W - workstation/ Z - Server / V - Virtual/ P - Printer *next number in sequence*
So, for instance, Our 4250dtn is TAW900P022, Print server is TAW900Z002 (soon to be a V), Teacher workstation is TAW900W190 etc
Not ideal, but...it may be different when we go to the new building.
just room-number for us
if you use some kind of delimiter between sections you can split up your string in batch.
like for printer assignments we do if %computername:~0,3% == 6R-

I've used this before on split site - Site-Room-PCno EG JS-ICT1-01 for Junior Site - ICT Room 1 - PC 1
Also used Room|yearofimage|PCno EG A1-2008-01
Laptops Ive used two schemes - LFT-yearoflaptop-laptopno EG LFT-2004-01 and then kept records seperate of who that belongs with or LFT-staffinitials EG LFT-HKL
All those work well, I feel that the PC name should always be fairly helpful for remote requests hence the fact they have the room name in them.
There are currently 1 users browsing this thread. (0 members and 1 guests)