Prevent users from running certain programs or applications on Windows endpoints using Intune

-
 

When it comes to blocking or preventing users from running an application on Windows devices, one normally uses App locker policy, Windows Defender Application Control and not so new but pretty useful method called Defender Vulnerability management within Microsoft 365 Defender Portal. A recent question on the Tech Community Microsoft forum prompted me to look for all possible alternatives. I started reminiscing over the legacy GPO policies and that is when I stumbled upon the policy Don’t run specified Windows applications located under User Administrative Templates -


The policy setting does come with its own caveat -

"This policy setting only prevents users from running programs that are started by the File Explorer process. It does not prevent users from running programs, such as Task Manager, which are started by the system process or by other processes. Also, if users have access to the command prompt (Cmd.exe), this policy setting does not prevent them from starting programs in the command window even though they would be prevented from doing so using File Explorer"

So if you have to implement this, make sure you are aware of the limitations as stated above. However, if you are ok with restricting access to cmd.exe, then it becomes comparatively easy enough to implement this as oppose to App locker and other alternatives as mentioned before.

So how does one configure this using Intune? Well let's find out -

2. Browse to Devices – Windows – Configuration Profiles.
3. Click Create Profile.
4. Select Platform as Windows 10 and later.
5. Select Profile as Settings catalog.
6. Provide a Name and hit next.
7. Click on Add settings.
8. Search for 'Windows applications' and select 'Don’t run specified Windows applications' as shown below.


9. Add the necessary application process executables and assign to a device or user based group.


End User Experience

Once the policy is assigned, the setting will come into effect and the user will see the following message on running both cmd.exe and chrome.exe


The enforcement of the policy can be validated in eventvwr.


The policy will also create a DisallowRun registry under HKCU.


Last but not the least, the compliance of the policy can be tracked in Intune.



Until next time..

Comments

  1. AnonymousAugust 28, 2023 at 5:06 AM

    Thank you for this great guide, this will be very useful. Do you have any recommendations on an easy rollback incase users are required to use blocked applications in the future?

    ReplyDelete
    Replies
    1. Rahul JindalSeptember 1, 2023 at 8:45 AM

      I haven't tested the rollback, but if the CSP allows removal action, then removing the policy may just work. Otherwise, the only other workable option I see is getting rid of the registry through a script.

      Delete
  2. AnonymousMarch 27, 2024 at 11:50 PM

    thanks for the guide!

    ReplyDelete

Post a Comment

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

-
Image
Every now and then it so happens that BitLocker recovery keys do not escrow in AAD. The usual culprits are incorrect BitLocker policies and\or the device hardware configuration failing to meet the minimum requirements. The other scenario and something I recently experienced is when everything is setup right and still the recovery key doesn’t escrow in AAD. As I understand, this can happen if the escrow process got interrupted the first time due to network or local devices related issues and the process could not resume. To circumvent this issue, one can simply push a PowerShell script to the devices to force the escrow of the recovery keys to AAD. Here is a script to do so. try{ $BitlockerVol = Get-BitLockerVolume -MountPoint $env:SystemDrive         $KPID=""         foreach($KP in $BitlockerVol.KeyProtector){             if($KP.KeyProtectorType -eq "RecoveryPassword"){                 $KPID=$KP.KeyProtectorId                 break;             }         }        $o
Read more

Intune: Configure Printers for Non-Administrative Users

-
Image
Configuring printers for end users or giving them the ability to do it themselves is a normal requirement for organizations. Now if your users are Administrators, then the configuration can be straight forward, but in case of Non-Administrators there are additional steps required as Non-Administrators will not be able to add a driver in the driver store despite being able to install a printer. In this blog, I will cover the steps that I took to address this requirement using Intune. The setup involves 2 steps -  1. Setup registries. 2. Install the driver and configure the printer Setting up registries – The registries that need to be configured are actually part of a GPO setting – Allow non-administrators to install drivers for these device setup classes It can be found under: Computer Configuration -> Policies -> Administrative Templates -> System -> Driver Installation I used a Powershell script to set the values and wrapped it in a Win32 application. $Path1
Read more

Intune: UAC Elevation Prompt Behavior for Standard Users

-
Image
Implementing and maintaining a good security posture is an integral part of overall IT security governance for most organizations now. While you want to harden the security of infrastructure and give least number of privileges to your end users, sometimes you may need to cut back on the restrictions to ensure a good user experience and an effective IT support process. Recently, I had a requirement where the customer wanted to ease the restriction on the end user devices to make the helpdesk support process more efficient. This involved easing the UAC level access for the Standard users and if you are managing your devices using Intune, then this blog may just help you. Let us see what all is involved and some of the ways that you can use to implement this easily. Policy CSP – LocalPoliciesSecurityOptions LocalPoliciesSecurityOptions has many CSP settings and if you are managing these settings at an individual level, then the CSP that we need to concern ourselves with here is U
Read more