Do I have to deploy Active Directory on Windows Server 2003 ?

A1: You don't absolutely have to deploy Active Directory. You can leave your Windows servers in a workgroup; however deploying Active Directory centralizes your security (users, groups, etc) and benefits in numerous other ways. You can deploy Active Directory on Windows 2000 Server or Windows Server 2003.

A2: Novell used to make a tool called NDS for NT, I haven't read much about it for a long time but I heard they would support Active Directory. Microsoft has a couple solutions to co-exist with NDS such as 'Services for NetWare' however I don't think they are meant to be a long term solution. If you truly want to leverage both directories in an integrated fashion I would suggest looking into a 'Identity Management' solution.

A3: You can use a alternative DNS other than Microsoft's. (Note: I would recommend using MS DNS if possible)

The requirements are as follows:

Must support RFCs 2052, 2163, Dynamic DNS and Service Resource Records
Must be compatible with Bind 8.1.2 or later

Hope this helps!

Best Regards,

J.R. Brown
iAdmin Mobile - Mobile Network Systems Administration
http://www.iAdminMobile.com

Being a Novell Shop you are using NDS for your user and group management. If this is working to your satifaction then why is the Windows 2003 server there? Introducing Active Directory into your enviroment gives you two network accounts and passwords per user and the sync issue that goes with it. If there are any features you want to use on the Windows 2003 server then you will need Active Directory. If it is just a larger workgroup PC to store files you don't need AD. You could setup the server with AD skip the users accounts load the NDS for NT and manage it like that. It all comes down why is it there?

You suggested NDS for NT .NDS for NT does not support W2K and above.

The mechanism between NDS for NT and EDIR/DIRXML (Nsure) are two very different Novell products.

NDS for NT(or Corporate NDS) replaces the SAM.DLL on the NT 4 box, where as DirXML is a shim between the AD on the W2K/3 boxes and EDIR on the NW box that synchronizes data between the two(publish or subscriber depending upon how things are set up).

I've done a few in my career (all though Novell is not very healthy out here on the west coast).What a shame, great products, but M$ is what sells.

West Mifflin, eh? I am from Brownsville originally, but IT back in SW PA is so bad I had to move back to S.F.

Go Steelers!

If you absolutely need Windows 2003 go with the Standard server product and stay away from Windows 2003 small business server as it requires Active Directory and to be setup as the only domain controller on the network (single tree in a single forest - not much of a forest with only 1 tree though), if you don't promote it to dc and setup up active directory, it's a violation of the the M$ eula and the server shuts itself down after the first 7 days of operation and everyday afterwards. Windows 2003 server in my opinion is just a Windows 2000 product with few upgrades and a WinXP eye candy face lift, go with Windows 2000 Server if you can, I've used it for years and for all intents & purposes it's bullet proof. Just my 0.02 cents.

(1) You don't have to have AD to use W2K03 but it is useful for centralising admin & security & all the other reasons people use domain models rather than workgroups. I don't think its an option to not use a domain but if you're happy to use a NT4 Domina Controller (or possibly a Samba DC) you could avoid it. Totally depends on your situation.

(2) No, Microsoft would never allow that BUT Novell do allow NDS AKA E-Directory to be layered on top of Active Directory & Linux & UNIX etc. It would be worth reviewing that as an option.

(3) DNS can be run on any O/S so long as it is compliant with the latest BIND versions. Obviously it never gets covered by MS training courses but if your comfortable with DNS it can be done.

Hope this helps