Linked by Thom Holwerda on Sat 6th Aug 2005 17:21 UTC
Windows Microsoft is planning to reissue the Windows 2000 Service Pack 4 Update rollup that it first launched in late June. While the company did not specify a reason for the planned reissue, a number of Windows 2000 users who have installed the download have complained of a variety of problems, ranging from incompatibility with third-party security applications to network-printing issues.
Order by: Score:
v Windows 2000 is obsolete
by Anonymous on Sat 6th Aug 2005 17:58 UTC
It shows two things
by rapont on Sat 6th Aug 2005 19:13 UTC
rapont
Member since:
2005-07-06

1. Debian is not the only body that "reissues" software (e.g. Debian 3.1.r0a)

2. Microsoft obviously doesn't care about Windows 2000, or at the very least concerns it as an afterthought, as this should have gone through proper Q&A testing before release!

Reply Score: 1

RE: It shows two things
by Anonymous on Sat 6th Aug 2005 20:41 UTC in reply to "It shows two things"
Anonymous Member since:
---

Well then i guess the same thing could be said about Debian, which also reissues software...

Reply Score: 1

v ridiculous
by Anonymous on Sat 6th Aug 2005 20:41 UTC
RE: ridiculous
by Anonymous on Sat 6th Aug 2005 21:38 UTC in reply to "ridiculous"
Anonymous Member since:
---

Nightmares are the reality. Linux, Windows, MacOS X.. you name it: all require maintenance, hence - administrators.

By the way, MS isn't too bad: normally, you get updates once every month. Use WSUS or similar tool to manage them and you'll be fine.

Reply Score: 0

Intesting problem...
by Anonymous on Sun 7th Aug 2005 02:41 UTC
Anonymous
Member since:
---

We got bit in the arse my this last month. The rollup changed a file that all the patches applied didn't change. The result of that change is that tha MTA's in Exchange 5.5 took a dive. it took 2 weeks of troubleshooting then a call to MS support who said that they had an internal memo that the rollup could cause a problem with Exchange.

My problem is, why is it that all the patches combined don't do this, yet the rollup does. Does the Rollup change more then the patches it's supposed to cover?

Reply Score: 0

RE: Intesting problem...
by Anonymous on Tue 9th Aug 2005 18:29 UTC in reply to "Intesting problem..."
Anonymous Member since:
---

Know the feeling. We got bit by the "You cannot save files from Microsoft Office programs directly to a floppy disk after rollup" bug.

Reply Score: 0

microsoft should have issued a service pack
by pravda on Sun 7th Aug 2005 08:31 UTC
pravda
Member since:
2005-07-06

Someone should be fired for making this dumb idea of creating a subpar service pack and calling it a "rollup".

Microsoft should have *done right by the customer* and made a real service pack.

Microsoft should have *done right by the customer* and *tested* a real service pack.

Instead we get the roll-it-over of the roll-up.

This behavior and shoddy engineering is not a good sign that Microsoft is changing for the better.

Reply Score: 1

Anonymous Member since:
---

this is nothing new. Those of us who still have to deal with NT 4.0 in some capacity know exactly what it's like to have a four year old service pack and dozens of subsequent patches to deal with.

Reply Score: 0

Rollup != WU offered hotfixes
by Anonymous on Sun 7th Aug 2005 10:54 UTC
Anonymous
Member since:
---

A service pack, or an updaze rollup doesnt mean, that only the hotfixes offered by WU are packed into one executable. WU offers mostly the critical patches, but MS issues dozens of other small fixes. You have to hunt these, if you encounter a problem on your server (if that is not so widespread). Maybe that was the problem of this rollup: it contained a hotfix, that was apllyed earlyer only by a small number of users.

Reply Score: 0

Driver issue
by Anonymous on Sun 7th Aug 2005 15:28 UTC
Anonymous
Member since:
---

The update is being reissued because of a problem in the driver for older ISA/MCA SCSI adapters that causes the system to bluescreen on boot after installing the update.

Reply Score: 0

TCP/IP Event Alerters
by Anonymous on Sun 7th Aug 2005 15:30 UTC
Anonymous
Member since:
---

I wonder if they finally got off their backsides and addressed the TCP/IP based Event Alert API bug in SP4 that completely breaks them and causes many things that rely on them to stop working...

Reply Score: 0