or is there a way to turn on UAC warnings for the built in Administrator without having prompts for std. user acc using the shortcut with admin privil. ?
Resumee: I want to use only ONE admin account which I use with UAC on and have shortcuts (with the privl. of this admin) for std. user acc. without prompts
but I expect a standard account using a shortcut with this elevated admin account will get the prompt as well
If you elevate your normal admin account, you will no longer get a UAC prompt just like the built-in Administrators.
The standard user will not get prompted by UAC when using the elevated shortcut since the shortcut uses the credentials of the elevated admin account instead of the standard user's.
Quote: Originally Posted by 5ggggg
or is there a way to turn on UAC warnings for the built in Administrator without having prompts for std. user acc using the shortcut with admin privil. ?
Resumee: I want to use only ONE admin account which I use with UAC on and have shortcuts (with the privl. of this admin) for std. user acc. without prompts
No. The key to this is an "elevated" administrator account so that the standard user will not be prompted by UAC using that account's credentials.
As a workaround, try elevating your normal admin account first to create the shortcut using your account's password instead of the built-in Admin to see if it'll work for the standard user or not.
If not, then you will be stuck having to use the built-in Administrator as per the tutorial instead of the workaround.
just trying to elevate my normal admin under Windows 7/8 ... I found,
ConsentPromptBehaviorAdmin=5 where the default is 2 in vista
ConsentPromptBehaviorUser=3
I am logged into my normal admin account:
when I start the "runas shortcut" using my normal admin (in the runas) with elevated rights, I get the message "you are not allowed to write to the registry" which i also get when I start my program without saying "start as Administrator"
It won't work if you just copied it over from Windows 8. Even if you modified it.
You have to start completely from scratch in Windows 7 using the built-in Administrator account from Windows 7. Since you already tried it, you will need to use a new name for the shortcut as well.
new shortcut created from the built in Admin (which is renamed) ... not working ... when I take the code to a admin CMD window it asks me to enter the Builtin Admin PWD and then it shows the above error