I'm working on this exact same issue, however the solution that should be working isn't. You can pull this information easily via WMI.
The proper method of doing this in LANDesk 9.5 SP2+ (not sure what version you are using) is to follow the information found here:
http://help.landesk.com/Topic/Index/ENU/LDMS/9.5/Content/Windows/inv_t_add_custom_wmi_items.htm
Here are the values you are looking for:
NameSpace: root\CIMv2
ClassName: Win32_WinSAT
Display Object: Windows Performance - WinSAT (or whatever you want your structure to be)
Properties \ Display Name:
CPUScore \ CPU Score
D3DScore \ Gaming Graphics Score (D3DScore)
DiskScore \ Disk Score
MemoryScore \ Memory Score
TimeTaken \ Time Taken
WinSATAssessmentState \ WinSAT Assessment State
WinSPRLevel \ Base Score
One of the tools I use quite often for WMI Query testing is called WMI Code Creator. http://www.microsoft.com/en-us/download/details.aspx?id=8572
The problem I have open with LANDesk right now however is that if I build the custom inventory collection the way the help file says to do so, the first display name appears but with the last record in the list.
So in my example above I am only getting "CPU Score = 5.1" when CPU Score is actually 5.9 and Base Score is actually 5.1. Sadly this seems to be a bug I need LANDesk to fix, but once it's done, it should work just fine.
I did try separating out the WMI data into separate records, but LANDesk started combining them on its own and left empty records. I assuming in some sort of attempt to 'clean up' after a messy admin, but its doing a really poor job of it aside from not working at all to begin with, so it only makes matters worse. Please Fix SOON!
In the mean time, Chetantv, if you could expand on the exact method you used and what "winsatconfig.exe" is and where you got it or how you set it up, that would be of benefit. I'm not finding any references to it. I could easily write a script to take the WMI values and write them to a registry to then collect through Inventory scan that is working, but its not exactly real time and not what I would prefer to be doing.