
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-30-2010 10:14 PM
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?
- Labels:
-
Archive

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-09-2011 12:40 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-09-2011 12:07 PM
in order not to open new topic, I will ask here.
Is this changed maybe?
I also have users which are logging on to computers regularly, but I don't see them in User OU overview?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-07-2010 03:25 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-01-2010 07:57 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-01-2010 07:40 PM
You will be able to select user OU's to synchronize each night.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-01-2010 07:16 PM
Is there going to be a "scan all users from AD" option any time soon to remedy this for the Lansweeper admins like me who have scripted services that run as an alternate user on login?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-01-2010 07:09 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-01-2010 11:42 AM
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 the cause of the problem, only the last logged on user is scanned from active directory.
What is the name for this software, we will try to reproduce it.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-01-2010 06:37 PM
Lansweeper wrote:only the last logged on user is scanned from active directory.
This makes sense, but why would it also show the actual user logon in the past in the history list, but not have scanned the user account? Is that pulling from somewhere else than the "last logged on user"?
I attached a screenshot showing that two user accounts are found on each scan, but only the "auto update service" is findable in the search bar or user OU breakdown.
Thanks!
