AD Naming
Ozgur Ozdemircili
Just a quick question. I am working on a project to creat multi
localtion, multi country AD schema. I have created the AD but I would
like to get your opinnions in naming the servers and computers in
different areas and companies
- The company that I am creating the AD for has mainly 5 other
companies inside it (I will bu using only 1 domain for all)
- All the companies has offices in different parts of the country.
-Mostly the companies, although namely different work in the same
offices.
- Sometimes one company has different offices inside the same CITY.
Ad domain : domain.com
Companies inside company.com : com1, com2, com3, com4, com5
I am thinking to use :
- host01.area.companyname.domain.com
OR
- host01.companyname.area.domain.com
And you are right there comes the problem! You cannot name the
computers as above because you will be needing different domains so
that the computer can be a part of companyname domain and area domain.
Or am I wrong?
What kind of names do you use for the computers and servers in your
practical lives?
Joe D
in that case ceate OU's for each company/location to break things up for
yourself
"Ozgur Ozdemircili" <ozdem...@gmail.com> wrote in message
news:74e25061-8d73-4513...@e6g2000prf.googlegroups.com...
Ace Fekay [MVP]
Ozgur Ozdemircili <ozdem...@gmail.com> typed:
You are altering the Schema too? May I ask why?
As for a naming convention, the FQDN method you gave an example for will be
problematic due to the way DNS registration works and SRV requirements. If I
may suggest, I've designed multiple location/international clients that have
one domain with location based OUs (as Joe D suggested) by following a
simple airport city code as a prefix with a letter signifying a desktop or
latop followed by firstinitiallastname. If the total name is more than 15, I
would just truncate it to 15. For example, if I had a desktop and I am in
the Philly region and the Philadelphia airport code is PHL, my workstation
computer name would be:
phl-dafekay
If the person would have a long name, such as John Reallylonglastname, it
would be:
phl-djreallylon
All names will be suffixed with the domain name, so the above two names
would be:
phl-dafekay.domain.local
phl-djreallylon.domain.local
Believe me, I remember someone trying to do something to the effect of what
you suggested many years ago and I told him he would get into much trouble.
You would have to alter the primary DNS suffix on each machine based on the
domain zone name based on your location. But you could not do this for
domain controllers due to the registration process. In some cases with this
method, apps that are directory enabled that require PTR records (such as
some UNIX apps), will fail. It;s just not worth the headache overhead in
making it (rather forcing it) to work. I wish I had saved that conversation;
I would have posted it for you.
--
Regards,
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations\
Ozgur Ozdemircili
wrote:
> Innews:74e25061-8d73-4513...@e6g2000prf.googlegroups.com,
> Ozgur Ozdemircili <ozdemirc...@gmail.com> typed:
Hi Ace,
Thanks for the exact answer I was looking for. I first started with
using company-000101 which is company-AreacodeDeptCodePersonno but had
doubts about it. Now it makes sense to see people are using the
schema.
Ozgur
Ace Fekay [MVP]
Ozgur Ozdemircili <ozdem...@gmail.com> typed:
>
> Hi Ace,
>
> Thanks for the exact answer I was looking for. I first started with
> using company-000101 which is company-AreacodeDeptCodePersonno but had
> doubts about it. Now it makes sense to see people are using the
> schema.
>
> Ozgur
Glad to hear you found it helpful.
Actually this isn't really based on the AD Schema per se, that is I didn't
customize anything in the AD Schema to make this work. It's just a naming
convention for computer names I derived that works for me.
Ace