Take a look at this setting in the snipping below, you might find that it works for your needs. The second setting is the one to really note. For regular workstations we let the updates fly, they’re deployed as available for 1 week prior to the deadline, after which install and reboot is forced. If a user has ignored all the notifications, they still have a reminder notification that they can’t close before they’re forced off. 24,000+ workstations get forced every month, there are some exceptions of course but for those they have a different patch deployment for available. [cid:[email protected]]
From: [email protected] [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Monday, February 2, 2015 4:46 PM To: [email protected] Subject: RE: [mssms] Pending Reboot and notification Shoot. I suppose maintenance windows might help with this, but they have so many terrible side-effects that I hate to use them. This problem comes up infrequently, but when it does, Murphy’s law dictates it happens at a critical time. That warning at the start of the reboot time, using notify balloons is easy to miss if you are looking away for 5 seconds. I could make the non-dismissable window pop up for longer than the default 15 minutes, but then that window is potentially in the way of something for a longer period of time. What I really need is for some way to make SCCM NEVER reboot the client. I will take care of rebooting when necessary From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Dwayne Allen Sent: Monday, February 02, 2015 3:03 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Pending Reboot and notification We are in pretty much the same situation. We suippress reboots, and then deploy a program to remind the stragglers of the need to reboot. A few times, that program or another one have forced reboots on people when a hard reboot is pending. As I understand it SCCM groups reboots in HARD or SOFT. A soft reboot just tells SCCM that the install is finished but a reboot is needed at some point in the future to fully complete. No big deal. A hard reboot tells SCCM that the computer is in such a state that install is finished but that the computer is in an unstable state and no other installations can be performed until a reboot is performed and the OS stabilizes. If you have a required deployment that hits a deadline then SCCM must install it, but if a hard reboot is pending then in order to perform the install it must first reboot the PC in order to complete the previous install. Unfortunately as far as I know there is no way to create a required deployment that will ignore hard reboots. Once you are in that hard reboot state it has to be resolved before anything else can happen ----- Dwayne Allen [email protected]<mailto:[email protected]> (479) 310-0027 On Mon, Feb 2, 2015 at 1:13 PM, Miller, Todd <[email protected]<mailto:[email protected]>> wrote: I suppress reboots on software updates and then I run a custom program to notify the user and reboot the computer. This has been working pretty well, but I recently ran into a problem with this. I had some computers that ended up in a “Hard Reboot was found pending” state and on those computers, SCCM forced a reboot before it would allow my Reboot package to run. Basically, it rebooted the client so that the reboot checker Program could run. What is a HARD REBOOT pending state? I have not run into that before. Normally, my check for reboot and notify script is allowed to run even if a client is in a pending reboot state. This Hard Reboot pending is a new one on me. It is forcing the computer to reboot before any other package is allowed to run- Even if I have all packages set to suppress reboot or “program controls reboots” I suppose there is no way to tell SCCM to ignore HARD REBOOT PENDING states and just let a package run. Hmmm….. ProgramID="Reboot for patches" <----This is my custom reboot notifier. It kicked off to notify the user a reboot was needed. But before it was allowed to run, SCCM wanted to reboot the client to get the client ready to run it. Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="XXX000F9",ProgramID="Reboot for patches", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l execmgr 2/2/2015 10:19:52 AM 7424 (0x1D00) MTC signaled SWD execution request with program id: Reboot for patches, package id: XXX000F9 for execution. execmgr 2/2/2015 10:19:52 AM 6704 (0x1A30) ++A Hard Reboot was found pending. Pause MTC task : {C07FCF2A-A85E-48D4-8E7C-A5DA125DF59E} execmgr 2/2/2015 10:19:52 AM 6704 (0x1A30) Pausing the corresponding MTC task with id: {C07FCF2A-A85E-48D4-8E7C-A5DA125DF59E} execmgr 2/2/2015 10:19:52 AM 6704 (0x1A30) Execution Request for advert XXX20069 package XXX000F9 program Reboot for patches state change from Ready to Paused execmgr 2/2/2015 10:19:52 AM 6704 (0x1A30) Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="XXX000F9",ProgramID="Reboot for patches", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l execmgr 2/2/2015 10:19:52 AM 6704 (0x1A30) MTC task with id {C07FCF2A-A85E-48D4-8E7C-A5DA125DF59E}, changed state from 4 to 6 execmgr 2/2/2015 10:19:52 AM 6704 (0x1A30) ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ ________________________________ CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. See our Privacy & Security page on www.henryford.com for more detailed information as well as information concerning MyChart, our new patient portal. If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us.
