Is this happening on Windows 7 and Windows XP 64bit assets only?
Can you please upload screenshots of the settings you have made under Preferences > Asset Settings and of the "*Absent* - Data not found" message you are getting?
As I said in my previous post; "I have checked both machines' registry and found valid data in at least one of those registry values" so the data is there and I will be happy if I only get one of these values populated by data
I have check a lot of machines that get the Absent Data and they all had proper data in their registries for at least one of these values
This message was edited 2 times. Last update was at 17/02/2011 00:07:19
So with MUCH time spent with support over the last few months, we seem to be getting closer to a cause for this. It seems that when you tell SysAid to look at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\LastLoggedOnUser it is actually looking at HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\LastLoggedOnUser.
Because LastLoggedOnUser does not exist in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Authentication\LogonUI it returns *Absent* - Data not found.
We tested this by manually creating the key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\LastLoggedOnUser and assigning a value to it. We then told SysAid to look at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\LastLoggedOnUser. It returned the value from the Wow6432Node key.
So now the question is Why is SysAid looking in Wow6432Node, instead of where we are telling it? It may have to do with the fact that the SysAid agent is a 32-Bit agent. I'm told the the new 9.x agent will have both a 32-bit and 64-bit version.