Discussion Locked

NT4, how are your customers responding to the upcoming end of cycle support

0 helpful
31 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
On the subject of NT4, how are your customers responding to the upcoming end of cycle support issue?

31 replies

by haileyan

I upgraded all of my NT40 servers 2 years ago. Support is so much easier without it.

by mjost

Lots of inplace servers and, I am sure, that alot of business' havent even thought about it. Wondering if MS will extend it again but it doesnt appear to be on the plate.

by clemmy

Most of our clients that resisted the win 2k upgrade are moving to 2003. This has been more due to the age of servers rather than the need to move away from nt4.
As a joint operation moving in new servers with new O/S is a lot easier than in line upgrade on old hardware.

by cjmpe

My company is only reluctantly moving to Win2K3 because of the age of our servers. However, since we don't qualify for upgrade licenses, we intend to keep the NT4 boxes running as NAS type devices until they die.

by mjost

Moving to the newer OS for a larger organization is not just the hardware and new OS. It is other costs that, after factoring in, are some what daunting to explain such as CAL's for multiple servers (and they do not migrate either). MS has pushed 'consolidation' as an off-setting factor but if you are a medium to small business for 2 to 5 servers it is going to hard bite off. I notice MS is offering some offsetting incentives for the CAL price issue. Did your organization do any 'consolidations'of hardware?

by rgun2515

Most companies feel it's a way Microsoft forces revenue. They feel if the system is working, why change it. If it's not broke, don't fix it is the aptitude today. Most companies look at their equipment as a tool. It's there to make money and nothing more. Would you change out all of your wrenches in your set just because (Sears) craftsman came out with a new line and would not replace your old one for free if you broke it?

I think, if Microsoft doesn't want to support the OS any longer, that's fine, Give out the source code to the expiring system. Someone would pickup the support. We with programming knowledge could even make changes to the system if need be. I would never be able to create a system for a company and NOT leave the source code with them when complete. Could you see a programmer going to a company 5 years after completion of a project and saying, OK, the system I built is no longer good. You have to hire me to create a new one now. I know it still works fine, but that doesn't matter. Its time. It just is.

by mjost

Migration factors - An upgrade is going to cost more time in documenting and planning and finally all the testing time. All those security issues with moving to Active Directory from NT4 ect. A new machine is a great way to go allowing you to deploy it in a pilot situation first. The big plus in all of this is that we should be finally getting all the permission/file security corrected from all the years of grafting more and more onto the existing infrastructure.

by spikeymike

If you're going with new hardware anyway - have any of you considered an alternative platform? Linux works - and NO CALS for basic file and print. Running exchange 5.0 or 5.5 - there are alternatives to Exchange 2k... Going from NT 4 to 2003 has a learning curve too you know.

-Mike

by gawiman

"Pay us for the desktop OS's, Pay us for the server OS's and pay us yet again for a separate license to connect each desktop to each server."

I will never understand CAL's. I've read explanations and justifications, but it still just seems to fit under the "because we can" column.

Wish we could go to a more liberal server OS but our organization just thinks MS is the bee's knees.

by tomsal

I'm with you on that too, I don't understand CALs either. I basically think it comes down to nothing more complex than simple greed. Its a way to get more money out of your products.

I can understand needing a license for each client desktop and each server -- that is fine by my book and that's how simple it should be. If you buy 100 copies of the desktop software, and buy 5 copies of the server software -- that's it. You should need nothing more for legalling using that software in a networked fashion. I should be able to use any of my 5 servers in any way I deem I want to and they should be able to connect to the 100 clients in any array, in any order and as often as needed. No connection limits or restrictions. No server "role" restrictions.

But once rules are applied "But you need ANOTHER license if your server is used as this, but if your server is that you don't need a license..and oh by the way how many connections are you going to use with that server...blah blah".

Basically I hate software licensing all together to be honest.

I abide by the rules of course -- you have to in business, its part of being professional; but it doesn't mean I think the rules are right.

I just think software should just be as simple as this:

1) ALL purchased software from any manufacturer should grant the purchaser legal use of the software on 2 machines at the same time. This would fill the need for "One copy at the office, one copy at home".

2) No restrictions on use in networked environments, simply you need to purchase 1 copy for each unique computer.

