Make sure you have the correct password of the user account and that this password is not expired.Make sure the user account you submitted as scanning credential in Lansweeper has administrative privileges on the client machine.You can rescan one or more machines by clicking the Assets link at the top of the web console, ticking the checkboxes in front of the assets and hitting the Rescan button on the left. If the scanning error is not recent, rescan the computer first to verify whether the scanning issue is still present.Look at the Last Tried (= last scan attempt) date in the computer's Summary tab to determine when the scanning error occurred.Make sure the client machine's OS is fully patched, as some old Windows builds had issues with remote WMI access.Non-Home editions of Windows can be scanned remotely without issue. Older versions of Windows Home operating systems cannot be scanned remotely and will need to be scanned with LsAgent or LsPush anyway. Make sure the client machine is running a non-Home edition of Windows.If a Windows computer is generating an "access denied" error, do the following: These errors are usually caused by your scanning credential lacking administrative privileges on the client machine, but can be caused by incorrect DCOM or other settings as well. When scanning Windows computers without a scanning agent, you may at some point encounter machines that return "access denied" scanning errors. Lansweeper pulls Windows computer data from WMI (Windows Management Instrumentation), a management infrastructure built into Windows operating systems. To successfully perform an agentless scan with RequireIntegrityActivationAuthenticationLevel set to 1, KB5005033 or newer must be installed.
0 kommentar(er)
