Re: delayed Reboots after security patch application
- From: "Roger Abell [MVP]" <mvpNoSpam@xxxxxxx>
- Date: Sat, 15 Jul 2006 09:56:39 -0700
I do not currently recall (have link) for an interesting discussion read
once
in some MS paper . . . to effect that deferred reboot is not advised
because
post patching the system is in an intermediate and, IIRC its word correctly
it said, "potentially unstable state".
If you window for cycling the systems is on the weekend that probably
should be when the patches are applied, with use of "workarounds" if
needed due to risks/exposures until that windows come around.
<chris.kernaghan@xxxxxxxxx> wrote in message
news:1152703616.331731.198640@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
I am currently working in an environment which doe snot have set
downtime windows. It makes patching quite difficult to schedule as a
result.
I would be interested to know if anyone has had successes or issues
with applying patches which require a reboot in the middle of the week,
and then simply rebooting the servers at the weekend.
We are running Oracle databases, and my only concern is that we apply
the patch and by not rebooting we have one version of a file running in
memory and another version present on disk. If anything were to happen
the system might get itself confused.
Has anyone got any advice on this.
TIA
Chris aka BoobBoo
.
- References:
- delayed Reboots after security patch application
- From: chris . kernaghan
- delayed Reboots after security patch application
- Prev by Date: Re: Remaining NT vulnerabilities
- Previous by thread: Re: delayed Reboots after security patch application
- Next by thread: Re: change permissions
- Index(es):
Relevant Pages
|
|