3) The license should be attached to the specific purchaser NOT the machine its installed on. If my computer dies, none of this "that software only works on that hardware image" BS --- no..If I go through 500 machines over the years, I should be able to use that ONE copy and re-install on each new machine as I need too.

Ok I'm done...

;)

by hmarks

Remember that MS's CALs were a lot more sensable than Novell's 50 user version and 100 user versions of NetWare. They would charge a different price for each and stop accepting connections when you hit the limit.

All the commercial (as opposed to open source) software vendors charge more for bigger sites somehow. Oracle charges for named users or processor power.

If they only charged a fixed price for SQL server or Exchange Server regardless of the number of users it would price it out of the mid market not to mention small.

CALs, pain in the butt they are, are the fairest way to get money based on usage.

by hal 9000

That's how it should be but because of one companies "GREED" it gets far too complicated. Trying to understand their reasoning working in that fashion gives me a headache so now I just go with the flow and no longer ask questions as the explanations are far more time consuming that I have to spend.

Col

by Member 28363368

I do consulting in the Wash DC area for a number of federal agencies. At least two of them have experienced the track record of instability of Microsoft products and are actively seeking alternatives.

The endless cycle of service packs to correct glaring flaws, serious security issues, support fade and increased cost licensing has prompted several agencies to look elsewhere. The choices are not as poor as you might think.

When an agency decides on a fixed set of applications, the OS need not be very complex. I have done several TCO (total cost of ownership) analysis studies and discovered that the cost of Microsoft products actually come pretty close to contractor bids to create original open source code to perform many of the same functions. In one study of 2,100 systems, it was decided that 120 could stay on MS products for network file exchange and internet compatibility while the others would convert to a proprietary OS and an open source office suite that met nearly all of the demands of the agency while also virtually eliminating OPSEC security issues and instibility.

I think this is a trend that will continue to spread as companies become more aware that they can stop the time and effort loss due to the massive and very costly problems of spam, virus and popup attacks as well as compatibility, integration and stability problems.

Let me give you one example - An office within DoD with more than 200 networked PC's running XP recently was invaded by a malware agent called ABOUT:BLANK that robs contorl of the browser. This office is in its NINTH WEEK of trying to eradicate that pest! So far, estimates are that about 6 hours per user and about 45 hours for each of several IT support people have wasted time on dealing with this persistent invader. That equates to more than $70,000 in lost labor time. This office is pursuing legal action against ABOUT:BLANK and has started a drive to get Congress to allow the use of other government resources (IRS, FBI, NSA) to respond to companies that create and distribute such malware. When taken in the context of a federal market that is significantly more aware of OPSEC issues since 9/11, the balance has shifted from trying to make do with what is available to permanently correcting the problem.

by mjost

Everybody complains about MS being a security rabbit, fixing things as they show up.. but in reality all products are designed to just preform the basic customer needs and no more inorder to get the product to market. Sales and cashflow is King in getting product to market.

But MS XP service pack 2 is aimed at stopping most of theses ADware/Spyware issues. Who but the Government and very large enterprises are really driving this push by MS.

Just goto: http://secunia.com/ website and check your favorite product or vendor and see just how many recent multiple vulnerabilities issues, which can be exploited by malicious people to cause a DoS (Denial of Service), spoof content of websites, or compromise a vulnerable system that were flying under the radar but are now coming to light.

by Member 28363368

You prove my point when you said that

"MS XP service pack 2 is aimed at stopping most of theses ADware/Spyware issues"

Note that this is for XP only. No such correction is offered for the other OS's on the street that collectively outnumber XP by a considerable amount. The reason is that they can use the stability/security card to pressure people to upgrade.

1. Hey - I just bought a car but it is hard to control and crashes alot.

2. Oh, you say the new car doesn't do that?

3. I guess if I want to stop crashing, I better buy it.

4. Go to #1

:-)

by gometrics

You can get rid of "About Blank" in 20 minutes by unhiding the installer files which are set as "super hidden" and using Hijack to clean the registry.

To prevent it from coming back just set the Internet Explorer settings to High Security to stop ActiveX. In W2K or W2K3, having your users in the user or power user group will stop them from installing software from the internet.

by Member 28363368

You are absolutely right - those techniques work...and we tried them early on in the process, however, setting the Internet Explorer settings to High Security has other serious consequences.
Nice idea but why should I suffer reduced capabilities just to respond to an intrusive advertiser?

