"Pimperator" <> wrote in message
news:...
> Hi there,
> can anybody tell me how I avoid Servers and Clients rebooting after being
> updated?
Well, basically, you don't. The design architecture of WSUS and the WUAgent,
and the Microsoft Windows OS (since the creation of Automatic Updates over
10 years ago) requires that the system be restarted when certain
system-level updates are installed. Until the system restarts, the updates
are not actually installed -- ergo, if you're not going to restart the
system, there's absolutely NO point in installing the updates.
In fact, partialling installing the updates (which is what may happen until
the restart is actually performed) may introduce system instabilities and
cause problems even worse than those you're currently concerned about as a
result of a controlled system restart.
So, the *best* way to achieve what you're trying to achieve is to
interactively install the updates WHEN you've determined it's an appropriate
time to restart the system.
Alternatively, on workstations and notebooks, you might take advantage of
the "Install Updates and Shutdown" feature, which requires some nominal
training and cooperation on the part of users, combined with an after-hours
scheduled installation (e.g. 3am) and the default feature to install updates
at power-on if they were scheduled for installation, and the scheduled
installation did not run due to the machine being powered off.
> I delivered several updates today and unfortunately I had some computers
> calculating for about a week rebooted. So I had Information-loss of about
> a week.
NO machine should ever be in a situation where DAYS of data is a risk of
loss due to an unexpected system shutdown. Unless you have those machines on
a perpetually-fueled generator, you cannot possibly protect against an
unanticipated system shutdown in a power outage of more than a few hours.
I do understand, however, that a machine might be involved in data
calculations that may take days to complete. May I be so bold to suggest,
here, that the issue is not that you installed updates (and inadvertently
caused a system restart) -- but that anybody even had access to the machine
in the first place while it was performing such calculations!
> Our Fileserver also rebooted during night while we had measurements
> running. So again data loss.
Installing updates on a mission-critical system without direct sysadmin
involvement at the console is the primary failure here, not the inadvertent
reboot resulting from those installations. If you have "measurements"
running against your fileserver that are uninterruptible, or "calculations"
running on a workstation, then the LAST THING you should be doing is
installing ANY software, updates, etc., never mind the obvious issue of
actually rebooting the box. In fact, you ought not even be permitted to
start ANY process on such a machine beyond those required to complete the
calculations required for the mission.
> really need to disable forced rebooting.
No, Erik, honestly, I believe you need to be more proactive in your system
and update administration tasks.
Based on everything you've said, fixing the standard behavior of Windows
updating that's existed for the past ten years is not what you need (and
it's not going to happen anyway); you need better control over WHEN and WHO
installs updates -- period.
I know my response sounds harsh -- but if your situation is as critical as
you've made it sound in this message, then IMO the system controls on these
machines are not near strict enough to ensure their safe and continued
operation.
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website:
http://www.microsoft.com/wsus
My Websites:
http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile:
http://mvp.support.microsoft.com/pro...awrence.Garvin
Similar Threads
Linear Mode
