cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
sqldba01
Engaged Sweeper III

Need a report with warranty status by department.  I'd like to have department based off of the last logged on 'user' field and then drill into the AD user information to pull their department or manager or something to help inform managers and facilitate budgeting. I know last logged on is not always the owner or user. Thanks for any help.

2 ACCEPTED SOLUTIONS
Tim_N
Lansweeper Employee
Lansweeper Employee

Hello @sqldba01 

In order to track every user that logs onto a system, you'll need to use LsPush. Introduction to the LsPush scanning agent for Windows (lansweeper.com)

LsPush is a script-based "agent" that must be ran through a GPO, scheduled task, logon script, etc. This is an important tool to use if you'd like to have more frequent scans based on specific triggers. 

See if this helps you provide the details on each user as you are looking for. 

Tim N.
Lansweeper Employee

View solution in original post

sqldba01
Engaged Sweeper III

I did get a good report for windows warranty devices out of date. But, instead we decided to use more simple reports we built exposing devices 4/5 years or older. Assumed the last logged on is the owner/user (mostly correct) and then used AD info on the user to find the department responsible for budgeting the new equipment.  Confident it could us some CSI but here ya go for four or more years old: Select Distinct Top (100000) tblAssets.AssetID,
tblAssets.AssetName,
tblAssets.Username As AssetUserName,
tblADUsers.Name As ADUserName,
tblADUsers.Department,
tblWarranty.ShipDate As Purchased,
tblAssets.Domain,
tsysAssetTypes.AssetTypename As Type,
tblAssets.IPAddress,
tblAssetCustom.Manufacturer,
tblAssetCustom.Model,
tblAssets.Lastseen As [Last successful scan]
From tblWarranty
Inner Join tblWarrantyDetails On tblWarranty.WarrantyId =
tblWarrantyDetails.WarrantyId
Inner Join tblAssets On tblWarranty.AssetId = tblAssets.AssetID
Inner Join tsysAssetTypes On tblAssets.Assettype = tsysAssetTypes.AssetType
Inner Join tblAssetCustom On tblAssets.AssetID = tblAssetCustom.AssetID
Inner Join tblADUsers On tblAssets.Username = tblADUsers.Username
Left Outer Join tsysIPLocations On tblAssets.LocationID =
tsysIPLocations.LocationID
Where tblWarranty.ShipDate < GetDate() - 1460 And tsysAssetTypes.AssetTypename =
'Windows' And tblWarrantyDetails.ServiceType Like '%prosupport%'
Order By tblADUsers.Department,
Purchased

View solution in original post

5 REPLIES 5
sqldba01
Engaged Sweeper III

Tim_N, 

We do not use LSPush yet. But, would this not simply show the last logged on user vs a history of logins, or a field with most frequent login (or actual owner/user) which would allow a report on the user in AD leading to the department responsible for the device nearing end of warranty for notification and budgeting purposes. Thanks again.

Tim_N
Lansweeper Employee
Lansweeper Employee

Hello @sqldba01 -- sorry for my slow response; I was traveling for work and had a little time off. 

LsPush will do a scan of the asset but does not track history in itself. So, you are correct, an LsPush scan will only show you the recently logged in user. For the history of logged in users, that will be tracked inside Lansweeper. 

I hope that answers the question with a little more clarity. 

Tim N.
Lansweeper Employee
Tim_N
Lansweeper Employee
Lansweeper Employee

Hello @sqldba01 

In order to track every user that logs onto a system, you'll need to use LsPush. Introduction to the LsPush scanning agent for Windows (lansweeper.com)

LsPush is a script-based "agent" that must be ran through a GPO, scheduled task, logon script, etc. This is an important tool to use if you'd like to have more frequent scans based on specific triggers. 

See if this helps you provide the details on each user as you are looking for. 

Tim N.
Lansweeper Employee
sqldba01
Engaged Sweeper III

I did get a good report for windows warranty devices out of date. But, instead we decided to use more simple reports we built exposing devices 4/5 years or older. Assumed the last logged on is the owner/user (mostly correct) and then used AD info on the user to find the department responsible for budgeting the new equipment.  Confident it could us some CSI but here ya go for four or more years old: Select Distinct Top (100000) tblAssets.AssetID,
tblAssets.AssetName,
tblAssets.Username As AssetUserName,
tblADUsers.Name As ADUserName,
tblADUsers.Department,
tblWarranty.ShipDate As Purchased,
tblAssets.Domain,
tsysAssetTypes.AssetTypename As Type,
tblAssets.IPAddress,
tblAssetCustom.Manufacturer,
tblAssetCustom.Model,
tblAssets.Lastseen As [Last successful scan]
From tblWarranty
Inner Join tblWarrantyDetails On tblWarranty.WarrantyId =
tblWarrantyDetails.WarrantyId
Inner Join tblAssets On tblWarranty.AssetId = tblAssets.AssetID
Inner Join tsysAssetTypes On tblAssets.Assettype = tsysAssetTypes.AssetType
Inner Join tblAssetCustom On tblAssets.AssetID = tblAssetCustom.AssetID
Inner Join tblADUsers On tblAssets.Username = tblADUsers.Username
Left Outer Join tsysIPLocations On tblAssets.LocationID =
tsysIPLocations.LocationID
Where tblWarranty.ShipDate < GetDate() - 1460 And tsysAssetTypes.AssetTypename =
'Windows' And tblWarrantyDetails.ServiceType Like '%prosupport%'
Order By tblADUsers.Department,
Purchased

sqldba01
Engaged Sweeper III

To clarify, LS does NOT keep a history of logins as Tim_N mentioned; only the last logged on. I made a product request some time ago to develop the potential to reflect last and most logged on. Several more fields in the table to move last logged on into those fields so you can report on most frequently logged on of the last maybe 3 times would be enough to eliminate the sporadic SD or support logon vs a real user. 

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now