Get Logged On Users

BatchPatch Forums Home › Forums › BatchPatch Support Forum › Get Logged On Users

Tagged: 

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • February 20, 2020 at 2:43 pm #12235
    doug
    Moderator

    The ‘NO OWNER’ result is obviously misleading/confusing. We’ll fix the language in the next release. However, essentially it means that BP was not able to successfully determine the logged on user, which it does by querying process ownership of explorer.exe. We actually have not ever seen this happen before in practice, but when the code returns “NO OWNER” it is because when BP queried the target computer’s OS for information, the returned info was empty/inaccessible/invalid. The likely reasons it could occur are, in no particular order:

    1. Insufficient permissions to target computer
    2. WMI corruption/error/failure on target computer
    3. Memory issue on target computer, possibly/probably with WMI service
    4. Other/unknown issue

    If rebooting the target fixes the issue, then the cause is probably 2 or 3. You could also check the event log on the target and see if it has any relevant/helpful info, though I wouldn’t be surprised if it doesn’t.

    -Doug

    February 20, 2020 at 3:47 pm #12236
    jomich18
    Participant

    Hi doug,

    1. I have admin rights on the computers
    2. Same output after restart

    Regedit is disable, does that affect the output?

    February 20, 2020 at 4:15 pm #12237
    doug
    Moderator

    I can’t see a reason why disabling regedit would have any impact. I just tried disabling it via GPO but it didn’t seem to impact anything in my test lab. Still worked fine without issue.

    I’m not sure what could be causing your issue (aside from the guesses in my previous message). At this time the ‘Get logged on users’ method in BP does not attempt to provide further detail about the error. What I can tell you though is no one has ever reported this before, and we have never seen it occur here, so it’s definitely unusual in that regard.

    In the next version of BP we’ll plan to print out the failure/error code or message text, which maybe will help point you in the right direction here for what’s going wrong.

    February 20, 2020 at 4:52 pm #12238
    jomich18
    Participant

    Thanks Doug.
    Any recommended script to output only the Username of the Logged on user via Execute Remote Process/Command?

    Already tried “query user” and it get the correct Logged on user on the computer

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.