Editing UAC

Is it possible to edit how UAC works using the Home Premium Edition? (like
using secpol.msc on some editions)

You can hack the registry directly. I don't know if gpedit.msc is there. You
may also be able to add the Security Policy Editor into a blank MMC instance,
but I don't have a copy of Home Premium handy to tell.

What do you want to achieve?

"Jaren" wrote:

> Is it possible to edit how UAC works using the Home Premium Edition? (like
> using secpol.msc on some editions)

I'm trying to disable UAC on certain folders that I access frequently (inside
Program Files), so I don't have to confirm the action every time I add new
files into my web page folder or any programs I might be working on.

"Jesper" wrote:

> You can hack the registry directly. I don't know if gpedit.msc is there. You
> may also be able to add the Security Policy Editor into a blank MMC instance,
> but I don't have a copy of Home Premium handy to tell.
>
> What do you want to achieve?
>
> "Jaren" wrote:
>
> > Is it possible to edit how UAC works using the Home Premium Edition? (like
> > using secpol.msc on some editions)

> I'm trying to disable UAC on certain folders that I access frequently
(inside
> Program Files), so I don't have to confirm the action every time I add new
> files into my web page folder or any programs I might be working on.

UAC is all or nothing. It is not like setuid. You cannot disable it per
binary or per folder.

In message <CAA58F98-226D-459A-AAF4-2B7F469E7EAA@microsoft.com> Jaren
<Jaren@discussions.microsoft.com> wrote:

>I'm trying to disable UAC on certain folders that I access frequently (inside
>Program Files), so I don't have to confirm the action every time I add new
>files into my web page folder or any programs I might be working on.

Check the NTFS permissions, explicitly include yourself, rather then
just the "Administrators" group.
--
Insert something clever here.

> >I'm trying to disable UAC on certain folders that I access frequently
(inside
> >Program Files), so I don't have to confirm the action every time I add new
> >files into my web page folder or any programs I might be working on.
>
> Check the NTFS permissions, explicitly include yourself, rather then
> just the "Administrators" group.

That will work, but making wholesale changes to ACLs on OS binaries is
generally not a very good idea. See KB 885409
(http://support.microsoft.com/kb/885409) for more details. I've seen
customers destroy tens of thousands of systems that way.

Pin-point ACL changes on specific files is usually fine though, as long as
you realize the risk you are creating by doing so.

Good idea in general.

In message <F1B76247-DC53-47F8-A143-9E19FF9EAD61@microsoft.com> Jesper
<Jesper@discussions.microsoft.com> wrote:

>> >I'm trying to disable UAC on certain folders that I access frequently
>(inside
>> >Program Files), so I don't have to confirm the action every time I add new
>> >files into my web page folder or any programs I might be working on.
>>
>> Check the NTFS permissions, explicitly include yourself, rather then
>> just the "Administrators" group.
>
>That will work, but making wholesale changes to ACLs on OS binaries is
>generally not a very good idea. See KB 885409
>(http://support.microsoft.com/kb/885409) for more details. I've seen
>customers destroy tens of thousands of systems that way.
>
>Pin-point ACL changes on specific files is usually fine though, as long as
>you realize the risk you are creating by doing so.
>
>Good idea in general.

True -- If you're not really careful this could open a hole in UAC too.

I'm just pointing out that there is nothing special about the "Program
Files" directory which kicks off UAC, but rather, simply the elevation
required to write as a member of the "Administrators" group.
--
Insert something clever here.

Thanks a lot guys,
I'm gonna give it a shot now since I don't have anything irreplaceable.
Thanks again for all the help.

"DevilsPGD" wrote:

> In message <F1B76247-DC53-47F8-A143-9E19FF9EAD61@microsoft.com> Jesper
> <Jesper@discussions.microsoft.com> wrote:
>
> >> >I'm trying to disable UAC on certain folders that I access frequently
> >(inside
> >> >Program Files), so I don't have to confirm the action every time I add new
> >> >files into my web page folder or any programs I might be working on.
> >>
> >> Check the NTFS permissions, explicitly include yourself, rather then
> >> just the "Administrators" group.
> >
> >That will work, but making wholesale changes to ACLs on OS binaries is
> >generally not a very good idea. See KB 885409
> >(http://support.microsoft.com/kb/885409) for more details. I've seen
> >customers destroy tens of thousands of systems that way.
> >
> >Pin-point ACL changes on specific files is usually fine though, as long as
> >you realize the risk you are creating by doing so.
> >
> >Good idea in general.
>
> True -- If you're not really careful this could open a hole in UAC too.
>
> I'm just pointing out that there is nothing special about the "Program
> Files" directory which kicks off UAC, but rather, simply the elevation
> required to write as a member of the "Administrators" group.
> --
> Insert something clever here.
>