This article describes an issue where SCNotification (part of SCCM) will prompt a message of "SCNotification.exe has stopped working" after lock down mode is enabled for the Pulse Secure Desktop client.
Problem or Goal
After enabling lock down mode for Pulse Secure Desktop client, Windows user may be prompted with the following message:
SCNotification.exe has stopped working
This issue occurs due to lock down mode is designed to block all network connectivity unless connected to a VPN tunnel. Since SCNotification is not part of the exception list, SCNotification.exe is not allow to bind to a socket and causes the application to stop working.
Pulse Secure will add SCNotification.exe to the exception list in a future release. As a workaround, Pulse Connect Secure administrator can manually add the SCNotification program and port to the exception list to help avoid the message.
Login to the admin console
Navigate to Users > Pulse Secure Client > Connections
From the list, select the applicable connection set
Under the Lockdown mode exception rules, click New
In the Name field, enter a friendly name
Select the radio button for Inbound
Under Resources, select the radio button for Custom
In the Program path field, enter C:\Windows\CCM\SCNotification.exe
From the Protocol drop-down menu, select TCP
In the Local IPV4/IPV6 Resources and Remote IPV4/IPV6 Resources, enter 127.0.0.1