Hello lko,
In addition to the report mentioned by andykn101; detailed on KM: TECH127607, you may also review the legacy (hidden) Policy Execution by Computer report.
This report can be unhidden by running the following SQL script to unhide the report (for good measure; ensure a recent backup of the database is in order before proceding):
begin tran
update Item
set Attributes =0
where Guid='F47ED416-3847-4B46-8D5B-851C075CAE7A'
--If all is in order with 1 row affected; run the following:
commit tran
--If undesired return occurs; run the following:
rollback tran
This report is hidden as the product has evolved from the original authoring; this report could time out due to the amount of data returned. Furthermore, it would be best practice to create a clone of the report, rerun the script to restore attribute =23 (default value), and use the cloned report moving forward. This will ensure the product is kept in a supported default state.
Keep in mind that the report pulls from several task tables that are purged on a daily or weekly schedule, so some columns may display n/a. Run the report as soon as updates are deployed and export the data for archive purposes before these tables are purged.
Note: problems with this report will not be supported as it was not included as part of the released product. However, I have found it to be a solid report that delivers the Computer Name, Software Bulletin, Update Name, Policy Name, Package Status, Execution Status, Return Code, Duration, Start & End Time, and Logged in User.
These reports, used in conjunction with the Compliance Reports, should provide all needed Patch Reporting data.
Hope this helps,
Joshua