When assigning the creds, are you hardcoding the domain or did you try to leverage a local admin account? I see that you stated domain\computername but I'm curious. In some instances, we're leveraging a local admin account via .\user instead of pcname\user .
I have also leveraged domain creds with the full email for an admin perm account (Ex. firstname.lastname@example.org). Do to Group Policies issues in our env, we've had to leverage both.
I could just be being nosy atm but, thoughts/opinions?
Global scanning credentials are only used when no other credentials are mapped to a specific target though, or when all other credentials fail. So, in effect, global scanning credentials will not be used if your credentials are fully and correctly mapped, so global scanning credentials are the fallback credentials. For more information on mapping scanning credentials, you can check this article: https://www.lansweeper.com/knowledgebase/creating-and-mapping-scanning-credentials/
*Oh, sorry, I used 'failback' insteed 'fallback'
Thanks for explanation.
More info about my situation.
We don't use domain admins accounts - we use special domain accounts for servers and workstations. LS allow set credentials for Windows only per computer or workgroup/domain. So we used IP-range mapping and I think before LS 10.5 (but it's not certain) IP-range mapping works for Windows computers too. But now it doesn't work.
May be it is 'by design'. In such way you have to add per-OU credentials mapping.
If we understand your setup correctly, Lansweeper will only use the credentials mapped to the domain, and there is no fallback to any IP range scanning mappings if the domain credentials fail. If these assets would be exclusively scanned via IP range scanning targets and not covered by your AD scanning targets, then Lansweeper should use the IP range mappings you have set up, but this might be a cumbersome setup to maintain.