Patch Management Test Series - Criticism, Feedback, feature suggestions

Hello,

we've tested TV Patchmgmt. for more than 2 Weeks. The TeamViewer (=TV) Sales employee told me that this is the right place for out critism, feedback and feature requests.If you have some of the points of criticism or suggestions on your roadmap for new features, we would be happy to receive information about them. German translation will be added below the english part.

1. Patches cannot be uninstalled in the Mgmt. Console.
   Why is it important to us?
   It happens that patches are not rolled out extensively tested by Microsoft and cause problems that go as far as BSOD. The option to uninstall individual updates is available in Windows 10 Pro. A patch management tool has a major benefit when it is possible to withdraw patches centrally via a console instead of having to switch to each individual endpoint in order to carry out the uninstallation manually.
2. No advance warning or announcement for the start of the update process (i.e. the download and installation process) for the user (or such a message was not registered during the test runs.).
   Why is it important to us?
   In case of live talks (software audio codec on our production machines) or video conferences (which are usually recorded and are therefore relevant to production), the download of the update process may take up the necessary bandwidth capacity and can lead to disruptions in live operation. Especially at branch offices or people who work on the go. Possible solutions:
   A) Limitation of bandwidth during the update process, definable in the Mgmt. Console. When preparing the first test run (June 9th) and reading the manual, such a feature was discovered-
   User will be notified of the start of the update process (as it is for pending restarts) and has interaction options (postpone / suspend).
3. No status display (progress) during the update process within the TV Mgmt. Console for the individual endpoints as well as for the respective patches.
4. E-mail notification about success / failure of the patching process does not work. The same applies to monitoring alerts.
5. There are no driver installations possible while using the Patchmgmt.-Service from TV, but these patches are indexed and offered via the normal Windows update process.
   Furthermore you can't supply the service with "own" patches.
6. Windows 10 feature upgrades are not taken into account, i.e. not shown as available or necessary in the Mgmt. console. Clients that have an outdated version of Windows 10  are not marked accordingly.
7. Some of the available patches can only be installed manually (OS and 3rd party). Quantity in our test series: ~ 30 - 40%
   Some of these patches do not contain any further information (KB No., details), including some Win 10 patches.
8. In several (and repeated series of tests) it happened that the automated patch deployment (policy driven) did not work for all patches on several different endpoints (all Windows 10 Pro - clients on different hardware basis). Since communication regarding successful and unsuccessful patches does not work, there is virtually no feedback on a patch that has not been deployed. Accordingly, a log is missing to find out the causes of these omitted patches. Pushing some of these "omitted" patches installed them in many cases (double the effort). When configuring the policies, explicit attention was paid to the correct date and time (UTC).

Thank you for enabling the test phase. We would be happy if someone from support / development took care of our topics. A documentation of the test series with requirements and results can be made available to TV.