Has anyone else seen users last logon dates in invalid formates like in my screen-shot below? If so, you might know of an explanation? I have contacted support, but I was curioes as to whether some of you might have come across such an issue also?
Haven't seen that one before... What does the users logon history look like if you look at it in Snow Inventory?
I don't think we have any user details in the Inventory as we 'only' get our user data from when they log on to machines. Or am I misunderstanding your question?
The data in your screenshot (list of all users) comes from what Snow Inventory has for each computer. Snow Inventory in turn gets the inventory from either Snow Inventory agents, SCCM, or something else.
So I'm wondering what the user login data looks like in Snow Inventory - does it have the same incorrect format? Well then it can be traced back to the inventory source, so you have located where the erroneous data comes from.
Haven't noticed that before, but checked this after your question and found some less users with an invalid last logon date in the future. But only around 30 users.
I assume the computers they logged on, had a wrong date at that time.
And because they now already have a "newer" logon date in SLM, that last logon date will not be updated any more.
I will remove some of that users and see how they will appear again.
That is a good idea Carola - I'll try that with one of mine also.
The 1 user I tried to delete now shows up correctly again. That's of course good, but not too assuring...
I was not so successful like you were.
The user I deleted, appeared again with a last logon date of 2083.
So I searched in the database and found that last logon information in his computer (tblcomputerusers).
In my case, I will need to remove also that computer and wait for another DUJ.
I do have a couple of errant systems that show the date in the future and show 2018 but yet to find out why.
I had the same issue where a couple of users who had logged on to a server showed as last logging on in 2018.
It turns out that they were using the server for testing an application and had purposefully changed the date for testing.
They still haven't changed it back yet....
That's exactly what I've noticed one day and sent to snow support. Some users suddenly had a "last logon date" which lies in the future. The guess of support was that the system date has changed recently and has been set correctly again. I couldn't really imagine that, but there is nothing that does not exist.
To see if the date will be updated correctly after a new inventory we've set the "last logon date" of all the concerned users back into the past. As if they will be inventoried the next day again.
The following SQL statement has been used:
Set LastLogon = '2016-12-12 09:00:00.000'
where LastLogon > '2018'
Set UpdateTime = '2016-12-12 09:00:00.000'
where UpdateTime > '2018'
Unfortunately the real cause why these "future dates" were discovered is still unknown. And it didn't happen again for those users. BUT what a pitty I just found new entries like this.
I deleted all my 'bad' entries and haven't anything similar happen since, but that's not really a solution... This - the occurence of these dates - might have happened around the time performed our Inventory upgrade, but other than that I have no explanation either.
In our case not. We haven't done any upgrade. Windows Client 3.7.05 has been rolled out on all clients and suddenly there were such entries.
Retrieving data ...