Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Disadantages of NT Operating Systems
- Thread starter essa2000
- Start date
Oooohh, it's almost like trolling....
Anyhow, the disadvantages of NT are varied and situational. In particular, NT is an old OS, at 6-7 years it's pretty long in the tooth and does not come with out-of-the-box support for many modern technologies. Furthermore, Microsoft is ending support for NT 4.0 beginning in June of this year (it will be phased out over time, say the next 2 years).
NT's security flaws, particularly in regards to the IIS product running on NT are legion.
NT does not make a particularly robust application server and the Terminal Server option is pretty damned anemic compared to what is offered by the various *nixes.
NT is frigging expensive compared to an open-source solution.
NT is unstable. 'nuff said.
The thing to remember is that NT 4.0 was essentially MS's third attempt at a NOS. It was a major improvement over NT 3.51, but it is still not up to level of a *nix solution (which has been around in one flavor or another for what, 30 years or more?).
Now, if you want to talk NT 5.0, aka Windows 2000, many of the above mentioned items have been ameliorated, though not entirely eliminated.
Anyhow, the disadvantages of NT are varied and situational. In particular, NT is an old OS, at 6-7 years it's pretty long in the tooth and does not come with out-of-the-box support for many modern technologies. Furthermore, Microsoft is ending support for NT 4.0 beginning in June of this year (it will be phased out over time, say the next 2 years).
NT's security flaws, particularly in regards to the IIS product running on NT are legion.
NT does not make a particularly robust application server and the Terminal Server option is pretty damned anemic compared to what is offered by the various *nixes.
NT is frigging expensive compared to an open-source solution.
NT is unstable. 'nuff said.
The thing to remember is that NT 4.0 was essentially MS's third attempt at a NOS. It was a major improvement over NT 3.51, but it is still not up to level of a *nix solution (which has been around in one flavor or another for what, 30 years or more?).
Now, if you want to talk NT 5.0, aka Windows 2000, many of the above mentioned items have been ameliorated, though not entirely eliminated.
- Thread starter
- #3
ChrisRAnthony
Technical User
IMHO The main problem with NT is the high support costs. This is essentially due to the high cost of training!!. I have found that the training for Linux costs virtually nothing compared with NT!!!!!!!
Guest_imported
New member
- Jan 1, 1970
- 0
I'm not an NT lover and was forced down that route some years ago.
I don't think it is as bad as the previous posting made out.
I have about 6 NT servers some on home built servers.
The simple answer with NT Bitter experience has shown :-
1) Always look for the latest drivers on teh web.
2) Always grossly overspecify your server in all areas
3) Always install as 'vanilla' unless you know exactly the changes you require or have the time and facility to work it all out.
4) Obvious one - Never use it as a workstation
My servers get re booted about every 45 - 60 days as an operating procedure and never give any problems.
I'd prefer Novell but sadly it is being marginalised even more so than Unix ssytems at present.
I don't think it is as bad as the previous posting made out.
I have about 6 NT servers some on home built servers.
The simple answer with NT Bitter experience has shown :-
1) Always look for the latest drivers on teh web.
2) Always grossly overspecify your server in all areas
3) Always install as 'vanilla' unless you know exactly the changes you require or have the time and facility to work it all out.
4) Obvious one - Never use it as a workstation
My servers get re booted about every 45 - 60 days as an operating procedure and never give any problems.
I'd prefer Novell but sadly it is being marginalised even more so than Unix ssytems at present.
There are alot of specific bugs with NT and quite frankly I haven't got the time to describe them all. I do NOT think NT is a terrible OS- the poster asked what the disadvantages were, so I gave a broad outline.
The killer point is that come June of this year OEM licenses will no longer be available as MS begins phasing out the product. June of 2003, you will have to pay for hotfixes, etc. That right there is a show-stopper because no one in thier right mind deploys an infrastructure based on an un-supported NOS.
The killer point is that come June of this year OEM licenses will no longer be available as MS begins phasing out the product. June of 2003, you will have to pay for hotfixes, etc. That right there is a show-stopper because no one in thier right mind deploys an infrastructure based on an un-supported NOS.
Just like what kjonnnn and others said, the problem with NT is mainly situational and the kinds of applications being run. I have a 10 NT Server shop with 100 users and for LAN/WAN environments and a mix of sp4 and sp6a. It could be luck or something. No major hiccups or anything(knock on wood). It's really a shame that it's being phase out, but for my experience I would say you would have enjoyed it. Think of it as the Maytag Man.
My 2 cents.
I have been working in a Novell as well as a NT4/2000 environment.
To be short an to the point both ends has it ups and downs.
Bottom line if you do not look after(pamper)your machines they will give you a load of problems.
Irrespective what OS you run. Hope this Helps
Maruis
"I sleep at home not on my Job!"
I have been working in a Novell as well as a NT4/2000 environment.
To be short an to the point both ends has it ups and downs.
Bottom line if you do not look after(pamper)your machines they will give you a load of problems.
Irrespective what OS you run. Hope this Helps
Maruis
"I sleep at home not on my Job!"
It doesn't hold up to change. You configure it for a job leave it alone and it runs great. If you want to broaden it's scope of work or change what you designed it for, you have to take it offline, (with the woes that entails) re-configure, test it and bring it online again.
Thats great in some environments I love starting out fresh anyway, but in some places or at some times it isn't practical...
Thats great in some environments I love starting out fresh anyway, but in some places or at some times it isn't practical...
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question