Win2k server, domain controller, no active directory?

nekromancerusnekromancerus New
edited September 2005 in Science & Tech
Some background info: We have a group of 25 or so laptops that we deploy for training. I want to centralize the administration of the laptops by sending a server along with them. I want the server to hold all the user accounts, act as DHCP server, etc... These laptops or server will not be connected to the internet but will be connected to a network when they reach their destination(s).

What I want to do is load Windows 2000 server (or 2003 server) and make it a domain controller. Only thing is, I don't want active directory. Is there any way to make either of these versions (2000 / 2003) a DC without AD?

If you need more information, just let me know and I'll see what I can do.

Thanks

Comments

  • ShortyShorty Manchester, UK Icrontian
    edited September 2005
    A server cannot be a domain controller without Active Directory or NT4 directory services. What is your reasoning for not wanting to use AD...? It's simple enough to create a local domain (test.local as an example).

    Possibly using a third party directory tool but I significantly doubt there is much that will centralize what you want to that scale. I have certainly not heard of any software that will emulate the functionality of a DC without AD.
  • nekromancerusnekromancerus New
    edited September 2005
    My main resoning beind not wanting to use AD is lack of experience with it and I was having problems getting it installed. That combined with my short suspense (end of next week)

    I am trying to create it named 'TRAINING.local' through the 'Configure Your Server' window but at the end of the 'Configuring Active Directory...' I get an error that says:

    "The operation failed with the following error:

    The network location cannot be reached. For information about network troubleshooting, see Windows Help."

    After searching the internet with such suggestions as 'plug it into a switch or hub and try again' I couldn't find a solution. That's when I was ready to give up on AD. Have any suggestions for that error?
  • ShortyShorty Manchester, UK Icrontian
    edited September 2005
    You just need to have a working local ethernet connection available. The server needs to have a static IP address assigned to it that it can use to enter into AD DNS (there are various reasons for this) :)

    Whatever ever you specify as domain (eg.. training.local).. make sure you enter that into the DNS suffix of the network card.

    The Configure your server wizard is very simple to use. Literally just follow the prompts. When it asks you about DNS, let it setup DNS for you and this will configure your forest & domain forward DNS zones and your DC will be online :)

    After that, setting on DHCP is very easy. Create a scope of addresses, set the DNS server settings to point to the static IP address of the DC, setup the DNS suffix the same as the domain, authorise the scope.. ya done :)
Sign In or Register to comment.