[sternkanz]

I work for a small private company and in the office we have several PCs hooked up to our network. Some log in to their own local machines (like myself) and others log into our domain and have Power User access to their PCs. Recently we had a problem on our secretary's PC. We logged into the administrator account and ran a registry fix program and the problem disappeared. However back on the Power User account the registry fix program was denied access. Is there any way to temporarily allow the account which is set up as Power User to make changes to the registry?

Thanks for any replies!

[cluberti]

Use runas from the command line, would be my suggestion.

[sternkanz]

while this worked to run the program, the program then did a cleanup for the administrator count (or so it seemed) and the power user account is still messed up. I'm looking more for a way to run the program AS the power user.

[cluberti]

Unfortunately, that's not as easy. Registry editing requires ACLs and perms set on the registry and the filesystem that would make the user, basically, an administrator for all intents and purposes. It might be better to change the account type temporarily, make the fix, then switch it back.

[iamtheky]

runas administrator

CACLS %path to folder containing settings that will change% /E /T /C /G "power users":F"

EDIT: (sorry left my runonce info in there which would be no help)

then run it normally as the power user

then remove permissions i suppose.


I believe your problem is power users not being able to modify system wide permission.

But if the changes were system wide they would have appeared when ran as admin, no?

This post has been edited by iamtheky: 05 February 2009 - 03:41 PM