Re: netbios name vs computer account name
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Sun, 10 Jun 2007 19:58:49 -0500
"Jeremy Schubert" <jscc-nospam@xxxxxxxxxxx> wrote in message
news:814FDE4F-E161-4E1F-9F59-993B6240C3D0@xxxxxxxxxxxxxxxx
Thank you all. So much vocabulary/terminology (domain tab description
properties vs aduc description property fields, CN versus account
name...).
Ace and Anthony, you're both right.
Ace:If it's serial numbers or whatnot that you are worried about, in the
computer description, you can put that in there. This way you can run a
'net view', see all the computer names and their descriptions. The
problem I think is more with the usefulness of a serial number as an
identifier.
Anthony: It wouldn't really help you go and look for it! Anthony
Just trying to work on the best naming scheme. We always start with the
plant code, a three digit number, 047 in my case. But then our downtown
people, our help desk, and our school techs are always debating what is
best. I have a program now called wsname from
http://mystuff.clarke.co.nz/MyStuff/Default.asp Through a script (batch
or vbs) it lets me easily rename a computer. The program can determin the
chassis type and serial number and a few other things. It also modifies
the description field in the system control panel but not the description
field in ADUC. So I have to have another script for that.
Lab techs of course want the physical location to find the machine.
Just resolve the name to an IP which will give the SUBNET and this
should get you the physical location of the computer to a close
approximation.
IF you wish, you can identify the EACH subnet with a REVERSE (PTR)
record that lets techs resolve the IP at the "zero offset" to the LOCATION,
e.g.,
192.168.20.0 --> Denver-Bldg2-Floor-3.yourDomain.com
192.168.32.0 --> Chicago-HQ-Basement.yourDomain.com
The help desk wants the serial number to enter a service call to IBM.
That might sound good but now everyone has to remember the Serial
Number (a useless number to users etc) in order to make the help desk's
job a little easier.
So just add this as some special zone for your help desk (as CNAMEs)
FredMachine.Serial.local --> H22340348.Serial.local
....or in some other database.
If the numbers can be easily found to CREATE the computer accounts
they can be easily found by the help desk when they need them.
Also you can build WMI queries for them so none of this needs to be
maintained.
With the 15 character limit for netbios, entering all of that is tricky.
I wouldn't even use the 15th character -- there are some odd cases where
the 15th is used by some programs.
My rule is 14 character names MAX with nothing but Alpha First and
Alphanumeric subsequent.
Especially if you want to make the number a bit easier to read for the
user by adding some hyphens.
Yes, and making every computer name obnoxiously meaningless for everyone
else in order to "help" the help desk is not that useful a strategy.
Give the Help Desk and Lab Techs some easy way to get the info they need,
and give the computers names that are meaningful to ordinary HUMAN BEINGS.
Part of the reason we have DNS -- so that humans can remember a meaningful
name and not have to remember IP addresses. <grin>
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
.
- References:
- netbios name vs computer account name
- From: Jeremy Schubert
- Re: netbios name vs computer account name
- From: Anthony
- Re: netbios name vs computer account name
- From: Jeremy Schubert
- netbios name vs computer account name
- Prev by Date: Re: Multiple Domains
- Next by Date: Re: Windows cannot verify >>>
- Previous by thread: Re: netbios name vs computer account name
- Next by thread: Re: netbios name vs computer account name
- Index(es):
Relevant Pages
|
