|
Home > Archive > 70-217 > October 2001 > Setup A.D
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Hello !
Can anyone please teach me how to setup a domain controller? I need to setup a server that with 25workstations. At the win2000server, when I first need to install A.D, it ask me whats my domain name, let see my company is ABC, so should I just put ABC or ABC.com as the domain name??? Also when it ask me for the DNS, what should I put? Since my company havent get the T1 install yet and I want to set everythings up first and once the line is on, plug it in and ready to go u know ...... At the DNS field what should I put???? Also If I need to setup this domain controller, is that I need to setup DHCP as well? If so, can u teach me how??????? I know I need to setup the users group in the A.D for letting those 25workstations to logon to. 1 last question, is it a server MUST have DNS, DHCP and A.D installed ??? How about just A.D ????
THANK YOU VERY MUCH FOR YOU GUYS!
TAKE GOOD CARE | |
| Craiglew 2001-10-30, 5:40 pm |
| First off, if your company plans to have an internet presence, you're gonna have to make sure your Active Directory root adheres to the internet standards - and register your name with ICANN. I'm sure that "ABC.com" is taken so your gonna have to either have "ABCcom.com"(for example) for the external users and whatever you want for your internal network. (ABC.com, ABCcom.com - just examples) If you use the same name for your forest root as on the internet: it will be easier for users to remember, you will need to configure a firewall, and you will have to ensure that the appropriate records are on the internal and external DNS servers. I would use different names for security because of the distinct differnce in public and private resources. Your internal resources will be inaccessible from the internet by using tne external domain name. Also, no need to replicate between the two servers......So, name your company ABC, call you company ABC.com, if you want to, for DNS and Active Directory internally. Also, Active Directory can't work without DNS. Active Directory uses the DNS strucure and naming stratagy. Before Windows 2000 it was all about WINS. Now, with Windows 2000 and Active Directory, it's all about DNS and only using WINS for backwards capatability and applications that rely on WINS. Also, DHCP can be nice, even though you only have 25 users. That way you won't run the risk of screwing up or creating typos while manually configuring and inputing the IP addresses of your clients. When you create the 25 user accounts in active directory, you can manually create and assign IP addresses or use DHCP...your call. (chanting, "DHCP! DHCP! DHCP! DHCP!") Man, I'm a dork!
If anyone has a problem with anything I said, let me know. This is how I understand everything. I passed the Implementing Directory Services test last Thursday with an 860, so I feel that I know what I'm talking about. Thanks! I'm going to take (070-219) "Designing Directory Services" in a couple of days. Then, I'll have 5 down and 2 to go! Peace-Out! Biatch! |
|
|
|
|