Re: Scheduled Updates Reboots Machines

From: Charlie (sulliaef@bc.edu)
Date: 04/04/03


From: "Charlie" <sulliaef@bc.edu>
Date: Thu, 3 Apr 2003 19:55:47 -0800


This is amusing - I decided to look into SUS. I opened
up the folder in Technet that contained the installation
file and almost ignored the one other file that was in
the folder. I happened to notice that it was an .adm
file so imported it into GP just to see what it contained
and there was my solution - simply a policy for
disallowing the computer to be rebooted after a WU is
installed. SUS is not needed for this, apparently.
Thanks in a roundabout way!
Charlie
>-----Original Message-----
>Charlie wrote:
>
>> Hi
>> We have 200+ XP Pro machines on an NT4 Network.
Windows
>> Updates are set to automatically download and then
>> install @3AM every night. Our users do not have Admin
>> rights so they are not prompted to install them after
the
>> download. We've been doing this since Novemeber with
no
>> apparent problems until last week - The updates
rebooted
>> the machines automatically. Needless to say, a lot of
>> users don't log off as they should and some don't even
>> close their apps. One user lost a new document that he
>> had left open. Another keeps a Web accessible
Filemaker
>> DB running which closed down. I didn't realize when I
>> set these up that there would be forced reboots. Is
>> there any documentation on this? Any ideas about a
>> better solution for our environment?
>> Thanks
>
>Hi
>
>You could look at Microsoft Software Update Services
(SUS). The newly released
>SP1 version can suppress reboots.
>
>
>Microsoft Software Update Services
>http://www.microsoft.com/windows2000/windowsupdate/sus/de
fault.asp
>
>Note that the free version will only install critical
updates and security
>rollup packages (SRPs).
>
>SUS needs to be installed on a IIS server. Supports
Win2k and WinXP clients
>only. SP1 for WinXP and SP3 for Win2k installs the
WU/SUS client as default.
>
>
>http://www.microsoft.com/technet/itsolutions/msm/swdist/p
msusog.asp
>
>Some info from a previous content in the URL above:
>
><quote>
>SUS is available in two versions. One can be downloaded
from
>http://www.microsoft.com/windows2000/windowsupdate/SUS/de
fault.asp ; the other
>is available as a licensing program. The downloadable
version downloads and
>installs operating system critical updates and security
rollup packages (SRPs).
>
>All other patches, including applications, service
packs, and non-critical
>updates that need to be installed before they are issued
as a security rollup
>package, go through distribution and deployment.
>
>For those customers on the Microsoft Software Assurance
(SA) licensing program,
>
>a more comprehensive version of SUS is available that
can download and install
>operating system service packs, non-critical security
updates, and selected
>Quick Fix Engineering (QFE) fixes determined to be vital
to the successful
>operation of the operating system. This version is known
as SUS SA Edition.
>
>Organizations wanting to obtain and use SUS SA Edition
in their environments
>will need to participate in the Software Assurance
program. For more
>information
>
>on this program and licensing in general, see
>http://www.microsoft.com/licensing/default.asp.
></quote>
>
>Note that the SUS SA Edition still is in beta but should
be available in a
>release version soon.
>
>
>There is a separate newsgroup for SUS:
>microsoft.public.softwareupdatesvcs
>
>URL to the group softwareupdatesvcs for those who uses
the not so good Web
>interface to access the newsgroups:
>http://communities.microsoft.com/Newsgroups/default.asp?
ICP=MSCOM&sLCID=US&newsgroup=microsoft.public.softwareupda
tesvcs
>
>
>
>
>
>
>A Web site about SUS with a FAQ and a SUS forum:
>
>SUSserver.com
>http://www.susserver.com/
>
>
>When evaluating hotfix administration methods/programs,
>there are also 3rd party solutions available that will
>give a lot more than what SUS offer, but of course, they
>are not free. It is as always a cost/benefit analyze that
>needs to be done.
>
>Below is links to a 3rd party product example that does
>not need a server to run and no IIS is needed. You can
>deploy mostly all types of hotfixes and service packs
from
>an ordinary workstation if you want. I have not tested
it,
>but it gets a lot of prize by other people e.g. in the
>newsgroups.
>
>
>UpdateEXPERT from Sunbelt
>http://www.sunbelt-software.com/product.cfm?id=357
>
>UpdateEXPERT reseller with a price list
>http://www.softwareshelf.com/products/display.asp?p=71
>
>
>
>
>--
>torgeir
>Microsoft MVP Scripting and WMI, Porsgrunn Norway
>Administration scripting examples and an ONLINE version
of the 1328 page
>Scripting Guide:
http://www.microsoft.com/technet/scriptcenter
>
>
>.
>



Relevant Pages

  • Re: SUS downloading XP SP2 with error code 407
    ... Go to your SUS admin page. ... The w2k DC SUS server is configured to automatically download updates ... Automatic Sync Started- 29. ...
    (microsoft.public.isa)
  • Re: SUS downloading XP SP2 with error code 407
    ... SUS can be configured to authenticate properly. ... "Jim Harrison " wrote: ... > SUS is fetching updates as domain user that has full download ... > rights for updates. ...
    (microsoft.public.isa)
  • Re: SUS downloading XP SP2 with error code 407
    ... - your ISA logs ... We're currently working on this with the WU team, although this is the first SUS failure I've heard of... ... SUS is fetching updates as domain user that has full download ...
    (microsoft.public.isa)
  • Re: Scheduled Updates Reboots Machines
    ... I knew about SUS and wondered if it would help. ... >> Updates are set to automatically download and then ... >> install @3AM every night. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Deploying Crit Updates
    ... Note that the free version will only install critical updates and security ... SUS needs to be installed on a IIS server. ... a more comprehensive version of SUS is available that can download and install ...
    (microsoft.public.security)

Quantcast