Re: For those of you who have disabled UAC while using user/admin, you don't have full admin rights -- <VBG>!


"Paul Montgumdrop" <Paul@xxxxxxxxxxxxxxx> wrote in message
news:e9jVpmAJJHA.5900@xxxxxxxxxxxxxxxxxxxxxxx
Zaphod Beeblebrox wrote:
"Paul Montgumdrop" <Paul@xxxxxxxxxxxxxxx> wrote in message
news:%2391CKh9IJHA.1556@xxxxxxxxxxxxxxxxxxxxxxx
Zaphod Beeblebrox wrote:
You explaine that to me. Why can't I do it as user/admin.
See above. In Vista, an admin user doesn't have permissions to do
everything they did in previous verions of Windows, but still has
the ability to take ownership and change permissions. You'll have
to be a bit more specific for me to be able to comment further.
Unless of course you already have, and don't want to repeat
yourself.

The rest of what you have talked about before this about the block,
I could care less about it.

And I have said all of this above there. And I am also saying that
even if you take ownership in some situations, you're still going to
get *access denied*.

Right, and then you set permisssions on the object (because as the
owner of the object, you have the ability to do that), and all is
well.

Because if it was the case as you indicate when someone takes
ownership then the problems should be resolved. Sometimes that fixes
it and sometimes that does not fix the problem, taking ownership,
because I have seen the posts.

As I said, taking ownership by itself does not necessarily fix
permissions problems. Often, you have to set the permissions after
taking ownership of the object. I've never seen it fail when done
that way, unless it wasn't done properly (and then, doing it properly
fixes it).


Really, all one has to do is add a second user account on the folder
or file and give full rights as like the Administrator group, which
would be the User account of the user/admin that logs into the
machine.

If *Beeblebrox* is the user-id that you login with as user/admin, then
one adds an account named *Beeblebrox* with full rights to the file or
folder, and then the problem is fixed. But that depends on if one can
add *Beeblebrox* as a new user.

Because Vista is looking at one's user/admin accounts as an individual
User and as the user/admin, and it also looks at the user/admin as
being part of the Administrators group.

If the individual user account is not there, it defaults to Users
group rights or neither one of the User or Users group matches the
full rights of Administrators, then it is *access denied*.

And if one can't go to the Creator/Owner account and set permissions,
because Vista is blocking the Vista user/admin account from setting
any account permissions for any account on the folder or file at the
graphical UI, then how is one to expect that what you're talking about
is even going to work at the Command Prompt in some situations on some
files or folders that are protected, like the Program Files and
Windows?


I'm sorry, I've read this 4 or 5 times and still don't think I
understand what it is you are trying to say. I've never mentioned the
command prompt, so I don't even know where that came from, nor have I
mentioned specific folders.

The bottom line is, if you actually _understand_ what is happening in
Vista with respect to folder ownership and permissions, which it is
clear you don't yet, it is simple to make whatever permissions changes
you need as an administrator user even on protected folders your user
and the administrators group don't have permissions to change. Step 1:
Take ownership. Step 2: Assign permissions (making sure to set them for
the group Administrators, if that is what you want, rather than a
particular administrator user).

However, I've never seen the need to do what you are aparently talking
about unless your goal is to undo some of the security barriers put in
place by Vista. Perhaps I'm being thick - not unheard of, that's for
sure.

--
Zaphod

Arthur: All my life I've had this strange feeling that there's something
big and sinister going on in the world.
Slartibartfast: No, that's perfectly normal paranoia. Everyone in the
universe gets that.


.

Relevant Pages