Describes the known issues in the Windows-based User-ID™ agent 8.0 release.
The following table describes known issues in the Windows-based User-ID™ agent 8.0 release.
For recent updates to known issues for a given PAN-OS® release, refer to live.paloaltonetworks.com/t5/Articles/Critical-Issues-Addressed-in-PAN-OS-Releases/ta-p/52882.
When the User-ID agent restarts, it loads the existing IP address-to-username mappings but with an incorrect username value if the username has a space. The ability to fetch IP address-to-username mappings from AD or other sources is not impacted even when usernames have a space.
This issue is now resolved. SeeUser-ID Agent 8.0.8 Addressed Issues.
The Windows-based User-ID agent does not detect users whose account name (sAMAccountName) contains a dollar ($) character that isn't at the end of the name.
Test Connection (MDM IntegrationSetupTest Connection) for the MDM integration service returns a Test Failed message even when the integration service successfully connects to the AirWatch MDM service.
Workaround: Refer to the top-level MDM Integration tab to view the correct connection status.
This issue is now resolved. SeeUser-ID Agent 8.0.3 Addressed Issues.
The MDM integration service of the Windows-based User-ID agent rejects connections from MDM event notification service if the IP Address of the MDM event notification service is not configured as a Permitted IP address (MDM IntegrationSetupPermitted IP).
The Windows-based User-ID agent has a memory leak while running the MDM Integration Service.
The Windows-based User-ID agent frequently resets its connection with a syslog sender, causing the sender to generate numerous connection failure logs and associated alerts.
The Windows-based User-ID agent attempts to contact the certificate store on the agent even though this step is not necessary when hashes match. As a result, authentication fails even for matching hash-es when the certificate store on the agent is inaccessible.
The Windows-based User-ID agent running the MDM integration service can fail during startup and require a restart. This issue is caused by a Windows module (webio.dll) that faults and appears in Windows Event ViewerApplications.
When the PAN-OS XML API sends user mappings with no timeout value to a Windows-based User-ID agent, the agent sets the mappings timeout to never instead of applying the User Identification Timeout setting.
Want to know if there are any issues related to the Windows User-ID™ agent 8.0 release that have been addressed? ...
Want to know if there are any addressed issues related to the Terminal Services (TS) agent 8.0 release? ...
Features Introduced in User-ID Agent 8.0
Review the new feature introduced in the Windows User-ID™ agent 8.0 release. ...
Configure GlobalProtect to Retrieve Host Information
Configure GlobalProtect to Retrieve Host Information Follow these instructions to configure GlobalProtect to retrieve host information from devices managed by AirWatch. Install and configure the ...
Known Issues Specific to the WF-500 Appliance
Known Issues Specific to the WF-500 Appliance The following list includes known issues specific to WildFire® 8.0 releases running on the WF-500 appliance. See also ...
AirWatch MDM Integration
AirWatch MDM Integration The Windows-based User-ID agent has been extended to support a new AirWatch MDM integration service. This service enables GlobalProtect to use the ...
Configure Windows User-ID Agent to Collect Host Information
Configure Windows User-ID Agent to Collect Host Information The Windows-based User-ID agent has been extended to support a new AirWatch MDM integration service. This service ...