>I'd prefer to have a separate server as my IIS server for Intranet apps and a separate server running Scheduled tasks that run a lot of FoxPro apps.
>
>But, the IT people want to save something (we're a total blade virtual environment) and install both on one server.
>
>I just feel that it is not a good practice because:
>
>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?

My big question would be: what kind of workload do these scheduled tasks have? How long do they run? VFP will happily steal 100% of the CPU (so on a single CPU box your website will come to a crawl). If it's only running for a few seconds once an hour, that's not a big deal. But longer running processes might be. On a multi-CPU box it's not a big deal unless it's a heavily loaded box and is already CPU bound.

But if they're already running a virtualize blade server set-up, it seems like it would be easy enough to let you run the jobs on another box (even if it's shared with other things) besides the webserver. At one place I was at we had one machine dedicated for everyone's automated tasks. But it was regularly hitting 50% CPU usage all of the time because of all of the jobs running.