Database Search
TechHome
- !! Understanding UAC !!
- A Referral was Returned From the Server
- Admin Privilege OK in WinBatch, but not Compiled
- Cmd Prompt Run As Administrator
- Determine if Application is Elevated
- Elevation Level and Environment Varibles
- FileCopy and UAC
- Installation Scripts
- Installing a program using Compatibility Mode
- Mapped Drives Issue with UAC
- Protected Directories
- Run As Admin WinBatch Script With UAC On
- RunWithLogon and UAC
- Scheduled Tasks
- SendKey and UAC
- Signing and Certificates
- StartUp No Prompt
- UAC Administrator Account
- UAC and WinBatch Studio
- UAC Help
- UAC Local System Account
- Unknown Publisher
- wntAccessAdd 64-bit Registry Key
- wntRunAsUser Issues
- wntShare UAC Problem
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
wntRunAsUser Issues
Keywords: wntRunAsUser Issue Bug Problem Elevate Escalate UAC Vista Win 7
Important: On Windows Vista/2008 or newer, wntRunAsUser cannot be use to escalate ( or elevate) privileges.
It can be used to if you are logged in as an administrator and you want to (de-escalate) to a standard user. Make sure you don't elevate to full administrator privileges before you run the script. If you elevate first, wntRunAsUser basically doesn't lower your privileges and the process continues to use your administrator privileges.
Windows 7 Strangeness
Windows 7: When UAC is on, a standard user can specify Administrative credentials but the script will still only act as a standard user. When UAC is off, a standard user can specify Administrative credentials but privileges actually get reduced to less than a standard users (anonymous impersonation.) This causes simple operations such as FileExist to fail.
Article ID: W18330
Filename: wntRunAsUser Issues.txt
File Created: 2011:08:19:12:57:26
Last Updated: 2011:08:19:12:57:26