A user at the University of Pennsylvania School of Medicine shared feedback regarding the ControlUp compliance agent installed on their computer to manage software updates. The primary issue reported was that while the agent provided notifications about pending updates and allowed snoozing them, there was no mechanism to initiate the update manually before the snooze period expired. This created a challenge for users like statisticians who keep long-running analysis sessions open and prefer to update at specific, convenient times without forced restarts interrupting their work.
The user requested one of two improvements: either enabling a way to revisit the notification after snoozing so they could start the update on demand, or having the compliance agent queue the update to trigger automatically upon the first manual restart occurring before the snooze period ends. This functionality would give users the flexibility to apply updates immediately when they choose, avoiding unexpected disruptions while still deferring updates if necessary.
ControlUp support engaged by asking for the organization name and requesting logs from the device in question to investigate the behavior further. The user clarified that no logs were clearly visible and only the notification and snooze options appeared. The support team then inquired about the presence of log files in the ControlUp compliance agent’s log directory located at C:\ProgramData\ControlUp\CU4DC\Logs, which is where relevant diagnostic data might be stored to better understand the update management interactions.
This discussion highlights an area for product enhancement around update scheduling within the ControlUp compliance agent. Currently, the update snooze feature lacks a proactive user control to manually trigger pending updates outside the original snooze timing. Users who rely on long-duration sessions or need precise control over disruptive restarts may find this limiting. Including the ability to either resume update installation on demand after snoozing or to ensure updates proceed on the next manual system restart would address these concerns and improve user experience in environments with sensitive workflows.
For administrators managing ControlUp compliance agent deployments, checking the client log directory at C:\ProgramData\ControlUp\CU4DC\Logs can assist in troubleshooting update notification and enforcement issues. Until this feature is added, coordinating the timing of forced updates with end users who require flexible update start times is advisable to minimize work interruptions.
More details about ControlUp Compliance Agent and managing update behavior can be found in the official documentation at https://docs.controlup.com/compliance-agent. Users seeking advanced update control features can also explore ControlUp’s community forums and support channels for the latest product enhancements and best practices.
Read the entire ‘Enhancing Update Control in ControlUp Compliance Agent: User Request for Manual Update Initiation Before Snooze Expiry’ thread below:
Our IT folks installed ControlUp compliance agent on my computer so that I could have some control over when updates happened. They would normally push updates at the beginning of the month, and force restart my computer at very inopportune times. I cannot close all of my analysis sessions at the whim of the update gods.
Your application has not turned out much better. Your notification comes, and I can snooze it, but If I find I am ready to do the update ahead of the snooze schedule, there is no way to make it happen.
One of two things needs to change. Either you should 1) give me a way to get back to the notification ahead of the snooze wake-up, so I can start the update from there, or 2) cue up the update so that it will happen with the first manual restart. Please do one of those things.
Hello,
Thank you for posting!
I’m tagging and for their awareness!
FYI
checking it now.
which org
could you share your organization name?
if you can attached here the logs from one of the devices with the problem
c/program data / controlup/cu4c/logs
University of Pennsylvania School of Medicine. I am a statistician and I generally have multiple analysis sessions open for days or weeks at a time. I need the ability to shut down applications and take those updates at times of my choosing.
What logs? I just get a frickin notice from the compliance agent, and my only option is to pick a snooze time. I usually pick one several days out… but then if I find that there is a good time to shut down all my stuff, I need to be able to update at that time of opportunity.
The best thing is to program it so that if I have hit snooze, the update will automatically happen if I restart manually before the snooze is done.
do you see files being created under this folder?
`C:\ProgramData\Controlup\CU4DC\Logs`
Continue reading and comment on the thread ‘Enhancing Update Control in ControlUp Compliance Agent: User Request for Manual Update Initiation Before Snooze Expiry’. Not a member? Join Here!
Categories: All Archives, ControlUp Workflows
