Er... what got hacked exactly? There's a big difference between IIS being hacked and YOUR OWN application running on IIS getting hacked.

IIS 7 (and even 6) is locked down very tight by default, and unless you open up specific features with attack vectors it's going to be VERY, VERY difficult to hack IIS. In fact the service record of IIS 7 for vulnerabilities has been much better than any of the *nix servers available.

+++ Rick ---

>>1. IIS is an attack target
>>2.I might need to reboot the scheduler
>>3.I need to fiddle around on the scheduler and run apps to see why they hang, etc.
>>
>>Anybody?
>
>>If it wouldn't be for those reasons, it would then be a question of evaluating the workload. If it fits OK, than, yes, one box would do it.
>
>>Af far as point 1, if I would stop all my decision on it, I wouldn't have installed all those servers. lol If the server is well installed, a proper firewall, good >security verifications, point 1 should not be a factor.
>
>Sorry I have to disagree. We installed a sonicwall, had everything turned off but we still got hacked. Lucky the sonicwall reported the hack almost immediately and everything was shutdown. Real question in my mind why! There is nothing that the client does (no credit cards, just manufacturing data) that was even worth the time.
>
>Johnf