xc3ss1v3 Posted December 18, 2013 Report post Posted December 18, 2013 Hey guys... wonder if I could get some suggestions/instructions. Currently, we are not employing any kind of maintenance window for monthly updates. Once deployed, we leave it up to our users to install before the deadline (1 week) and after that, they're left up to the will of SCCM to install when it wants. Obviously, that deadline has been met with some frustration in people not wanting their machines restarted in the middle of the day... some even with work still open because they've walked away. I would like to tell them that they've had 7 days to do this whenever they like, but obviously, I can't do that. So, I wondered what others are doing to ensure that software updates are pushed out in a reasonable amount of time, while balancing letting the user decide and then forcing AFTER hours to accommodate the user. Thanks for any input. Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted December 18, 2013 Report post Posted December 18, 2013 I would like to tell them that they've had 7 days to do this whenever they like... This is exactly what I do! If they can't be bothered to do it when it is better for them, then how can I be blamed for it. Quote Share this post Link to post Share on other sites More sharing options...
Edenost Posted December 19, 2013 Report post Posted December 19, 2013 What I've done is I've given the update a couple of hours once deployed to install. I have suppressed ALL and ANY reboots and notifications. The user see's nothing, except sometimes they will be told they need to restart to complete the updates. In the evening, around 8-9pm, we have a scheduled task which shuts all PC's down, room by room, for the night. When they turn on the next day, they have been fully updated. That way, no one even knows . Quote Share this post Link to post Share on other sites More sharing options...
Fugeth Posted December 30, 2013 Report post Posted December 30, 2013 I have a similar situations. We have mostly mobile users so shutting machines down at night at a certain time doesn't work well. What I have done is created a maintenance window that starts an hour before the end of the day. This way the updates gets pushed out, but the users aren't forced to reboot during the middle of their days. Any machines that get left on will be rebooted as required by the updates, and any machine that get missed will hit the wall and will be forced.when they hit the deadline. Quote Share this post Link to post Share on other sites More sharing options...
