In this blog post, we will test an Intune Settings catalog policy Prevent access to the command prompt(User). Enabling this setting and deploying it to Intune-managed windows devices will disable/block/prevent access to command prompt for the current user.
There is an additional setting you will have to configure along with this is Disable the command prompt script processing also? (User). This setting controls whether execution of batch scripts or login scripts (that requires command shell for execution) should be blocked as well.
Most commonly this should be set to No. However, if you want to take block all approach, you can block the command prompt access and also block .bat or .cmd scripts execution, in that case you can select Yes.
Block Command Prompt using Intune Policy
- Sign in to the Intune admin center > Devices > Configuration > Create > New Policy.
- Platform: Windows 10 and later
- Profile type: Settings Catalog
- Basics – Provide a Name and Description of the Profile.
- Configuration settings – Click on + Add settings and search for the command prompt in the settings picker. Select Prevent access to the command prompt(User) to configure.
- To enable it, toggle the switch to Enabled for prevent access to the command prompt(User) setting. This will not allow users to launch the Command prompt on their device.
- Disable the command prompt script processing also? (User) – Set this to No.
- Assignments – Assign this profile to an Entra security group containing users/devices.
- Review + create – Review the profile settings and click on Create.
Sync Intune Policies
The device check-in process might not begin immediately. If you’re testing this policy on a test device, you can manually kickstart the Intune sync from the device itself or remotely through the Intune admin center.
Alternatively, you can use PowerShell to force the Intune sync on Windows devices. Restarting the device is another way to trigger the Intune device check-in process.
Monitoring Deployment Progress
- Sign in to the Intune admin center > Devices > Configuration.
- Choose the Device Configuration profile you want to work with, and at the top of the page, you’ll see a quick view of the Success, Failure, Conflict, Not Applicable, and In Progress status.
- Click on View report to access more detailed information.
End User Experience
Once this policy has been successfully applied on target devices, when users launch the command prompt from the start menu or using the Run dialog box, they will receive the message below in the command prompt window.
The command prompt has been disabled by your administrator. Press any key to continue.
Open registry editor and navigate to HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\System. On right-hand side, find a Dword entry called DisableCMD which should be set to 2.
If DisableCMD value is 2, this will allow batch files execution on the device and If its set to 1, that means you must have configured Disable the command prompt script processing (User) setting to Yes, which does not allow execution of batch files on the device.
FAQs
What is the OMA-URI setting for blocking Command Prompt?
./User/Vendor/MSFT/Policy/Config/ADMX_ShellCommandPromptRegEditTools/DisableCMD.
Use a String data type and provide the below value. Set a value of 2 to block command prompt access, and a value of 1 will block command prompt access and execution of batch and cmd scripts.
<enabled/>
<data id=”DisableCMDScripts” value=”2″/>
Registry Key for blocking Command Prompt access for all users on a device
As discussed earlier, the registry key is HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\System, and a DWORD entry DisableCMD of value 2 will block Command prompt access. Setting it to 1 will also block batch file .cmd script file execution along with command prompt access.
Where can I find logs related to the Device Configuration Profile?
– Press the Windows key + R to open the Run dialog box
– Type eventvwr and press Enter to open Event Viewer.
– Go to Application and Services logs > Microsoft > Windows > Devicemanagement-Enterprise-Diagnostics-Provider > Admin folder.
– Search for Event ID 813 or 814 and go through the logs to find the one related to the deployment.
I want to read more about DisableCMD Policy Setting.
You can read more about it at the link: ADMX_ShellCommandPromptRegEditTools Policy CSP – Windows Client Management | Microsoft Learn
