Best Practices Analyzer: Srv.sys should be set to start on demand
This article is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this article to computers on which Best Practices Analyzer scans have been run, and that are experiencing the issue addressed by this article. This article can also be useful as general troubleshooting and best practices information to help you configure your server. For more information about best practices and scans, see Run Best Practices Analyzer Scans and Manage Scan Results.
If you think that something in this article is missing or could use improvement, we encourage you to add or edit content that addresses this specific issue. Instructions for editing a TechNet Wiki article are available at Wiki: How to Use the Editor.
Operating System |
Windows Server 2012 |
Product/Feature |
File and Storage Services |
Severity |
Informational |
Category |
Configuration |
Issue
Srv.sys is not set to start on demand.
Impact
Client computers will not be able to access file shares and other Server Message Block (SMB)-based network services on this computer.
Resolution
NOTE: This BPA message is erroneously produced when the SMB 1.0 feature has been removed from Windows Server 2012. SMB 1.0 is required for older clients, such as Windows XP.
Set Srv.sys to start on demand.
This can be achieved by running the following command from an elevated command prompt:
sc config srv start=demand
Or through the Powershell way:
Get-CimInstance -ClassName CIM_Service -Filter "Name='srv'" |Invoke-CimMethod -MethodName ChangeStartMode -Arguments @{StartMode='Manual'}