I can view the current status of the installation state of a specific Update by selecting it from the Update Services/WSUS/Updates/xxx/Update....." tree and viewing the "Computer Summary" Tab. Example as a screenshot.

Using this view I can view the most current data. Now I'm searching for a way to create an automatic report. I can get the informations from the WSUS Analytics Tree, but those reports use consolidated non live data collected by the WSUS Inventory Task. This task needs about 4 hours to run.

Any idea how to get such (near live) information in an automatic report? I could even live with a powershell script if it is not possible by using the reporting functions of patchmanager.

Followed all 4 guides, but my Cleanup Task (just selected the first option) runs into a timeout (after only 3 minutes).

Yes, it's going to do this. It's a manifestation of not having done the maintenance previously.

Restart the task and let it run until it times out again. Rinse and repeat until it completes.

What's happening in this phase is that a complex set of database joins needs to occur to identify the updates eligible for deletion. A list of updates is built from that list, and then the rows are deleted from the various tables, one update at a time. This takes quite some time to do if thousands of updates are involved. Unfortunately, the ASP.NET timeout waiting for a response from the database server is not very tolerant, and the writers of this utility never envisioned this volume of work to be performed. As a result, ASP.NET gets bored, drops the connection, and reports a timeout waiting for the database server. The database, however, was still working, but with the dropped connection the task gets killed off. The good news is that the work that was already done is still done, so nothing is lost.

Also, if you're performing one option at a time, this is the order you should perform them in:

Decline expired updates and superseded updates (Option #5 and #6 in the Patch Manager dialog) -- this task will run fairly quickly in any condition because no deletions are being performed, merely flipping a boolean flag value from No to Yes.

Delete updates (Option #1 in the Patch Manager dialog) -- this is the task that actually times out. As described above, the delete updates process can be an exceptionally time consuming one depending on how many updates are eligible for deletion. It will likely take several executions of this task before it completes all available work.

Delete files (Option #4 in the Patch Manager dialog) -- after all updates have been declined or deleted, then the filesystem can be effectively cleaned up. If filesystem space is already critical, you can run this task after each "Delete updates" timeout, and it will remove whatever files might exist that are associated with whatever updates have been deleted.

Sadly the rinse and repeat strategy is not working. I've got 484 computers which did not connect the last 30 days. Dozens of "Delete Computer" Cleanup Tasks later I've got the same amount of computers.