Hello,
Can you create a report from the following Powershell:
Get-Hotfix | Select PSComputerName, InstalledOn, Description, HotFixID, InstalledBy | Export-Csv -NoType "$Env:userprofile\Desktop\Windows Updates.csv"
This would allow me to select the computers I want to run it on.
Thanks
This is a bit of a weird ask. You want to use a "report" (which is kinda what this will yield) as the scope for another report?
It would help to know what the filter criteria for your ultimate report will be.
Have you looked at the Powershell cmdlets available for Reporter?
With a bit of work, you could actually take the output of your command line and use it to launch a report that you have authored in the GUI.
Some helpful articles:
support.quest.com/.../how-to-add-additional-objects-in-a-discovery-using-powershell-127045
support.quest.com/.../how-to-run-a-report-using-powershell-183312
I would like a report that will show all MS Patches/Hotfixes installed on computers. I can use the above PS but have to login to each computer separately. However, if I had a report, I could select which computers to run on w/o having to login to each computer and run the PS.
A document, Instructions on extending WMI to retrieve info on HotFix info can be found at this link:
www.quest.com/.../262
Two days now and the report is not returning any data.
Have you confirmed that your Discoveries are collecting data OK from the computers you are targeting? - i.e. no errors due to them being offline, access denied, etc.
we always have errors.
Hello,
You are going to have to look closer at the Computer discovery you are using and the collection options. Did you extend the attribute as suggested by Clarence Hemeon? if you are experiencing collection errors it may be best to contact our support team.
Also are you looking for Windows Apps? or just hotfixes and updates?
Thanks,
-Angela
I'm sure you do - but you can drill into the discovery status information and see what specific aspects of the data gathering it had problems with. So for example, maybe it could gather the list of services but not some registry data.
Does the service account you are using have necessary permissions to retrieve on the systems you are collecting the hotfix data from. Is the WMI service running on those systems. If so then you should have a table in your database with data on the hotfixes.
As I said, we've always finished with errors and Yes we have been getting the information we need on reports. This report, however, provides no data.
You created the report. Did you miss a step or forget to include all of the fields for the Win32_QuickFixEngineering as seen on page 13 of the instructions?
The thing is, in order to present the additional piece of data you are looking for, you had to add it to Reporter via Configuration Manager so it would collect it. This data is collected by Reporter connecting to the WMI interface on your machines. This can be problematic as this data source is not always accessible (some people disable WMI via GPOs). So as both I and Angela suggested, you need to take a close look at the discovery results and see if the connection to WMI is failing or not. If it is, than that would explain why this piece of data is not showing up in your reports.
The thing is, in order to present the additional piece of data you are looking for, you had to add it to Reporter via Configuration Manager so it would collect it. This data is collected by Reporter connecting to the WMI interface on your machines. This can be problematic as this data source is not always accessible (some people disable WMI via GPOs). So as both I and Angela suggested, you need to take a close look at the discovery results and see if the connection to WMI is failing or not. If it is, than that would explain why this piece of data is not showing up in your reports.
WMI is working.
I am sorry you are having a problem. Please contact Quest Support for any further assistance.
Yes, we have and the RedHat servers we have are the cause. We "try" to keep them in an exempted OU but are not always successful. On other reports, Quest provided a script/file to run on our SQL database to add the fields. Could this be the issue?
