I'm pretty sure that it just needs a reboot that clears RAM. Generally this requires full power down, but the newer BIOSes may work around that by reinitializing the BIOS without need of a power down.
On Mon, Feb 2, 2015 at 1:13 PM, Miller, Todd <[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. > ------------------------------ > >
