Reset Search



TN40108 - Wireless Suppression fails when wireless Group policy objects (GPOs) are used

« Go Back


Last Modified Date12/21/2015 8:26 PM

Pulse desktop is unable to suppress any wireless profile deployed via GPO. Any wireless profile suppressed by something other than Pulse can not be launched by Pulse.

The presence of any wireless polices deployed via GPO will prevent Pulse from suppressing  wireless at all, even those profiles not deployed via GPO, other errors may also occur.

There is a simple way to determine if a wireless profile was deployed via GPO. In the Pulse debug zip file go to the Network directory and open the netshwlan.txt file and scroll down to Show Profiles

============================= SHOW PROFILES ===========================

Profiles on interface Wireless Network Connection:

Group policy profiles (read only)

As you can see in the example above the wireless profile Test was deployed via GPO.


To determine if there are any wireless policies present on a workstation check for the presence of the following registry key:


If present there is likely a wireless policy on the device. From a command line, you may use the following command to export all the GPO data to a text file for review:
gpresult /v >C:\gpoexport.txt

Keywordswireless suppression, GPO, Group Policy Object
Upgrade Pulse Desktop to 5.2R2 or later which has a feature to overcome this issue. 

The 8.2R3 PCS, 5.3R3 PPS and 5.2R3 PDC What's New Document describes it as:

Support for Wireless Suppression with GPOs (5.2r2)
• The Pulse Secure desktop client can now disable wireless adapters when a wireless adapter is active – even when Group Policy Objects (GPOs) are used for wireless configuration of Windows devices.

For Pulse Desktop versions earlier than 5.2R2 the following options are available:

Options for wireless profiles

1. Remove the GPO.

Options for wireless policies

1. Remove the GPO.
2. For immediate functionality while not connected to the network containing the domain controller, you may delete the registry key with the wireless policy. Caution should always be used when modifying the registry.
External ID
Attachment 1 
Attachment 2 
PurposeTroubleshooting; Interoperability



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255