Why do registry keys that I monitor return "*Absent* - Data not found" for Windows 7 and Windows XP 64bit assets even though that registry key exists and has a value on the machine?
The "Remote Registry" service on these machines are enabled.
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?
Even if only one of these keys gets populated with the correct data, then I would be happy but on some machines both has an "Absent" entry and on some machines one has an empty entry.
Attached are screen shots for Xp 64bit and Windows 7 64bit. I have checked both machines' registry and found valid data in at least one of those registry values.
The XP 32bit and Windows 7 32bit machines do get populated correctly with one of those keys.
BTW: these assets all have 7.5.05 agents on them
Filename
XP_64bit.JPG
Description
Filesize
21 Kbytes
Downloaded:
3 time(s)
Filename
Win7_64bit.JPG
Description
Filesize
22 Kbytes
Downloaded:
2 time(s)
This message was edited 11 times. Last update was at 11/02/2011 01:05:46
I think the key you are looking for on 64bit Windows is possibly HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultUserName
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
I just tried to gather that exact same information. I tried using the reg key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\LastLoggedOnUser
and received the same *Absent* - Data not found result for a Win7 64-bit system. Did you get any follow-up answers from SysAid Support?
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.
SysAid Technologies Ltd.
Toll-Free phone center (U.S.): 1-800-686-7047
Offices - U.S.617-231-0124
Israel:+972-3-533-3675
Email:helpdesk@sysaid.com
Optimized by SEO Israel
SysAid logos and other SysAid Technologies marks
are trademarks or registered trademarks of
SysAid Technologies Ltd.
All Rights Reserved by SysAid Technologies Ltd.
2002-2011
Live Support Hours
07:00 AM - 09:30 PM (UK)
03:00 AM - 05:30 PM (EDT)
We provide worldwide services, and we do our best
to match the working times of customers from
different time zones.
SysAid Help Desk Software and Asset Management Software