When attempting to scan a Windows 10 version 1607 (aka the Windows 10 Anniversary Update) system or a Windows Sever 2016 Desktop Experience that is part of a Workgroup from a Domain system you receive the error "201: System not found" despite being able to resolve and connect to the machine through other means such as:
- DNS resolution: nslookup machinename resolves correct IP
- Admin share access: net use \\machinename\IPC$ succeeds
- Remote registry connection: Able to connect to the machine from Regedit by going to File > Connect Network Registry...
When checked, the ST.Protect.managed log, located at C:\ProgramData\LANDESK\Shavlik Protect\Logs, will have an error similar to the following:
2017-01-27T19:57:55.5249309Z 0020 W NativeMethods.cs:233|DsRoleGetPrimaryDomainInformation for '10.25.87.55' failed: 2.
2017-01-27T19:57:55.5249309Z 0020 W ResolvableMachineWorkflow.cs:273| 10.25.87.55 The system cannot find the file specified
This is a known problem with the Microsoft's DsRoleGetPrimaryDomainInformation call, which is used by Shavlik Protect, as seen in the following MSDN post: Known Issue: DsRoleGetPrimaryDomainInformation returns an Error 2 - ERROR_FILE_NOT_FOUND even though the call was succes…
This problem has been resolved with the release of Ivanti Patch for Windows Servers 9.3. Until you can upgrade, there are a couple of options to work around it:
- Adding the machine to your domain will allow it to be scanned normally
- Installing an agent on the machine will bypass the problematic call
a. Information on agents can be found here: Protect Agent Information and Troubleshooting
Shavlik Protect 9.2.x