Here's the problem - Most government agencies now use the internet for all their communications. Some use VPN's, some use encryption but most just rely on normal email and browser features to exchange files and to do "document conferencing". That is when five offices sign onto one web site to access a slide show while they talk on a conference call phone. The one common web site might be "netmeeting" or, more often, some other COTS program that gives them added features like live video feeds, etc. There in lies the problem. No Activex, no document conferencing. It also reduces some features setup on federal and other web sites. We all have been using HijackThis and CWShredder and they work but do not stop the reinvasion thru the network or from common access files. The problem of getting everyone, all at the same time, to do the right thing is not easy and the limited IT staff and the nature of their jobs makes it difficult to sweep thru all the computers before someone reinfects and starts the process all over again. We have found commercial antivirus programs that work but at this late time in the fiscal year, money is short and they aren't cheap. Its a work in progress.

by Member 29884799

I've moved my smaller clients to linux using samba pdcs. Microsoft dropped the small office ball. I can have the same (albeit without some of the NT foibles), networking environment without the morass of Active Directory. The migration is painless and everything works better. If I need to I can setup openldap and have all the "benefits" of active directory. Most of the users see no difference, except the server does not reboot as much. And I use the bsod screensaver so they think it is acting normal. :)

by mjost

Linux using samba is ok but using MS client (as probably 90% of end users are) may cause you to be scurrying around to get a work around to access your samba pdc if MS changes anything major. Then what? Your Customers are DOWN for the count??? I'd say the savings factor that is enjoyed for open sources is moot when compared to the overall compatibility to the rest of the small to medium business clients in the world. Now look at all the law suits beginning to appear in the Other OS side. I would always recommend to the SMB customer to leave the other OS?s to the bigger players that can afford to specialize in both a Ford and GM product?

by Member 28363368

Actually Microsoft doesn't want to support the OS any longer because it is no longer porfitable for them to do so. Long ago, MS adopted the same mentality as the auto industry - change out your vehicle (OS or application suite) every two years. Their schedule started like that back in the days of Win95 but complexity and codeing flaws have lengthend the recycle time to more like 4-5 years. Their business model does not allow for the creation of a stable, long term OS because, like cars, they must make repeat sales to the same customers more frequently than that to maintain their high profitability.

MS will not willingly release the source code, even for older OS for the same reason unless they are forced to by legal challenge but that is not likely.

You are right that you would never be able to do what they do but they get away with it because of size and lack of alternative choices - that is the penalty we pay for a lack of a competitive market. Their legal tactics have achieved exactly what they were intended to do - intimidate people into not even thinking about challenging them in court or in the marketplace. In that regard, they ahve been very successful - even when challenged by the government.

Not only do they routinely say they will no longer support a previous product, but they will create pressure to force a move to the new system. This is done by making the file formats incompatible with previous versions of their applications - like they did with MS Word, and MS Project - this forces companies to upgrade to communicate with clients or other companies that have upgraded.

MS also will incrementally add hardware compatibility - some is because they add it as it is developed but rather than offering drivers for previous versions, they market strongly for you to upgrade. Just look at the Win98, Win98SE and Win-ME changes - each added only one or two new drivers but businesses and government offices were pressured to upgrade because of instability, security and compatibiity issues.

Isn't it odd that a company can sell you a product and then announce that it is so flawed that they will stop supporting it and you are forced to buy another product from them?

Isn't it odd that MS sells a product that has so many security problems as to create a MASSIVE second industry just to take care of the issues that result from a flawed design? By contrast, look at what happened when the Ford Explorer has bad tires? Recalls, law suites, massive press coverage! MS OS security flaws are so common and routine that they get almost no notice unless the fix is motivated by a world-wide virus attack - as has happened several times.

Have you noticed that the issuance of updated versions of MS OS and Office suite tools alternate over time? Win98/ME is replaced by Win2000 and then Office 2000 comes out then XP replaces Win2000 and then Office 2002 comes out. This alternate expiration and introduction assures MS a steady cash flow over time.

Would you pay for a car that you never really owned? Take a look at the XP license (EULA) and you will notice that in all that legal language, it actually remains the property of MS and that you have effectively leased it from them. That gives them the right to inspect your use of their product, to shut it down if, in their estimation, you may be using it wrong and they can effectively control where and how you install it. This is especially true of their OEM license that comes with new computers.

