This post originated from an RSS feed registered with .NET Buzz by Greg Reinacker. Original Post: Windows 2003 Server default settings Feed Title: Greg Reinacker's Weblog Feed URL: http://sedoparking.com/search/registrar.php?domain=®istrar=sedopark Feed Description: Greg Reinacker's Weblog Latest .NET Buzz Posts Latest .NET Buzz Posts by Greg Reinacker Latest Posts From Greg Reinacker's Weblog

Dave Burke isn't happy with Windows 2003 Server's default security settings:

[...] But at the end of the flying day or computing day, what has changed?  Really?  As a developer (or flyer), there is just more crap to do to get to where you want to go.  But at the end of the day you still end up at the same place.

I'm sure lots of folks want to ream me for dissing the new W2K3 security features.  I'm in no position to question the array of security restrictions in W2K3.  Smarter guys than me thought they were a good idea.  Hey, I'm just saying that to me, using W2K3 is like post 9/11 Airport Security.

Windows 2000 was like buying a big new house, moving in, and seeing that all the doors and windows are unlocked and open. You have to remember to go around the house and close/lock them, assuming that you care if anyone breaks in.

Windows 2003 is a similar house, albeit with stronger doors and more tamper-resistant locks...but when you move in, all the doors and windows are locked - and you can open what you wish.

Seems like an easy choice to me.