Solved

Best Way to Bring NT4 Server into a Server 2003 Domain

Posted on 2008-06-23
3
364 Views
Last Modified: 2013-12-23
Environment:

NT4 Server at SP6. It hosts applications that we need to keep and that only run on NT4. Currently the domain controller.
Server 2003 Standard. Currently a standalone server.
10 workstations which are currently in the NT4 domain.

We want to promote the Server 2003 server to a domain controller and bring the NT4 box into the new domain. What's the best way to accomplish this? It has been a long time since I touched an NT4 box but I think that simply demoting the NT4 box to a standalone or member server, promoting the 2003 box to a domain controller and putting the NT4 box in the new domain will work.

We only have about 10 users so I don't really need to export anything from the NT4 domain. I am planning to input the user accounts manually - we need to standardize usernames/passwords anyway. I can also put the workstations in the new domain manually as there are not many of them.

Is this an acceptable way of accomplishing my goal? If not, please advise as to the preferred procedure.
0
Comment
Question by:gbrooke
  • 2
3 Comments
 
LVL 5

Accepted Solution

by:
HeinoSkov earned 500 total points
ID: 21852760
I would bring up a new server with NT4 and make it a BDC in the existing domain. Then promote it to PDC and then upgrade to Windows Server 2003. This would raise your domain to Windows Server 2003 and get all current users, groups and computer objects migrated with you

This is the safest path in my opinion. The reason for installing a new NT 4 BDC is that you get a clean install of your Domain controller.

Your current NT will then be a BDC in the Windows Server 2003 domain. You should however try getting 2 Windows Server 2003 Domain Controllers up and then remove the NT4 machine as domain controller. Can be easily done with UPromote http://utools.com/UPromote.asp, which I have used plenty of times - and without one single problem.
0
 
LVL 5

Expert Comment

by:HeinoSkov
ID: 21852767
Oh I misread your question.

Well you cant demote a NT4 domain  controller. Simply its not supported by Microsoft.

Use the utility I linked to above. Then your suggestion will work. Demote it to standalone and join the domain afterwards.
0
 

Author Closing Comment

by:gbrooke
ID: 31470047
Thanks for the help, HeinoSkov.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.   However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…
This article is in response to a question (http://www.experts-exchange.com/Networking/Network_Management/Network_Analysis/Q_28230497.html) here at Experts Exchange. The Original Poster (OP) requires a utility that will accept a list of IP addresses …
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Both in life and business – not all partnerships are created equal. As the demand for cloud services increases, so do the number of self-proclaimed cloud partners. Asking the right questions up front in the partnership, will enable both parties …

920 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now