Their new Software Assurance program ought to be called MS Profit Assurance program as it forces companies to "subscribe" to the use of their OS and office suite software rather than own it outright and upgrade as needed by the owner. Now, to some degree, it is MS that decides when you will upgrade. A careful look at what you actually commit to and the total cost of ownership (TCO) in their OEM, Open Value, Company Wide Option and SA programs would really surprise you.

You can fool some of the people some of the time but after awhile, they get fed up and look for alternatives. That is happening now in the federal sector and the trend is spreading fast.

by selectiveden

I presume you are in the IT industry and are involved in software development.
On that basis, have you ever developed and implemented a solution that meets all current & future requirements and is 100% bug free? If you have, you are in a minority of one and should be in a position to challenge Microsoft for supremacy!

by mburns

If I want to buy parts to fix a 1949 ford ... I can buy them or at the very least obtain the exact spec's and commission any competent machinest to make them.

I can't buy leaded gas but I can obtain additives that may be added to compensate for that.

lets see how MicroSoft is different in that reguard...

I still have a perfectly operating 486 hardware (infact I might have a 386 or even a 8086) Microsoft informs me that there is no way to obtain a valid user license for an operating system unless I could buy one from someone else who then quit using it. The license may only be obtained by having in ones possion the origional media and CoA.

The only justification must be a political/legal (ie someone could/would sue them for something) reason. MS stated that they no longer have any means to support any operating system that would run on the hardware - and it would be a violation of the license agreement to install any existing copy on a machine that you have no CoA for. Also there is no way from them to obtain a valid CoA.

To my way of thinking they have abandoned the OS's capable of running on the hardware, when that happens in the automotive world you can often get an adapter kit - reman'd parts - or if you are willing to pay or have sufficent skill fabricate one. The license agreement bars using any of those remidies.

Not to restart the dreded debate about InternetExplorer and Netscape... but that also has analogs in the auto industry that somehow are not the same in the software business...

GM places connectors in its wiring harness for the Audio entertainment systems installed by them at the factory if you want to put your Sony system into the vehicle your not prevented however its on you and/or Sony to either use the existing connectors on the wiring harness either by using some sort of addapter or run your own wires either of which you can do.

read that as use the existing dialer/network stack API's and dll's or write your own but MS isn't just like GM required to put the wires there for you if you don't want to use the ones provided. Are there performance issues ... you bet that is the advantage/disadvantage of using the "factory" installed components.

by mburns

If I want to buy parts to fix a 1949 ford ... I can buy them or at the very least obtain the exact spec's and commission any competent machinest to make them.

I can't buy leaded gas but I can obtain additives that may be added to compensate for that.

lets see how MicroSoft is different in that reguard...

I still have a perfectly operating 486 hardware (infact I might have a 386 or even a 8086) Microsoft informs me that there is no way to obtain a valid user license for an operating system unless I could buy one from someone else who then quit using it. The license may only be obtained by having in ones possion the origional media and CoA.

The only justification must be a political/legal (ie someone could/would sue them for something) reason. MS stated that they no longer have any means to support any operating system that would run on the hardware - and it would be a violation of the license agreement to install any existing copy on a machine that you have no CoA for. Also there is no way from them to obtain a valid CoA.

To my way of thinking they have abandoned the OS's capable of running on the hardware, when that happens in the automotive world you can often get an adapter kit - reman'd parts - or if you are willing to pay or have sufficent skill fabricate one. The license agreement bars using any of those remidies.

Not to restart the dreded debate about InternetExplorer and Netscape... but that also has analogs in the auto industry that somehow are not the same in the software business...

GM places connectors in its wiring harness for the Audio entertainment systems installed by them at the factory if you want to put your Sony system into the vehicle your not prevented however its on you and/or Sony to either use the existing connectors on the wiring harness either by using some sort of addapter or run your own wires either of which you can do.

read that as use the existing dialer/network stack API's and dll's or write your own but MS isn't just like GM required to put the wires there for you if you don't want to use the ones provided. Are there performance issues ... you bet that is the advantage/disadvantage of using the "factory" installed components.

by too old for it

The last time I saw Windows NT 4.0, it was in a classroom environment at the dawn of the Windows 2000 era. I think I ran Workstation for about a month on a 486, until I could upgrade the motherboard.

The consulting firm I hooked up with hit the ground running in October 2001 as a Windows 2000 shop. Since then we have had one migration from NT4, which involved new hardware and a nice new install of SBS.

