Discussion Locked

2000 pro in NT4 domain (good idea?)

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

Is it a good idea to deploy windows2000 pro as standard, in an NT4 domain?
I've heard mixed opinions about this, is there such a thing as a definitive answer?
I know that several features will be unavailable that require AD, and there are problemswith roaming profiles.

What I really want to know is if it is sensible!

We WONT have 2000 servers for a good while yet.
I would be most grateful for your views!

3 replies

by mhubbard

I'm in a company with 10,000+ nodes. We don't have Win2K server as of yet (but have plans to migrate sometime next year). We are currently rolling out Win2k pro to ALL our computers, everywhere.
We are doing it for a couple of reasons:
1. To stabilize our environment with one supported OS.
2. To reduce support costs because of #1.
3. To finally have one "build" (an image of special dept. apps for various deptartments).
4. Once the clients are rolled out, we can easily migrate to the Win2k Servers environment and just "push" out (via a software deployment tool) the changes necessary for the clients.

Either way... good luck!

by keeny

thanks alot.

I've researched it, i just wanted to hear what people were doing in the real world!

This discussion is closed to new replies.