You receive the error, "SMBv1 server check failed" when running a Computer Details scan or any Scan Profile that uses the Computer Details scanner.
If you run one or both of the following commands in an elevated PowerShell prompt on the target computer experiencing the error, you may also receive an error:
Invoke-CimMethod -Namespace root/Microsoft/Windows/SMB -ClassName MSFT_SmbServerConfiguration -MethodName GetConfiguration
This error is most likely caused by a SMBv1 server setting in the registry that is either:
- Containing non-standard data
The key/value is probably located in HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters (though the problem can exist elsewhere in the LanmanServer key or even in a different registry location)
Check any GPO or other script that could make changes to the registry. To resolve the issue, correct the registry and attempt the scan again. The Event Viewer may have additional information about the issue after running
One customer had the DisableStrictNameChecking value set in HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters, which caused the scanner to fail.
See this TechNet thread for another example.