Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We run a Windows NT workstation connected to special manufacturing equipment, that everyone is deathly afraid to touch. It has custom software and special cards inside of the machine, making a rebuild impossible. The problem is, we are migrating to an AD domain from an NT domain, and this workstation stills needs access to storage on the network (AD computers). How should I go about doing this, after we get rid of our NT Domain controller? Upgrading to 2000 is not an option (so says management).

I know, I know, if it dies we are in trouble. But that's managements choice, we just need to get rid of this NT domain.

share|improve this question
OT: You should definitely use Acronis or some other imaging software to get an image of that NT4 server BEFORE it dies. We have some of the same legacy issues in my environment, and you CANNOT assume you will be able to restore this kind of legacy system from a regular backup. You should also review and TEST the procedures for restoring NT4 to "unlike hardware" as it is a rather painful procedure. FYI. – Ryan Fisher Apr 1 '10 at 17:55
up vote 2 down vote accepted

Windows NT can work perfectly fine as a member computer in an Active Directory domain.

share|improve this answer
Yes, the NT4 workstation will talk to AD via whichever domain controller holds the PDC Emulator fsmo role. – squillman Oct 1 '09 at 16:49
I'd plan on arranging for good NetBIOS name resolution. If your DC holding the PDC emulator token is off-subnet from the NT 4 machine you may need to use WINS. – Evan Anderson Oct 1 '09 at 16:54
He probably already has WINS in place, if this is the case; good point, anyway. – Massimo Oct 1 '09 at 17:23

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.