Much of what Lansweeper does is WMI based. I suppose the difference in my situation is that it could have fallen back to the global credential (domain based) if the local failed, however I have no indication as such that the local failed. There are various types of credentials: AirWatch credentials (added in Lansweeper 7. I just tried storing credentials using the same format and it was successful. Creating scanning credentials To create a credential, hit the Add new Credential button in the Scanning\Scanning Credentials section of the web console. I've double-checked that the local account is indeed an admin and it is.
Looking in the Event Viewer on the destination PC, I see an Audit Success event that shows the same security ID as the new scanning credential. It shows "Scan in Progress", but ends about 10 seconds in and I see "Access Denied" in the Errors tab. I've created a new scanning credential, with a Type of "Windows", and the Login as ".\" I then mapped this credential to one of these Windows 10 PCs and did a Rescan Asset command. Each of these PCs has a local account that is a local Administrator. They use the same IP subnet and also use our internal DNS for lookups. In addition, the local firewalls are turned off. Perform the test from your Lansweeper server to the device, submit your SNMP credential and show us the entire test window. We have added several Windows 10 Pro PC's to our network, but they are NOT joined to the domain. Screenshot of a connection test performed to the same Cisco device with devicetester.exe, which can be found in Program Files (x86)\Lansweeper\Actions on your Lansweeper server. If you reach your limit, scanning of new and existing assets stops until you delete some. Running Lansweeper v8.4.010.8 from a server joined to our domain. Make sure you havent reached your Lansweeper licenses asset limit.
0 kommentar(er)
