I understand that a user must log into a system for it to be populated with data from AD. I have a situation in my new implementation of 4.0 where many of my user accounts are not even findable within lansweeper, but when viewing their computers directly I can see that the user account is shown in the user logon history for that machine.
The account that is shown as the currently logged on user is an auto update service account that is another internal service account. <-this is annoying but probably something on our end.
The part that doesn't seem to be on our end is that the users are logged on and have been detected as logged on in that history, so shouldn't Lansweeper find and scan their user accounts from AD?
When I try to search for the affected user names nothing is found - which also means that all the user OU reports are incomplete.
I have tried a trigger scan, full rescan, and rescan on a few affected machines. (I also later upgraded to the new beta version today and tried that.)
We have a logon script that runs when any domain user logs on. The old 3.5 implementation doesn't seem to have this problem.
Any ideas?