General discussion

Locked

No NT Domain: Go NT or W2K?

By Bad_karma ·
My company currently has no NT Domain infrastructure (maybe I lied but it's as good as none). I am trying to push going straight to W2K based on its ease of administration and stability. Unfortunately, management is understandably wary of first iterations of MS products. All the articles that I have been able to find, discuss the value of upgrading an existing NT domain to W2K AD, but in my case, my company doesn't really have one. The way I see it, my company has a chance to dispense with the costs of upgrading licenses and all the headaches that come with upgrading NT to W2K and go straight to W2K. In my position, what would you say to management?

This conversation is currently closed to new comments.

10 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

No NT Domain: Go NT or W2K?

by aekland In reply to No NT Domain: Go NT or W2 ...

I think you are correct, going with 2k would eliminate the hassle of upgrading and fixing any mistakes in NT. I would try to show them the costs, both of licensing and manpower for implementing two domains. It also depends on what you are going to run. Terminal server as a means to administrate and for applications is better in 2k and Exchange 2000has alot of pluses. On the other side, going with 2k does mean lots of testing of apps, especially in house products and involves a lot of planning. If the push is for something right now, NT is pretty quick for a single domain, where as 2k can really mess you up if your planning is rushed and you haven't tested fully.

Collapse -

No NT Domain: Go NT or W2K?

by Bad_karma In reply to No NT Domain: Go NT or W2 ...
Collapse -

No NT Domain: Go NT or W2K?

by ec364 In reply to No NT Domain: Go NT or W2 ...

Windows 2000 is a good NOS. You can go straight to it as your network OS. But bear in mind that is not perfect. You'll encounter rough times and resources are few yet. Hardware and software, although available, are still in the wait and see stage. If you're starting to build a network, you don't want to be a sacrificial site where everyone would learn. You would want one that is robust and tested. Problems are there but solutions are there too. A lot of them. A lot of us. So, I would go with what the management's feeling is. My company didn't go for it too, for now. We decided to let about a year, a year & a half to pass before we'll reconsider to jump to Win2K. Don't get me wrong, we have a small isolated network running Win2K. And all wesay is, eeehhhhh, let's see.

Enjoy!

Collapse -

No NT Domain: Go NT or W2K?

by Bad_karma In reply to No NT Domain: Go NT or W2 ...
Collapse -

No NT Domain: Go NT or W2K?

by bstei18 In reply to No NT Domain: Go NT or W2 ...

If you're setting up a new domain I would go with W2K. You won't have the headaches later when you'll need upgrade to it or the added expense. It also has better security features built in than NT but some of these features require all machines to be W2K.

The drawbacks are the need for more powerful machines, but who doesn't need those. Also, with all the new stuff, learning it will take a little longer.

Collapse -

No NT Domain: Go NT or W2K?

by Bad_karma In reply to No NT Domain: Go NT or W2 ...
Collapse -

No NT Domain: Go NT or W2K?

by kanaant In reply to No NT Domain: Go NT or W2 ...

I agree with Aekland,
I'm in the same situation as you, I decided to move the messy network i had here to a Win2K OS and AD structure.. i didn't find any problems in the process except for a few apps that didn't work under 2k, fortunat for me that win2k can run in a mode supporting both nt4 and win2k, so keep atleast a NT4 server u can fall back on if the app doesn't run in win2k.
as for performance and managability, Win2k is the defenate choice.

Collapse -

No NT Domain: Go NT or W2K?

by Bad_karma In reply to No NT Domain: Go NT or W2 ...
Collapse -

No NT Domain: Go NT or W2K?

by calves In reply to No NT Domain: Go NT or W2 ...

I have tested Win2K Beta 2 and 3 and now I have a small lan in home with Win2K and a hybrid at work consisting of NT Domain, Win2K joining the Network, and other OSs. I think you should not give the management a report showing a big bill for something that will replace what they already paid for and it's working. Now, you can show the management how adding a few Win2K machines can enhance the network, and using what Win2K has best to offer:
-Less reboots
-Better RAS Management, particularly for VPN.
-Better Administration Tools
Anything that will make your Win2K look better then the NT4. Justify even a test machine where you can test services and programs in your environment on a machine that can be easily erased. But, how to justifyFile/Print Services, or an upgrade of a software, where the version you have is not compatible with W2k? I also advise you to get to know Active Directory first, before you get into a pure W2K network. A lot things changes in the new OS.

Good luck!

Collapse -

No NT Domain: Go NT or W2K?

by Bad_karma In reply to No NT Domain: Go NT or W2 ...
Back to Windows Forum
10 total posts (Page 1 of 1)  

Related Discussions

Related Forums