Setting up a Windows 2000 Domain

I have to 2 computers that I want to make DC's. Both are running Windows 2000 Server. I want them both to serve as DC's, for replication. I have ~10 workstations running XP, and want them to authenticate to the domain. I do not want to implement Active Directory, but I want to implement Group Policy for OS and application updates. What are your recommendations? Thanks

 

In order to create DC's must implement AD. Also to use Group Policy must use AD. Why don't you want to use AD?

 

I cannot implement AD because AD is already installed within one of the organizations at my company. The organization I work for does not want to join the main Domain that has AD installed. They want me to have my own DC's that replicate eachother, and be able to authenticate to it. If AD is necessary for group policy, then I cannot implement group policy. Also AD is necessary for a domain, so I don't think I can accomplish what they want..right?

 

you can create your own AD independently of theirs, depending on if you may need to merge them later you need to consider forests, trees etc

Basically you need to know about their internal DNS structure in order that you can make decisions on yours

2003 has a lot more flexibility in this respect than 2000 did

 

You actually have many options to make this work, I think you really need to sit down with the Domain Admin for "they ", and discuss how the networks are designed (are you and "they" in the same building? connected via LAN? WAN? are they using a registered/public domain name? and exactly what they want to accomplish. A domain, and especially in an existing domain environment requires designing and planning.

 

We are not in the same building. Look at it this way.. Consider the organization named, ex. "ABC ", beneathe the org we have different groups spread out in different bldgs. All these groups, ex. "A ", "B ", "C ", "D ", and so on connect to the main domain "ABC ", which has active directory. The groups "A ", "B ", "C ", "D ", are OU's under the "ABC" domain. Say I am group "E ", my boss does not want to connect to "ABC" domain, he wants us to be our own domain because of security/vulerablility issues. I could install AD on my domain and use "ABC" DNS server, but it does not allow dynamic updates, which means I would have to install DNS locally when installing AD on my DC. What would be the best thing to do??

 

DNS is a fundamental part of AD, you cannot install AD without installing DNS first (recommended), or during AD installation.
1: I'm assuming you have your own WAN/INTERNET connection Y/N?
2: Do you need to access any resources in "ABC" domain? files, applications, printers, etc?
3: Do you have a "registered domain name" for your group?

Sorry didn't get back sooner, been cramming for Sec + Exam, took it yesterday and PASSED !!!!!!!! Been hoping someone else with more experience would chime in and maybe get you going in the right direction quicker..............Newt????

 

TJ-IT - I stayed out of it because you seemed to be doing fine.

rleyba - the question of ABC resources you might need is important. If there are not any, you could just set up your AD domain as if ABC didn't exist. They could even share wiring but ignore each other if you set things up carefully.

We need quite a bit more detail to offer any sensible help though.

 

Thanks Newt, that means alot. Still trying to get my confidence level up. Knew we needed much more info, but was having trouble trying to figure out which questions took priority. Started out with about 50 questions, when i previewed my post, "I" was confused, LOL. Glad to know you are "watching" out for me . Here to learn, as well as help when I can. This place is GREAT, thanks to all who keep it going.

rleyba, keep the questions coming, I, as well as others will try and guide you in the right direction, WE are all learning. To me that's what keeps the FUN in computing

 

abc's domain not allowing dynamic updates is not necessarily a problem - however you need to know if this is what you want

Setting your domain and DNS up completely seperately will work fine but, depending on the DNS structure, you may have huge problems if you want to integrate them later

As Newt said, lots more info required