Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Focus-Microsoft
[Top] [All Lists]

RE: Automatic Updates and Users/Power Users

Subject: RE: Automatic Updates and Users/Power Users
Date: Thu, 13 Jan 2005 20:46:17 +0100
Actually. the NO button is grayed out for everyone. Even for local 
administrators (on workstations)
I addressed this problem a year ago.. It is still not fixed.

Ronald Balk
Borland Software Corporation

-----Original Message-----
From: Stegman, William [mailto:Bill.Stegman@transcore.com] 
Sent: Thursday, January 13, 2005 2:17 PM
To: focus-ms@securityfocus.com
Subject: RE: Automatic Updates and Users/Power Users

I've noticed one annoyance with SUS and non-admin users.  If you're using SUS 
and a GPO with the automatically download and schedule the install, only admins 
are able to click yes or no to the subsequent reboot screen after having the 
updates applied.  The no button is grayed out for non-admins.  



-----Original Message-----
From: Rasmus Rønlev [mailto:rr.its@cbs.dk]
Sent: Wednesday, January 12, 2005 5:14 PM
To: focus-ms@securityfocus.com
Subject: RE: Automatic Updates and Users/Power Users

Okey,

If my first post gets through, that needs to be semi-disregarded, was a bit 
quick on the reply button there. Sorry.

The Windows Update program/service runs as the System Account. And if it's set 
to automaticly download and notify it will ask anyone logged on interactively, 
for permission to install the downloaded patches. Since it has rights from the 
system account it will install updates no problem in this setting, from a 
normal user account and upwards. No problems at all.

If you use SUS nothing much changes except your Windows Update service will now 
only download updates, that you have accepted to roll out on/from your SUS 
server. In this way you can potentially delay or block rolling out certain 
update packages, which you might not want to deploy in your enterprise. The 
same download/install behaviour described above will still be in effect though. 
I.e. you can use it for everyone with User privileges and up.

I hope that answers the questions somewhat more to the point :)

Regards,
r@smus

.
Rasmus Rønlev
Copenhagen Business School, ITSu
Cell: (+45) 29612544
Phone: (+45) 38153521
Fax: (+45) 38153536

-----Original Message-----
From: Evan Mann [mailto:emann@pinnaclefinancial.com]
Sent: 12. januar 2005 17:56
To: focus-ms@securityfocus.com
Subject: Automatic Updates and Users/Power Users

If Automatic Updates is not set via GPO to contact an SUS Server but has been 
set to download updates and notify to install, will a user or power user be 
able to initiate the install?

If Automatic Updates is set via GPO with the same download/install, but from an 
SUS server, does anything change?

Essentially, how do I ensure, using Automatic Updates, with and without SUS, 
that a computer that the daily user only has User or Power User Access, that 
the updates can be installed.


---------------------------------------------------------------------------
---------------------------------------------------------------------------



---------------------------------------------------------------------------
---------------------------------------------------------------------------

---------------------------------------------------------------------------
---------------------------------------------------------------------------



---------------------------------------------------------------------------
---------------------------------------------------------------------------


<Prev in Thread] Current Thread [Next in Thread>