I have a Win server 2003 R2 machine that runs some tasks for my company. It is a pretty antiquated task system that often brings errors. Once the error occurs I have to manually restart the machine before the task will start running again (it is not a windows task in case you are wondering).
The obvious best choice is to fix what is causing the error so it does not happening. but my programmers have a big backlog and can;t get to it right now.
Since rebooting the server always fixes the issue, I have set a windows task to reboot the server every few hours. that way, even if I fail to manually check on the server, if it has an error, it will just fix itself by rebooting.
However, this will cause the server to reboot 5-6 times per day. Can anyone think of why this may be inherently bad for the hardware to reboot that many times per day?