Re: POSTPONING REBOOT AFTER INSTALLING UPDATES
- From: KatakaH <KatakaH@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 9 Dec 2008 15:28:15 -0800
Thank you very much Harry. Yes, you are correct. I do indeed know that
server should be restarted immediately after applying an update. Now I have
corroboration of another IT expert along with slightly embarrassing remark
regarding Sammy the hamster. Perfect. Absolutely perfect. If you know
anyone else that could put their two cents in as well, please ask them to
make a comment. Expanding on the Sammy the IT hamster theme would be greatly
appreciated.
A little more background: My IT nemesis is a youngster (age 23) that found
himself in a position as IT director of a law firm employing over 300 people.
He has marginal IT skills and terrible communication skills. One of his
duck-and-cover routines when he ignores my suggestions and requests (related
to resolving a problem in my companies Financial and Practice Management
suite) is to circulate emails to all the principals at the firm. Take this
"update" issue for example: I'm trying to eliminate potential causes of our
db engine locking up after a period of time and asked he stop applying
updates without rebooting. His reaction was to send emails to seven
different, non IT employees at the firm stating that he has docs to prove
applying updates without rebooting is ok. He goes on to say that he hopes
that we will acknowledge the problem with our software and make an effort to
fix the corruption in our databases. He then goes silent for the past three
weeks while users at the firm are grumbling and muttering about the problems
in our software that we are unwilling to fix.
It is my sincere hope to educate this young man with the help of other IT
professional such as yourself. The upside is I get to circulate (with a
Reply to All)these comments to the firm executives. I know I shouldn't enjoy
this...but I do.
Thank you again.
I need more comments people! Would you, or do you, follow similar practices
where you work?
"Harry Johnston [MVP]" wrote:
KatakaH wrote:.
What kind of problems will occur if you install updates on a 2003 server
without rebooting when prompted?
This might cause the system to become unstable. Almost any symptoms are
possible ... well, I don't suppose it will cause the hardware to fail, or
electrocute the system administrator, but anything short of that. :-)
For example, can you safely operate the
server if you postpone the reboot for a couple days?
No.
How about a couple weeks?
An even bigger no.
[From a later post:]
The IT guy refuses to listen and claims he has
documentation explaining that postponing reboots after applying updates is an
acceptable practice.
Ask who wrote the documentation ... Sammy the Hamster, perhaps? :-)
As I think you already know, this is wrong. Servers should always be rebooted
immediately after installing updates. If you can't reboot the server, wait to
install the update until you can; after all, the update won't actually work
until the reboot has completed, so you aren't gaining anything by installing the
update early.
Harry.
- References:
- POSTPONING REBOOT AFTER INSTALLING UPDATES
- From: KatakaH
- Re: POSTPONING REBOOT AFTER INSTALLING UPDATES
- From: Harry Johnston [MVP]
- POSTPONING REBOOT AFTER INSTALLING UPDATES
- Prev by Date: santigonzar01@hotmail.com
- Next by Date: Microsoft Update?
- Previous by thread: Re: POSTPONING REBOOT AFTER INSTALLING UPDATES
- Next by thread: 0x80071B6E error?
- Index(es):
Relevant Pages
|
