Roger
Sat May 20 18:40:59 CDT 2006
It would be interesting if you could control in your cpau so that the
token did not get restricted, and I find it dumb if it does restrict when
someone has conciously used runas to get an admin session . . .
After thinking some I believe the suggestion should be to provide a
"suspend for remainder of this login" button and have a time limiter
of say a day for those like myself that customarily hibernate a client.
Roger
"Joe Richards [MVP]" <humorexpress@hotmail.com> wrote in message
news:OfoUJZ1eGHA.4948@TK2MSFTNGP04.phx.gbl...
> Yeah that sounds like a good suggestion, maybe when it first pops up after
> an install it asks if you want to suspend for a day or two for the initial
> build up. Course bad things could still get through, but that is the same
> as if they turned it off permanently and maybe doing it this way the
> benefit comes back instead of being always off.
>
> I haven't tried it (note to self for the weekend testing), if I use runas
> or my cpau if the newly spawned window is also impacted by UAC. If it
> wasn't, that would be handy because then I just spawn a new command prompt
> with those rights and the UAC doesn't pop up for anything I do from
> there...
>
>
>
> --
> Joe Richards Microsoft MVP Windows Server Directory Services
> Author of O'Reilly Active Directory Third Edition
> www.joeware.net
>
>
> ---O'Reilly Active Directory Third Edition now available---
>
>
http://www.joeware.net/win/ad3e.htm
>
>
>
> Roger Abell [MVP] wrote:
>> Perhaps we have hit on something to suggest Joe.
>> A temporary UAC suspend - say for 24 hours at a wack.
>> People are going to find the trick to shut if off, at least the
>> more power users are, and then it is off until reenabled.
>> So, what if during inital config, times of extensive admin use,
>> etc., there was a suspend UAC for x hours ??
>>
>> I have noticed that with 5381.1 it is less annoying than when I
>> first started experiencing it, at 5308 or whatever build that was.
>> Perhaps it is less invasive, but I tend to believe it is that I am
>> becoming more accustomed to it and also that I have to do less
>> hunting to find where things have been hidden (or omitted).
>>
>> I still believe that if people who do run as an admin just get over
>> the hump of inital config, then they will not that often see the
>> prompting. At that point UAC is only a good thing, as they are
>> running as a limited user.
>>
>>
>> "Joe Richards [MVP]" <humorexpress@hotmail.com> wrote in message
>> news:%23n9gxxheGHA.3484@TK2MSFTNGP04.phx.gbl...
>>> I agree, it is annoying but the folks using it right now are doing all
>>> sorts of things they may not be doing after they have it running for a
>>> month or two and are "stable". I noticed that the UAC was pissing me
>>> right off until all of a sudden I didn't reload the machine for a week
>>> or so and I realized I went a day or two without seeing it at all
>>> because I was just using the machine after I had stabilized.... Getting
>>> through that few days though is going to be trying for some folks.
>>>
>>> And honestly, I almost got to the point when reloading a lot where I
>>> wasn't even looking at the prompts anymore and I was just clicking. At
>>> that point, it has completely lost its effectiveness as a security
>>> feature.
>>>
>>>
>>> --
>>> Joe Richards Microsoft MVP Windows Server Directory Services
>>> Author of O'Reilly Active Directory Third Edition
>>> www.joeware.net
>>>
>>>
>>> ---O'Reilly Active Directory Third Edition now available---
>>>
>>>
http://www.joeware.net/win/ad3e.htm
>>>
>>>
>>>
>>> Roger Abell [MVP] wrote:
>>>> My own feeling is that the jury is (not yet formed but effectively)
>>>> still out
>>>> on consumer acceptance of the final form of this feature. Once the
>>>> behavior is refined for release, AIUI the intent is for people that use
>>>> an
>>>> admin account as their normal login to not imperil their machine by so
>>>> doing, and yet when they do activate something that does require use
>>>> of their admin privs they will be allowed to do so.
>>>> Now, in the current and prior builds many testers do find the feature
>>>> to be obnoxious. But then those testers are characteristically doing
>>>> all
>>>> sorts of things that use their admin privs (exploring all the config
>>>> settings,
>>>> installing components, etc.) so perhaps the current test sample is not
>>>> characteristic of the consumer base that will only occassionally be
>>>> doing something requiring the elevated privs.
>>>>
>>>> "Imhotep" <imhotep@nospam.com> wrote in message
>>>> news:cdqdnZDPy9JX_ffZnZ2dnUVZ_tidnZ2d@adelphia.com...
>>>>> "SEATTLE - An annoying surprise awaits 2 million consumers expected to
>>>>> enthusiastically step forward in the next few weeks to help Microsoft
>>>>> test
>>>>> its new Windows Vista PC operating system.
>>>>>
>>>>> Volunteers will test Vista Beta 2, a near-final version of the
>>>>> much-hyped
>>>>> upgrade of Windows. The testing is the last step leading up to Vista's
>>>>> broad consumer release, scheduled for January.
>>>>>
>>>>> Beta 2 testers can expect to encounter an obtrusive security feature,
>>>>> called
>>>>> User Account Control (UAC). Designed to prevent intruders from
>>>>> performing
>>>>> harmful tasks, the feature grays out the computer screen, then prods
>>>>> you to
>>>>> confirm that you really want to do certain functions.
>>>>>
>>>>> In early test versions, the queries crop up