Windows Vista UAC Questions

[Gary S. Terhune]

Re: UAC Questions

OK, but just to be clear, your example is not relevant to the OP's desires.
The whole point of UAC isn't to say "OK" to potentially bad programs, it's
to notify you that *something* or *someone* wants to launch the program. The
idea is to get you to ask the question, "What initiated this application?
Was it me? If not, then or who, or what issued the command?" If it isn't
"me" that initiated the program, UAC protocol dictates that I first find out
who or what tried to up the app before I let it continue. And just because
it's OK to run an app one time does not by any means guarantee that the next
time it runs it won't be at the behest of a virus or other malware. Take
Windows Explorer for example. That's one I can see OP adding to the UAC
Ignore List. It's also capable of wiping a lot of data, especially if OP is
already running as Admin. The list is long of legitimate apps that can
destroy your system or your personal data. Or just steal it, whatever.
That's why they put in UAC in the first place (and believe me, I am, shall
we say, ambivalent about the thing.) In the OP's case, using the method you
linked to would be silly. Oughta just turn UAC off.

Now, about that old app of yours. I don't follow. Do you have any idea what
the actual mechanics of the failure to run were? "Run as Administrator"
didn't work?

--
Gary S. Terhune
MS-MVP Shell/User
http://grystmill.com

"Synapse Syndrome" <synapse@NOSPAMsyndrome.me.uk> wrote in message
news:uQUSMeB%23IHA.3092@TK2MSFTNGP03.phx.gbl...
> "Gary S. Terhune" <none> wrote in message
> news:eGX3rLB%23IHA.3396@TK2MSFTNGP03.phx.gbl...
>> While I thank you for the link, if you're going to start disabling UAC
>> for anything, you might as well just turn it off.
>
>
> No, not is you are just doing it for particular known applications, as
> described on the page. I've had to use that method to get an old CAD
> application working in Vista.
>
> ss.
>

 

[Gary S. Terhune]

Re: UAC Questions

Your entire first paragraph is ridiculous. Makes it pretty obvious where you
fit into the paradigm you describe in your second paragraph -- "Clueless".

--
Gary S. Terhune
MS-MVP Shell/User
http://grystmill.com

"audiophile" <guest@unknown-email.com> wrote in message
news:8ec8ad0a9211e14fd3b50668edf7cab7@nntp-gateway.com...
>
> i just turned UAC off and disabled automatic updates on the applications
> i install. That way i know nothing is being installed i don't know
> about.
>
> It basically depends on who / where your pc is located and how much you
> can trust other people using your pc to know what they are doing.
>
>
> --
> audiophile

 

[Chris Geerlings]

Re: UAC Questions

To configure the UAC prompting behavior for administrators
1.. Log on to a Windows Vista computer with an administrator account in
Admin Approval Mode.
2.. Click the Start button, click Run, type secpol.msc, and then click OK.
3.. At the User Account Control dialog box for the Microsoft Management
Console, click Continue.
4.. In Local Security Settings, expand Local Security Settings, expand
Local Policies, and then expand Security Options.
5.. Right click the User Account Control: Behavior of the elevation prompt
for administrators in Admin Approval Mode setting and select Properties.
Note
For most situations, the No Prompt setting is NOT recommended. No prompt
elevation would permit UAC applications to launch administrator applications
without your knowledge or consent.

The following procedure details how to configure the User Account Control:
Behavior of the elevation prompt for standard users setting. This task can
be performed by standard users and administrators, but the following
procedure details the process for an administrator in Admin Approval Mode.

To configure the UAC prompting behavior for standard users
1.. Click the Start button, click Run, type secpol.msc, and then click OK.
2.. At the User Account Control dialog box for the Microsoft Management
Console, click Continue.
3.. In Local Security Settings, expand Local Security Settings, expand
Local Policies, and then expand Security Options.
4.. Right click the User Account Control: Behavior of the elevation prompt
for standard users setting and select Properties.
The following table describes the User Account Control: Behavior of the
elevation prompt for administrators in Admin Approval Mode and the User
Account Control: Behavior of the elevation prompt for standard users
settings.

Consent policy for elevation
Setting Description Default Value
User Account Control: Behavior of the elevation prompt for
administrators in Admin Approval Mode
There are three possible values:

1. No prompt - The elevation occurs automatically and silently.

2. Prompt for consent - UAC asks for consent before elevating.

3.
Prompt for credentials - UAC requires valid administrator
credentials are entered before elevating. This policy is only in effect when
UAC is enabled.



Prompt for consent

User Account Control: Behavior of the elevation prompt for standard
users There are two possible values:

1.
No prompt - No elevation prompt is presented and the user cannot
perform administrative tasks without using Run as administrator or by
logging on with an administrator account.

2. Prompt for credentials - UAC requires that valid
administrator credentials are entered before elevating.



Prompt for credentials


Changing the behavior of the UAC elevation prompt should be done with
careful consideration. This policy is configurable for both administrators
in Admin Approval Mode and standard users. The following general guidance
can help you determine how to configure the UAC prompting behavior for your
environment.


--
Chris