Discussion Locked

NT4.0 Domains Into Windows 2000 Network

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a Windows 2000 domain (running in native mode using Active Directory) at our corporate headquarters and a number of NT 4.0 standalone PDCs at various branch offices. We're about to connect all our offices with corporate via frame relay. My question:

Do I have to upgrade the NT4.0 servers to Windows 2000 in order to have them participate in the network? If not, can someone point me to some documentation on how to handle this issue? I've gone through the Microsoft site and it appears that, since my predecessors brought the 2000 network up in native mode, the NT servers are incompatible.

11 replies

by frobo

Yes your'e right,

when you switch in to native mode, the DC-Emulator for NT-domains are switched off. The best way is to make an in place Upgrade of the NT-PDC's in the branch offices. But formerly it depends on the Network interaction you need between the central and the branch offices. Only for the central-Administration it may be usefull to take an 3dt party tool like NetIq Administrator, with this you can get the one Point of Administration, since it could synchronize User Accounts and other things.

Hope it helps

Frobo

PS: Look at www.netiq.com

by erikdr

Well, depends on how you want to define 'participate in'. They can indeed not be used as BDC's in the ADS domain, as this would require mixed mode. However any NT-W2K pair can still mutually logon by using the NET USE /U: switch and then the userid (qualified with domainname!) of the other directory. And there's also ftp, http, e-mail as ways of transferring info between the machines.
So what are your requirements, and are they really so heavy that the standalone servers need to become ADS domain members?

Hope thiz helpz,

- The Netherlandz

by artcabot

I like this answer and will probably give it a try once the network is live, but another answer hit closer to the mark. Thanks for the input, though.

by james.pounds

You have undertaken quite a complicated project. Did your predecessors leave you with a documented plan or strategy for your company's network or did they simply bring up a Win2K native mode server to impress the folks at HDQ. Sounds like you havea multidomain network that needs to be integrated/migrated into a Win2K network. You need to have a very good understanding of Active Directory design to plan how your corporate infrastructure and network topology will map into Win2K sites within the forest. Your first step must be to plan your forest and domain namespaces and then decide the approach to take to integrate the legacy domains. You may consider engaging a consulting firm to asess the situation and offer a plan. If you decide to tackle the problem yourself, there are products from third party vendors to assist with multidomain migrations to Win2K (ie. Fastlane, NetIQ, Bindview). Before you begin to upgrade those PDCs you should investigate the situation thoroughly and plan accordingly. Once a PDC is upgraded it may be more difficult to get it to participate in your network.

by artcabot

Even though the URL didn't work (Microsoft's moving stuff around, I guess), I get the point. I've also set a bookmark to this section of their site. Thanks for the assist!

by ttrinh

You said PDC, so they can not be stand alone, but must be controller of an existing domain. Eventually, you might want to upgrade to win2000, but right now you could resolve the problem quite simply by establish a trust relationship of your existingdomain to the head office domain. With trust established, users can still access resources on other domain (it has to be both way if users from both domains need to access the other domain)

Tuan

by artcabot

Thanks. An earlier respondent said the same thing. Guess it's the preferred way.

This discussion is closed to new replies.