AppLocker runas not working for standard user


I'm implementing AppLocker site wide within the weeks end. I noticed in testing that I cannot runas other user using an elevated account while logged in with my standard user account. The logon prompt repetitively says Access Denied even after stopping the service and rebooting. It works obviously on another server

Is this by design?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Please clarify. What are you trying to do?
The functionality "run as a different user" does not imply elevation, even if that user is an admin - that could be your misunderstanding. What implies elevation is "run as administrator".

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
snyderkvAuthor Commented:
Trying to do: Runas administrator on a non administrative logon

The user is not an administrator but should still work regardless and not send access denied in the user credential box
I see. The message "access denied" is not originating from applocker. Applocker would talk about "This app has been blocked by your system administrator". Or what exact message is it?
If in doubt, open eventvwr.msc and look at the applocker event log to see what happens meanwhilst access is denied.
snyderkvAuthor Commented:
Didn't realize that there was a local policy set to "Don't elevate standard users". As McKnife said Runas different user does not elevate the elevated account. What's weird though is some machines get the same AppLocker "blocked by group policy" error when trying to runas administrator from a standard account.  I attributed this to denying elevate to standard users in the security options of a GPO. Thanks AppLocker for not changing the wording around at all making me think we had an AppLocker bug.

McKnife, I do need your help in another thread regarding publisher rules
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.