You can write a batch file, which checks to see if the service is running, and if it isn't, attempts to start it. So do 'net start' from the command line, and find the name for your service.
Then have the batch file perform a:
net start | find /i "[exact name of service found above]"
if errorlevel==1 net start "[exact name of service you want to make certain is running]"

You can then use "Scheduled Tasks" to run the batch file, scheduled to run daily at a time after the server should have recovered from it's reboot. (And if you like, you can use the Advanced Schedule Options to repeatedly run the task... it'll only attempt to start the service if it doesn't find it in the list of running tasks.)

Featured Post

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.
However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…

This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP, Windows Server…

Is your OST file inaccessible, Need to transfer OST file from one computer to another? Want to convert OST file to PST? If the answer to any of the above question is yes, then look no further. With the help of Stellar OST to PST Converter, you can e…