Plans are underfoot for the upgrade to XP as you type. They had to be put on the back-burner for a few months, but we will be XPd up by November, as far as I hear.
Plans were afoot when I first arrived in October. In January I checked and IS were going to be the first to change over.
It's now June...
Oh, and we're using IE5.0, which is bug-filled, doesn't have lots of fixes that protect against known hacks and is generally recommended against use...
RBOS also. Luckily I have nothing to do with that in my job. We have far too many piss-ant home grown applications that will probably be a nightmare to convert to XP. I'll stick to my ZOS....
Converting NT apps to XP should largely take no work at all. Unless you're doing deep, dark, operating system stuff (anti-virus, for instance), your app should just work.
Its only the workstation version thats being withdrawn, and about time too TBH, its very long in the tooth. Server will be supported for a while yet.
January 1, 2004 Beginning on this date, non-security hotfixes are no longer available.
January 1, 2005 Beginning on this date, Pay-per-incident and Premier support will no longer be available. This includes security hotfixes.
January 1, 2005 (or later) Online support will no longer be available.
Note the (or later), these dates have already moved several times and will quite possibly move again. The fact is that large sections of the Industry are still lurking about on NT4 server. MS would dearly love to remove support so they can focus on 2k and 2003, but as long as large swathes of companies still use it, it will be supported.
Um, did you misread the bit where I said that it was desktops I was talking about?
I have no idea what our servers are, but I think we're on some kind of Novell, as it's Novell logins that we see, and Novell's Application Launcher that my programs are all available through...
Nope, I saw that. I just dont see how workstations are as big a deal to update as servers. Big propritary server apps can be a right sod to migrate. But there is much less of this client side.
Frankly I have little sympathy for companies who don't keep up to date then get all shocked when MS withdraw support for old apps. It doenst mean you have to stop using it, you just have to spend a bit more money and effort supporting it. On the plus side there's a huge pool of data and ability out there to draw upon.
Its like owning an old car, the manufacturer won't keep making spares forever, so you have to use third parties. This is more expensive and awkward, but thats the price you pay for using older stuff. The same is true for nearly anything complicated that you buy, from a PC to a washing machine.
Oh, I'm sure they aren't that big a deal to update - most software will probably run just fine. And as the PCs here can network boot and can be controlled from a central point, I'm amazed that it's not just a case of causing them to network boot from a central source that causes a new install to wipe the hard drive and install the stadnard build of XP.
Bandwidth constraints would stop them doing all 11,000 PCs in one night, certainly, but you could easily do a heck of a lot of them at once...
I'd love to get a chance to play with Linux, but it's not going to happen in the near future. Work certainly aren't going to move across to it, not when our front end apps are produced on VB...
no subject
Date: 2003-06-27 02:20 am (UTC)no subject
Date: 2003-06-27 02:50 am (UTC)It's now June...
Oh, and we're using IE5.0, which is bug-filled, doesn't have lots of fixes that protect against known hacks and is generally recommended against use...
no subject
Date: 2003-06-27 03:55 am (UTC)no subject
Date: 2003-06-27 02:23 am (UTC)no subject
Date: 2003-06-27 02:48 am (UTC)no subject
Date: 2003-06-27 06:15 am (UTC)no subject
Date: 2003-06-27 02:30 am (UTC)I'll stick to my ZOS....
no subject
Date: 2003-06-27 02:48 am (UTC)Converting NT apps to XP should largely take no work at all. Unless you're doing deep, dark, operating system stuff (anti-virus, for instance), your app should just work.
no subject
Date: 2003-06-27 02:47 am (UTC)January 1, 2004 Beginning on this date, non-security hotfixes are no longer available.
January 1, 2005 Beginning on this date, Pay-per-incident and Premier support will no longer be available. This includes security hotfixes.
January 1, 2005
(or later) Online support will no longer be available.
Note the (or later), these dates have already moved several times and will quite possibly move again. The fact is that large sections of the Industry are still lurking about on NT4 server. MS would dearly love to remove support so they can focus on 2k and 2003, but as long as large swathes of companies still use it, it will be supported.
Current details of NT4 retirment are here.
http://www.microsoft.com/ntserver/ProductInfo/Availability/Retiring.asp
no subject
Date: 2003-06-27 02:52 am (UTC)I have no idea what our servers are, but I think we're on some kind of Novell, as it's Novell logins that we see, and Novell's Application Launcher that my programs are all available through...
no subject
Date: 2003-06-27 03:49 am (UTC)Frankly I have little sympathy for companies who don't keep up to date then get all shocked when MS withdraw support for old apps. It doenst mean you have to stop using it, you just have to spend a bit more money and effort supporting it. On the plus side there's a huge pool of data and ability out there to draw upon.
Its like owning an old car, the manufacturer won't keep making spares forever, so you have to use third parties. This is more expensive and awkward, but thats the price you pay for using older stuff. The same is true for nearly anything complicated that you buy, from a PC to a washing machine.
no subject
Date: 2003-06-27 04:35 am (UTC)Bandwidth constraints would stop them doing all 11,000 PCs in one night, certainly, but you could easily do a heck of a lot of them at once...
no subject
Date: 2003-06-27 05:24 am (UTC)no subject
Date: 2003-06-27 05:40 am (UTC)