Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Determine the last logged on user

Determine the last logged on user

Table of contents

Updated January 26, 2017

Overview

Assett inventory, when SAM is installed, attempts to find out the last user to log on to a given Windows node. In some cases, the information in Orion may seem wrong. This is an advice for making the initial determination as to whether Orion is getting the value presented by the Windows node, or if our value is incorrect for some reason.

Environment

  • All SAM versions
  • Any Windows node with WMI

Detail

SAM gets that value from the registry on the node; check the key/value below and compare it to the most recently polled value in Orion:

Key: HkeyLocalMachine\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI

Value: LastLoggedOnUser

Type

REG_SZ

 

If the values match, contact Microsoft support or your local admin to see if they can determine why the incorrect value is being presented.

If it does not a match, contact Solarwinds Technical support for deeper troubleshooting.

 

Last modified

Tags

Classifications

Public