ADEM not reading the Wifi name on endpoint and reporting "Poor connection" for Wifi

ADEM not reading the Wifi name on endpoint and reporting "Poor connection" for Wifi

1242
Created On 01/24/25 10:07 AM - Last Modified 07/18/25 04:02 AM


Symptom


  • Frequent access experience notifications about poor wifi quality being poor even though there is no issue on user's machine and signal strength is excellent.
  • ADEM dashboard doesn't show the Wifi Name (Connected wifi shows Offline).

Connected SSID shows offline 



Environment


  • ADEM (Autonomous Digital Experience Management ) agent
  • Windows 11 24H2 or later


Cause


  • The phyMode will show as  Unknown palo_alto_networks_dem_agent.log
"wlans": [
- {
- "active": true,
- "channel": "44",
- "interfaceId": "{133C717E-547E-4EA0-86BA-717E34660BCD}",
: "phyMode": "unknown 0". <<<<<<<
  • The logs might also show access is denied error.
 [default] [warning] WlanQueryInterface() failed on querying the current connection -- Wifi interface information will be missing. Error: Access is denied.
  • The issue is because the Windows OS denies access to it's wlan interface to the access experience agent.


Resolution


Enable location services for the Access Experience agent:

  1. In Windows, navigate to Settings > Privacy & Security > Location.
  2. Set Location services to On.
  3. Add Access Experience to the list of allowed apps.
  4. Restart the Access Experience agent. Or restart the PC if unsure how to restart the access experience agent only. 
  5. Wait for few hours again and the connected SSID should show the right value with Wifi score showing expected values. 


Additional Information


From the Microsoft docs on the changes in 24H2.

If the user hasn't given consent to precise location access, then the following Win32 APIs in the wlanapi.h header will return ERROR_ACCESS_DENIED:

* WlanGetAvailableNetworkList

* WlanGetNetworkBssList

* WlanQueryInterface (if the argument of OpCode is wlan_intf_opcode_current_connection)

* WlanScan

The agent depend on WlanQueryInterface() internally, and this is one of the reasons why the agent is failing. 



Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000TpY5CAK&lang=en_US&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail