Microsoft Releases Windows Server 2003 SP1
Masq666 writes "Microsoft has wrapped up development on the first major update to its Windows Server 2003 operating system and released it for download, The company said that Windows Server 2003 Service Pack 1 is currently available for download via Microsoft's site and will soon start showing up on new servers. Among the primary benefits of the free update is the inclusion of security enhancements similar to those added to Windows XP with last year's Service Pack 2. News.com.com has more details and commentary."
</sarcasm>
Ok, I have used Windows for development in 95 and 98 releases and now use OS X very happily. What surprises me is we are in late March of 2005 and Windows 2003 SP***1*** is being released.
--- Old Time NeXThead
Ok, you are basically throwing up the red flag saying, "I don't have a legitimate install of Windows 2003 Server, so I want to know if I can update my server without getting in trouble". To answer that, I say take your chances, because my company has ligitimate copies, so I don't have to worry about if it will let me update or not.
-----BEGIN PGP SIGNATURE-----
12345
-----END PGP SIGNATURE-----
File Name: WindowsServer2003-KB889101-SP1-x86-ENU.exeo ad Size: 337230 KB
Downl
Date Published: 3/30/2005
Version: SP1
Even without specifics, it blows me away that a service pack is almost 330MB. How can you explain something like that? If it's supposedly not insecure, and that much of an improvement over W2K Server, yet still requires fixes to the tune of half the size of the original install CD... then what am I suppsed to think?
Honestly. Can anyone give a legit reason why this is acceptable?
I'm against picketing, but I don't know how to show it.
1) They are easy to crack remotely with default installs.
2) Weekly if not daily patches are required.
So, Microsoft comes out with SP1 and people are already whining.
1) What is the "no inbound connections by default" stuff going to help?
2) The length of time between Windows 2003's release and its first service pack.
C'mon people, put it together.
The open-source world must scare you shitless then. A lot of those projects have a release-of-the-day or release-of-the-week...
I had a pranoid thought the other day. It seems that the MS policy for supporting products runs for about 5 years. Support for 2K pro was dropped earlier this year. XP was first released in May 2001, longhorn May 2006. Is this the forthcoming strategy for the forced upgrades the we all know and love?
Our diversity is our strength
Hey, why aren't they rolling out a paired down version of Security Configuration Wizard (SCW) for XP?
The "Security Center" on XP is pretty cheesy, didn't even include an updated MBSA until a couple months after XP sp2 was released. Most folks won't dig into using the Local Security Policy snap-in or Security Configuration and Analysis snap-in, or fiddle with changing their template.
"I'm really at a loss of words to describe this brilliance.
Just think of it, closing all open ports from incoming traffic by default now. Wow. Why didn't anyone else come up with this great idea before?"
It's not what you're thinking of - I don't think you're getting it. This isn't a firewall that gets turned on. Rather, the user can't do anything on the network until the system is up-to-date. It basically sandboxes the user from all internet traffic but the update site. I don't know of a single other OS that does this.
Among the primary benefits of the free update is the inclusion of security enhancements similar to those added to Windows XP with last year's Service Pack 2.
YES! I bet W2k3 server sysadmins will just love the new security features of XP like that great firewall. You know... the one that blocks local ICMP pings by default!
Are you kidding? 2k3 server makes for a far better desktop than XP. All the annoying crap is off by default.
No bubbly playskool theme. No MSN Messenger popups. No product activation. No "take the tour!". No windows media player intruding into everything. IE is crippled by default -- ripe for Firefox installation.
It feels a lot more like if you took 2000 Pro and added the few GOOD things about XP.
That's not always true. A wizard that quickly macros something you were going to do anyways sounds like a great idea.
First new and improved script-kiddie exploits available in 3...2..1...
Keep that argument going, but the reality is that Windows Server 2003 has been the most secure Microsoft offering to date (I know I know - that isn't saying much).
Through a minimalist initial setup, to a wide variety of security improvements in things like the way IIS 6 operates, Windows Server 2003 has fallen prey to very, very few exploits. I think the fact that the first service pack took two years to hit the market, and much of it is additional functionality or tweaking (rather than actual fixes), really says a lot for the quality of the product.
I guess my point, if I have one, is that while the anti-M$ hoardes continue the security mantra as if it was 1999, Windows Server 2003 is really an excellent, secure product. I think the mininions need to evolve their FUD.
Actually... there are a lot of Sys Admins that still will not even think about upgrading their server OS until SP1 comes out.