We have seen this occasionally, but usually it is due to some extenuating circumstance. Like if we had turned off the SUS GPO to do some testing (we only have one SUS server setup right now, with multiple GPOs) the clients revert back to their previous Automatic Update settings. If they have it set to Download but Prompt me, they can ignore those. Therefore SUS will think they are good, but they are really not. Similarly, if they turn their computers off continually during the time you have SUS set to run (like ours is 3 AM every day), they may have downloaded the patches earlier (we find sometime in the afternoon or late evening it prepares this), but if the computer is off, it never runs. And if it prompts them the next morning, they can choose to ignore.
 
Ok, enough rambling. But what it comes down to is a bit of planning on our end (the sysadmins) as well as a bit of user education. The latter is the part that has been most troublesome for us. I guess "leave your computer on (but logged off) all the time" does not mean anything to anyone. :)
 
Chris
---------------------------------------------------------
Christopher England
Server Administrator
MCSA, Server+, Network+, A+
College Information Technology Office
Indiana University


From: Greg Felzer [mailto:[EMAIL PROTECTED]
Sent: Friday, September 26, 2003 8:08 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] SUS failure rate

I was wondering what kind of failure rate you have all been seeing having SUS install patches.

 

We are preparing a lab test to get hard numbers.  We have seen failures where SUS repeatedly tries to install the same patch on each connect and where SUS claims the patch is installed but scanning with HFnetCHKPro shows that the patch is not installed.

 

Greg Felzer
MCSE NT4, MCSE 2000, CCA, CCNA, CNA
Senior Systems Engineer
Center for Computing and Information Technology
Medical University of South Carolina

 

Reply via email to