I understand that the below scenario is a bit odd. Why it was done this way, I have no idea; but it’s my job to correct it, and I’d like some ideas on how to do so!
I have an NT 4.0 domain with about 60 users on it (lets call it ABC domain).
I also have Windows Server 2000 running Exchange 2000. The 2000 Server is NOT a part of the ABC domain, but it is the DC for it’s own ABCEXCHANGE domain (previous vendor apparently pre-set up the server outside of the ABC domain and just brought the box in and plugged it into the network)
Users log into ABC with user/pass and that info is somehow transparently passed on to Active Directory on ABCEXCHANGE. Creating/modifying users has to be done on BOTH domains, or login errors occur.
I have one particular Windows Server 2003 box that is a member server (no AD) on the ABC domain. I would like to use this box as an Exchange 2003 Server (and possibly as login server as well), but I’m not sure if installing AD on an NT 4.0 domain is even possible.
Can I install AD on a 2003 server already in the NT 4.0 domain and have it assume the login functions for the ABC domain, and then remove the NT 4.0 server? Will I have to go to each workstation and rejoin it to the new AD domain (assuming the first question is ‘yes’)?
Thank you for any input.