I still have a box of retired NT licenses and CALs on the off chance that I would run into some hardware that it would run on better than 2000, but these days such hardware would likely get a install of Mandrake Linux instead.

Too bad these discussions always seem to bring the Bill Gates/Microsoft bashers out of the closet.

by mjost

I just came from a shop that has extensive NT4 server infrastructure and a few newer w2k domains and member servers running under the NT4 PDC. They're not going to replace the machines and the OS until they have to. All those exchange 5.5's that are out there prolly running on a NT4 domain too. I see alot of work ahead!

by tomsal

I guess I never thought of Oracle or Novell's way of doing things -- that does suck.

I just don't understand why there needs to be so many rules or complexities to it -- particularly Microsoft's license structure.

I think there should be discounts on volume but besides that just make it simple like:

A) You need to buy at least one FULL copy of a server OS for each unique server you have (doesn't matter if its 1 cpu or 16 cpu's)

B) You need to buy one full copy of the Desktop OS for each machine but if you buy more than say 10 the cost of each copy is discounted by say 25% or so.

C) Finally the licenses should be volume discounted, with no need to pick a special program or be a certain size company -- its simply your discount is based on your volume purchase and it happens automatically. Further more a CAL should be no more than say $10, because let's face it they still made money on the initial software sale and you still legally paid for each copy already.

That's it.

No openvalue this, volume licensing that, these set of rules apply to how you use this software or that software.

Hey when software licensing gets to be so complicated that it can be nearly a full time job just managing that --- something is seriously wrong with the licesning picture.

by mjost

If newer then why would these workstations have been setup with everything wide open when they could have been locked down to stop any IE with high level security and control Program installs with GPo's? And, when Rarely needed, openned back up just for one-time configuration of any Active-x needs?

by hal 9000

Who runs a piece of software that will only work on NT4 so I'll be continuing to use that platform for a very long time to come. The software in question has a very limited appeal but is vital to the industry involved so it has not been rewritten since the thing was originally developed.

They seem to have the idea if "It Ain't Broken Don't Fix It!" and since it works very well most of the users are very happy with it as it stands. I might add that because this piece of software is used on construction sites the hardware that runs it lives in a very hostile environment so the computers have a short life expediency as they tend to suck in a lot of dust and other air borne rubbish.

Col

by mjost

Well why would (should) you ever upgrade when an app is running great. But have you tried this program on w2k or newer? and under the W95 Compatiblity mode option? I'd be curious to see what happens(ed).

by hal 9000

When I first replaced a dead unit I did try Y2K Pro & Server but the software wouldn't run on that platform so I had to load NT4 again.

Previously I had tried it on 98SE mainly because there are USB devices used so I didn't bother with the older version of 98 and for the same reason I haven't tried it on 95 either. But as the software concerned is only $80,000.00 AU + hardware and that is laser stuff that goes on heavy earthmoving equipment as well as around the site it is a bit expensive and hasn't been rewritten and from what I can find out there currently are no attempts at rewriting the program so I'm stuck with NT4. Not that I really mind as it keeps me busy and off the streets at night. I have a copy of it here so I can load any replacement computers before I take them out on site and while I can not test it to see if it is working I can at the very least make sure that it runs, which it doesn't do on any other Platform although I did think it would work on Y2k.

Because it allows the operators to scrape the soil to an accuracy of .5 mm I have yet to run across any company who currently uses it who are willing to try something else {even if it is available} apparently it saves then quite a lot of money by not requiring constant surveys being done and back filling and compacting if too much is removed.

Also being earth movers they have a different temperament to most IT customers and will quite willingly tell you where to go if you try to get them to change things that are currently working.

Col

by elphick

If a user has an NT4 Server and it is running okay then I will leave it alone.

I just make sure every possible security protection is installed (hardware firewall, AV, latest MS Updates, backup, secure passwords, etc) and I just wait for the next time the server fails and can not be repaired. The user appreciates not having to buy a new server just yet. I postpone the hastle of an in-place upgrade.

For low usage servers for undemanding users NT4 is adequate. Yes, there are much better O/S's, but if the user is happy (and he prefers to keep his money in the bank) then why change things.

For the NT4 Servers which are not stable they have been upgraded or dumped over 2 years ago.

This discussion is closed to new replies.