Here are the prompts users will see if you allow them in your deployment. http://www.cmu.edu/computing/repair/dsp/doc/updates-sccm.html
You can control the timings up to 1440 minutes (24 hours) via the Client settings. [cid:[email protected]] Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Charles Hiland Sent: Wednesday, July 15, 2015 11:16 AM To: [email protected] Subject: [mssms] SUP 2012 Best Practices Good morning/afternoon/evening. I currently have configured SCCM to act as a software update point for a few test machines, and I've been asked to expand the testing to a few departments. I was wondering if those who have experience doing so had any tips? Eventually I will be pushing out Windows updates to about 1200 workstation machines, and want the end-user to experience minimal invasiveness. In a perfect world, I'd like to hide the updates and require a restart, but my experience is that once the deadline is reached, updates are installed and I'm given a 90-minute window to restart my computer (assuming the MS updates require a reboot, which they usually do). There isn't an option for a user to postpone rebooting is there (vis-à-vis standard WSUS). Any feedback is appreciated! -Charlie The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
