• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4899
  • Last Modified:

Srv.sys should be running. Srv.sys should be set to start on demand.

Hello,

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.
0
fakaul
Asked:
fakaul
  • 2
1 Solution
 
Ayman BakrSenior ConsultantCommented:
I believe srv.sys is important as a service for various functions and that the BPA advise to change it to demand is just a misleading information. I think this started with Windows 2012 R2 - isn't it?
0
 
fakaulAuthor Commented:
I believe so.  I have run in to serveral articles confirming that start=demand is the "desired" setting.  But it does not work on my server.  I must use start=auto for things to work.
0
 
Ayman BakrSenior ConsultantCommented:
I think start=auto should be fine and do you no harm, however you can follow up with Microsoft to see if they have a fix to this discrepancy between BPA advise and the 'want' of your server/services!
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now