We currently have this relevance where it lists which pates have already been installed on Windows level only.
But we need a relevance where it is shown for all OS. Can you help me with this?
((item 0 of it, ((it as date) of ( ((it as integer as string) of preceding text of last "/" of following text of first "/" of it ) &" "& (preceding text of first "/" of it as integer as month as three letters)&" "& (following text of last "/" of it as integer as string)) of item 1 of it), item 2 of it) of (((if (exists property "HotFixID" of it) then (string value of property "HotFixID" of it) else ("")), (if (exists property "InstalledOn" of it) then ((if (exists hexadecimal integer (it)) then (((month of it as integer as string&"/"& day_of_month of it as integer as string&"/"&year of it as string) of ((january 1 of 1601)+((hexadecimal integer (it)/(864000000000))*day))) of it) else (it)) of string value of property "InstalledOn" of it) else ("")), (if (exists property "Description" of it) then (string value of property "Description" of it) else (""))) of select objects "* from Win32_QuickFixEngineering" of WMI))
Ok, so if you want to retrieve a list of installed packages for the various package managers of each operating systemā¦thatās probably a job for Inventory.
Yeah, you probably would need relevance in that case. Iām not sure that thereās a property reflecting OS patches for many of those distributions - and Iām not sure whether the concept makes sense.
For RHEL, what would even be an āinstalled OS Patchā? Is it a list of every RPM package installed, or is there some criteria you would use to define a āpatchā versus an āinstalled packageā? If every endpoint reports the thousands of installed RPM packages, your report (and more importantly the BFEnterprise database) could become quite huge quickly.
(Iām not saying it canāt be done, I honestly donāt know)
I would use the Inventory report for Installed Packages to show the RPM/DEB/etc. packages.
The size of the data just makes it untenable to do as Analysis Properties or Web Reports. Reporting of huge data sets like that is pretty much the whole reason for Inventory to exist as a standalone product.
Checking my Inventory āPackage Dataā report for a single RHEL 8 server that doesnāt even have third-party software installed, I have 1,375 package results. I think Inventory is the way to go for that.