Re: Client computer naming conventions

Tech-Archive recommends: Fix windows errors by optimizing your registry

I use the Description Field for the location b/c as SuperGumby said it
doesn't cause a problem when changing it. This helps with the remote access
since you can put a better description where the pc is located. Sometimes I
even put the functional persons role and location in description.
PC Names I stick to names that don't change i.e. WS01, LT01, etc.....



"Mike" <none> wrote in message news:eMYY9samIHA.5280@xxxxxxxxxxxxxxxxxxxxxxx
Hi All,

I'm looking for feedback or opinions regarding the importance(or lack there of) when it comes to naming client computers. I've thought about naming each client computer based off of the department followed by a sequencial number like "accounting_100", "executive_105" for example. Also, what about separating users and groups into separate OU's? I know that the user accounts must reside in "SBSUsers" OU. Keep in mind that I haven't joined any computers to the domain yet.

Please share what you have done in past or any user/computer best practices' organization in AD. I'd really appreciate any feed back.

We are running SBS 2003 R2, single nic with exchange running. Most of our CAL's are user based mixed with one 5 license device CAL.

Thanks so much in advance everyone.
-mike


.

Relevant Pages

  • Re: Client computer naming conventions
    ... I'm looking for feedback or opinions regarding the importancewhen it comes to naming client computers. ... what about separating users and groups into separate OU's? ... We are running SBS 2003 R2, ...
    (microsoft.public.windows.server.sbs)
  • Client computer naming conventions
    ... of) when it comes to naming client computers. ... separating users and groups into separate OU's? ... We are running SBS 2003 R2, ...
    (microsoft.public.windows.server.sbs)