The second service pack for Windows 2000 doesn't offer a lot of new thrills, but it does kill off a few bothersome bugs. Do you need it?
Talk about a Windows network operating system for more than a few minutes and the words service pack are likely to pop up. From NT days to the current Windows 2000 fare, Microsoft has periodically used service packs (SPs) to update its network operating systems in order to plug holes, fix bugs, and add features.
The latest pack for Windows 2000 is SP2. You can download it from the service pack Web site or order a CD for US$19.95. While Microsoft considers some packs required updates, SP2 has been tabbed a recommended update. In other words, install SP2 if you find that it fixes a compelling problem.
Depending on how you fared with previous even-numbered service packs and whether you're superstitious, you might shy away from SP2. But our experience with it is positive. We started W2ksp2.exe from the SP2 CD. After accepting the license agreement and choosing to back up system files before applying the service pack, the process was completely hands free, if a bit time-consuming. After rebooting, we noticed no significant changes, per Microsoft's commitment not to add new features via service packs.
We heard rumors of some problems with SP2, so we headed straight for the alleged hot spots. But we didn't have any trouble connecting to the network or the Internet, and all of our devices worked properly. Having used SP2 for some time, we can report no problems with stability. Our overall impression is that SP2 manages to swat many bugs while causing little residual havoc.
SP2 contains fixes for a variety of trouble spots:
- Application compatibility
- Base operating system
- Directory services
- Internet Information Services/COM+
- Management and administration
- Microsoft Data Access Components (MDAC)
- Microsoft Message Queuing (MSMQ)
- Networking
- Printing
- Security
- Setup
- Shell
- Terminal services
Most of the fixes are for the base operating system, directory services, networking, and security.
 | |
| |
| |
|
1. Intro
2. Start it up 3. Slug some bugs |
4. First, do no harm
5. Ever more secure 6. Not quite perfect |
| |
| |
