I do the same thing (SCCM 2007) all laptops & some desktops that cannot be 
rebooted (1000+) apply patches during the day silently suppressing any reboots. 
Usually natural shutdown / restart attrition allows them to become compliant. 
Some users need a reminder but that is just my environment. This has worked for 
us for many years, we do use 1E Wakeup and Maint Windows for the other desktops 
across our footprint.

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Marcum, John
Sent: Friday, January 09, 2015 8:13 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] A tool idea related to Maintenace Widow discussion

I believe you are perfectly describing the software that 1e sells.

What I've done in the past for laptops is to ignore maintenance windows, patch 
completely silently and do not reboot. I've never had a single complaint doing 
that for 8 years now.





On Thu, Jan 8, 2015 at 10:54 AM, Miller, Todd 
<todd-mil...@uiowa.edu<mailto:todd-mil...@uiowa.edu>> wrote:
All the discussion of Maintenance Windows has me thinking about a significant 
gap in the SCCM product.

Maintenance windows are pretty terrific for clients that are always on like 
servers, but are not so hot for clients that go to sleep.  It is missing in the 
product to schedule a wake up at the start of the next MW if there is a 
deferred installation pending.

It would be cool if someone with skillz could write a shim that computes 
whether there is a deferred installation waiting for the next MW.  The shim 
could subscribe to sleep/shutdown event and run just prior to the machine going 
to sleep and schedule the computer to wake at the start of the MW if there is a 
deferred installation pending.

It doesn’t solve the laptop problem with MWs, but it sure would make them more 
reliable for plugged in but sleep enabled computers.

I know you can set the power settings to wake the computer up for the MW, but 
there are two problems with that.  The first is that the computer will 
frequently wake up unnecessarily with no scheduled task to perform.  The second 
problem is that the go back to sleep timer is usually set to 2 minutes which is 
frequently too short for SCCM to discover it has a task to run

________________________________
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 e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.

________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.


Reply via email to