Here you go!
1. Maintenance Windows
* Physicals only have a couple edge cases where they only want reboots
at a certain time. Mostly long running SAS reports and such. All VMs have MWs
each night at specific times, staggered across all VMs. This is because of our
storage and the impact deploying any patches because they download and run
locally. All software deployments run from DP and have no impact.
* Do you usually just do it for 'Restarts' or 'Installs' as well? Both,
see above.
* Are you leveraging WoL and/or AMT? A little WoL, 1E Nightwatchman, but
nothing standardized. No AMT.
* If so, what is your success rate? Not sure, never reported on it.
2. Restart Behavior
* What do you specify for the two Client Notifications? 1440 & 120.
3. Communication
* Yes, posted on our intranet a few years ago. Everyone knows they get
24 hours, unless they are on a VM.
Daniel Ratliff
From: [email protected] [mailto:[email protected]] On
Behalf Of Adam Juelich
Sent: Wednesday, March 29, 2017 4:07 PM
To: [email protected]
Subject: Re: [mssms] Maintenance Windows & Restart Behavior
Thanks, Mike.
So you guys strictly use Windows Embedded? If you have traditional clients,
how do you manage them differently?
On Wed, Mar 29, 2017 at 2:27 PM, Marable, Mike
<[email protected]<mailto:[email protected]>> wrote:
Hi Adam,
1. Maintenance Windows
a. We use these only on our embedded devices and not on traditional
clients. We have a window set once a week (like 2 am on Sunday mornings) so
that SCCM turns off the write filter on the device, runs our deployments and
then re-enables the write filter.
2. Restart Behavior / Communications
a. We actually have written our own utility to handle reboots. It allows
us to display a message to the end user, countdown timer, users can delay the
reboot, we can have it check for running executables before attempting to
reboot, etc.
b. We have agreements in place with critical areas, such as emergency
rooms, and other 24hour clinics to limit reboots to specific days and times.
Otherwise the understanding with the users is that we will do our deployments
and maintenance outside of business hours. Combine that with our reboot tool
and the users are pretty happy.
We do use WOL very heavily. Different clinics have varying office hours/days
and we have collections set up to wake machines up about 15 minutes before the
beginning of business for them. We’ve been very successful with that. The WOL
issues that we have run into in the past have usually been attributed to either
mis-configured BIOs settings or users hard-powering off machines.
Mike
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Adam Juelich
Sent: Wednesday, March 29, 2017 2:55 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Maintenance Windows & Restart Behavior
Hello Everyone,
This isn't as much of a question as much as a poll on how people are doing
this. I know everyone is in charge of different environments, different
sizing, and other complex variables. I'd like to know what settings you
specify for the following items:
1. Maintenance Windows
* What are your MW for Windows Clients?
* Do you usually just do it for 'Restarts' or 'Installs' as well?
* Are you leveraging WoL and/or AMT?
* If so, what is your success rate?
1. Restart Behavior
* What do you specify for the two Client Notifications?
1. Communication
* How have you communicated this to end-users? It's obviously a
delicate balance between security and end-user convenience. Every environment
is different but I'm curious.
Anything else that I missed in this realm, I would appreciate knowing!
Thanks!
**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be
used for urgent or sensitive issues
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.
