- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
03-25-2025 08:26 AM
We are facing an issue where we have Visual Studio running elevated on our developers workstations but they are unable to end the task if it becomes unresponsive. This can be become a pain when debugging. They have asked if we can have Task Manager run elevated, so they have the ability to end Visual Studio if it is hanging. I would like to avoid this as running Task Manager elevated essentially gives them full admin through the Run New Task option in Task Manager. Any ideas on how we can workaround this issue?
03-25-2025 09:49 AM
Though not a full answer we lockdown Visual studio run as admin for security reasons so to elevate users need to be in the AAD group, I guess mostly because you can load CMD/Notepad++ from it, also helps us control and reduce risk, you could obviously create an advanced policy if you don't apply AAD groups to epm policy as we do, what about creating an advanced policy for Task Manager so only those users can elevate it in order to shutdown VS by targeting the policy to those who have VS installed via Targets ? not the full answer will be curious to know if you can block RUN esp with the tickbox run as admin available when you elevate Taskmgr.exe?
Option 1: Create a Targeted Elevation Policy for Task Manager
You can create an advanced application policy in EPM that elevates Task Manager but with restrictions:
While this doesn't directly disable the "Run New Task" option, it can help limit what can be executed through it.
and not sure if it's applicable to task manager RUN AS - but you can remove the RUN as via - Hide Windows "Run As..." Menu Items: In the Agent Configuration settings, there's a specific parameter called "Hide Windows 'Run As...' menu items" that can hide standard Run As and Run as Administrator items from the Windows context menu.
03-25-2025 09:49 AM
Though not a full answer we lockdown Visual studio run as admin for security reasons so to elevate users need to be in the AAD group, I guess mostly because you can load CMD/Notepad++ from it, also helps us control and reduce risk, you could obviously create an advanced policy if you don't apply AAD groups to epm policy as we do, what about creating an advanced policy for Task Manager so only those users can elevate it in order to shutdown VS by targeting the policy to those who have VS installed via Targets ? not the full answer will be curious to know if you can block RUN esp with the tickbox run as admin available when you elevate Taskmgr.exe?
Option 1: Create a Targeted Elevation Policy for Task Manager
You can create an advanced application policy in EPM that elevates Task Manager but with restrictions:
While this doesn't directly disable the "Run New Task" option, it can help limit what can be executed through it.
and not sure if it's applicable to task manager RUN AS - but you can remove the RUN as via - Hide Windows "Run As..." Menu Items: In the Agent Configuration settings, there's a specific parameter called "Hide Windows 'Run As...' menu items" that can hide standard Run As and Run as Administrator items from the Windows context menu.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

