Hello, Some of our partners use the site concentrator. It's useful, but not really handy: - we don't know what is is actually doing, and what it is going to do later during the day (as we speak, debug.log and DryDockService.log are not usable to know what is happening) - we can't manage how it downloads files and updates So, if possible, we would like to see a web UI similar to the one we have when using Backup & Recovery ...more »
Over the Christmas period and other holidays my company occasionally requests a patch freeze - to prevent issues occurring when we have minimal staff in. An option to halt patching with one switch - or to be set via a paused time frame across all the customers we support would be ideal as currently I would have to go through and adjust each individual one.
allow us to chose which part of patching we are running 'on demand' e.g detection, download, installation, reboot.
The tool tip on the Patches Pending dot in the North pane just says "pending". It would be much more useful if it showed how long they have been pending so that we can identify systems that are being turned off in the evening or for some other reason are not performing updates. The number of updates pending would also be nice.
I have noticed that if you approve a patch for install. Then the device discovers that this patch has been superseded, the original patch is removed from any patch reports and in the Patch Management, and it still gets installed. There is no way to track what has been installed when it has been superseded. So a step by step scenario would be: 1. Patch is detected i.e. Patch1 2. Set Approval to 'Approve for Install' ...more »
It would be useful to be able to patch 3rd party products only to a specific version.
Unfortunately, some LOB Applications still require specific version of Java, Adobe Reader etc.
At present we can either not patch them, or patch them to the latest version; Nothing between.
Patches (specifically drivers) that require user input do not install under patch management.
Many of the drivers do not actually require any input despite this tag. They should be installed or attempted to be installed during the installation window.
Maybe a check box to allow this in the install windows.
Right now there is no good or easy distinction between missing patches which are approved and failed installations of the approved patches. Besides that the monitoring has a constant failed patch status, due to limitations in the service templates and thresholds. Besides that. If we approved patches, the patch status changes directly to failed. This is because the approved patch are (still) missing. This is true but not ...more »
Ability to clear probe and agent patch cache from the UI
When I re-apply a patch approval rule, I need to be able to tell when it is done applying and what all was changed - if anything.
Associated with ticket # 00897232.
It would be nice, if it's possible somehow to provide an overview of the patch management settings of each customer as a total overview and export them as .CSV.
At the moment when a restart is issued by the patchmanagement the logged in user of the device is only receiving a short message that his device will be rebooted but if he is not familiar with CMD commands he cannot stop the shutdown command and has not enough time to finish what he is doing / working on. It would be great improvement in regards to the user experience if the user on the device would get an actual dialog ...more »