Srv.sys should be running. Srv.sys should be set to start on demand.
Posted on 2014-04-18
My Windows Server 2012 file server stopped receiving faxes via the SMB connection, (although it used to work fine). During my investigation I ran the Best Practices analyzer and was told that Srv.sys should be running. Reasonable enough. After further research I ran the command:
sc config srv start=demand
at an elevated command prompt and confirmed that this command was successful.
I tested the scan to SMB and it still did not work. I ran "sc start srv" to force a start and the scanning worked. After a reboot the scanning no longer worked however and the service was stopped again.
Using sc config srv start=auto seems to have the desire affect, in that the service is running and continues to do so after reboot. But apparently this is not the "Best Practice" since the BPA now advises that it should be set to "demand".
Am wondering why "demand" is preferred to "auto" and why it is not working correctly. No obvious clues in the logs but will dig further.
This is a VM running under ESX 5.1 and running VMware tools.
Expert insight on this issue is solicited.