Update Management
Please take a few minutes to submit your idea or vote up an existing idea. All of the feedback you share in these forums will be monitored and reviewed by the Update Management engineering team.
-
servers with pending reboot should not show as compliant
Don't turn a recently patched server to compliant before the server has been rebooted (after patching). the existing implementation turns a recently patched server to compliant before it's restarted and can lead a person to forget to restart the server and leaving the patches not yet applied.
12 votesThanks for the feedback. We will take a look as resources allow.
-
Do an immediate refresh of compliance data after update deployment (linux)
After a deployment/update job, the data for the compliance dashboard should be immediately updated - not have to wait for the next scheduled compliance check
3 votes -
Schedule immediate compliance refresh function
I'd like to be able to schedule a refresh of compliance data (outstanding patches) whenever the next heartbeat occurs. Unless I'm missing something, the data can be somewhat stale and offers no easy way of getting it updated in a more timely fashion.
2 votes
- Don't see your idea?