-
1. Re: WEI value in inventory for EUC machines
francesco.baldini May 27, 2014 8:04 AM (in response to chetantv)Hi there Chetan,
The WEI data is stored in several XML files in the following path:
%systemroot%\Performance\WinSAT\DataStore
The files are named according to the date and time the Windows System Assessment Tool has been started, but if you manage to reduce the files you're interested in to a static nomenclature, you can then add their content to the LANDESK inventory according to the instructions of this article:
How to scan for the contents of a text file and return it with Inventory.
http://community.landesk.com/support/docs/DOC-2400
Hope this helps
Francesco
-
2. Re: WEI value in inventory for EUC machines
chetantv May 27, 2014 8:30 AM (in response to francesco.baldini)Hi,
Thanks for the information .
So this will add the entire content of the file to inventory or i can pick whichever data is required ?
Regards,
Chetan.T.V
-
3. Re: WEI value in inventory for EUC machines
chetantv May 28, 2014 4:36 AM (in response to chetantv)Also,
The xml files you are referring will have file names based on the date it ran so its not possible to have a query for that eventually.
Any other way? Any WMI path you know to record this data?
-
4. Re: WEI value in inventory for EUC machines
francesco.baldini May 28, 2014 6:09 AM (in response to chetantv)Hi again,
Yes the files are named according to the date and time the assessment tool has been run, that's why I was warning you about the need to change the file naming to a more static nomenclature.
Unfortunately, as far as I know, that's how windows save this data. But for instance, if you have just one file you are interested in, let's say for intsance the Formal.Assessment (Here is why you would: http://www.howtogeek.com/71500/stupid-geek-tricks-hacking-the-windows-experience-index )
C:\Windows\Performance\WinSAT\DataStore>dir
Volume in drive C is OS
Volume Serial Number is 08C9-1A4A
Directory of C:\Windows\Performance\WinSAT\DataStore
03/07/2013 08:52 <DIR> .
03/07/2013 08:52 <DIR> ..
21/05/2013 22:31 10,456 2013-05-21 22.31.42.874 DWM.Assessment (Initial).WinSAT.xml
03/07/2013 08:52 122,880 2013-07-03 08.49.15.318.winsat.etl
03/07/2013 08:52 45,358 2013-07-03 08.49.17.584 Cpu.Assessment (Initial).WinSAT.xml
03/07/2013 08:52 51,294 2013-07-03 08.49.17.584 Disk.Assessment (Initial).WinSAT.xml
03/07/2013 08:52 42,318 2013-07-03 08.49.17.584 Graphics3D.Assessment (Initial).WinSAT.xml
03/07/2013 08:52 19,204 2013-07-03 08.49.17.584 GraphicsMedia.Assessment (Initial).WinSAT.xml
03/07/2013 08:52 9,690 2013-07-03 08.49.17.584 Mem.Assessment (Initial).WinSAT.xml
03/07/2013 08:52 146,420 2013-07-03 08.52.36.624 Formal.Assessment (Initial).WinSAT.xml
8 File(s) 447,620 bytes
2 Dir(s) 419,166,564,352 bytes free
You could rename the file easily with a ren command like this:
C:\Windows\Performance\WinSAT\DataStore>ren *formal.assessment* Formal.Assessment.xml
Then again, if you want to query the content you are retrieving, you need to use custom data, which means registry keys:
http://community.landesk.com/support/docs/DOC-1089Using the previous method won't allow you to query the gathered content:
http://community.landesk.com/support/docs/DOC-2400
So in this case the complete process would be:
- Script the normalization of the file names you want to retrieve information from
- Parse the files content to extract the information you need
- Merge the extracted content into the machine's registry
- Set up inventory custom data to add those registry keys into the LANDESK databaseHope this helps
Francesco
-
5. Re: WEI value in inventory for EUC machines
chetantv Jun 3, 2014 7:00 AM (in response to francesco.baldini)Hi All,
Thanks for the information and helped me to think in different ways
However, i managed to them on Custom Data without modifying any files.
In WMI Info section of LdAppl3 included the winsatconfig.exe to run and extract the information from WMI and was able to these information handy and wrote query for the same.
Cheers
-
6. Re: WEI value in inventory for EUC machines
Rick.Smith1 Jun 23, 2014 1:30 PM (in response to chetantv)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.