Can you please explain how the RunAsAdmin, Run As Invoker, and RunAsHighest Shims work? I am new to ACT.

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1

RunAsInvoker: The application should run with the same Windows privileges and user rights as the parent process. This setting is the equivalent as not having an application compatibility database for the application. The application launches with the same privileges as the parent process launching it, which reduces the application’s security exposure. This is because for most applications, the parent is Explorer.exe, which runs as a Standard User application.

RunAsHighest: The application should run with the highest Windows privileges and user rights the current user can obtain, but the application does not necessarily require the user to be an administrator. The application can be run by both administrators and standard users, and it adapts its behavior based on the user’s privileges and user rights. The application requires privileges and user rights greater those of a standard user, but it does not require the user to be a member of the local Administrators group.

RunAsAdmin: The application should run only for administrators, must be launched with a full administrator access token, and will not run correctly in a standard user context. This requested execution level marking is reserved for pre-Windows Vista applications that require the user to be a member of the local Administrators group.

Answered 10/08/2012 by: jagadeish
Red Belt

  • This content is currently hidden from public view.
    Reason: Removed by user request
    For more information, visit our FAQ's.
  • we are getting the UAC prompt(While launching the shortcuts) in the Admin mode only, then what , shim does actually in the backend....Please explain
Please log in to comment
Answer this question or Comment on this question for clarity

Share