The Setup Behind Microsoft.com

Toreo asesino writes "Jeff Alexander gives an insight into how Microsoft runs its main sites. Interesting details include having no firewall, having to manage 650 GB of IIS logs every day, and the use of their yet unreleased Windows Server 2008 in a production environment.

Comments

Supporting

[kripkenstein]

The highly objective and insightful article mentions, for example,

Windows and IIS...rock solid and secure!

Way to go with supporting the troops there.

You ARE a m$ fanboy!

[mangu]

He's a tard for using a "full featured word processor" for a "simple find and replace"

Two points you and the other fanboys are missing: (1) there IS no text editor for "a simple find and replace" in a default micro$oft system, and (2) full featured text editors in Linux do NOT load the whole file in memory before opening it.

Idiots. Typical micro$oft shills.

Typical Microsoft

[Bryansix]

You realize that Win2k3 does turn off most services by default, and Win2k8 takes this even further by not installing them at all.

Why does Microsoft not install them at all? Could it be because in their default state they are insecure? I don't want them to not be installed. (btw, Server 2003 does this too just with less services) I want them all installed and all turned off. Then I want the default state of the services to be secure when I do enable them. If this means making a wizard to set up the damn service then so be it. Why does Microsoft always assume that everybody using their products is all of the sudden going to have some magical knowledge of all the attributes that define said program? Why don't they make services as easy to configure in a secure manner as Microsoft Word is to use?

Re:Beta in production environment.

[goodtim]

Dear LordSkippy,

You're fired.

Kindest Regards,
Your Boss

P.S. Please learn the difference between a server and a workstation before applying for a job in the IT department.