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.
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.
) for the MDM integration service returns a
Test Failedmessage even when the integration service successfully connects to the AirWatch MDM service.
Workaround:Refer to the top-level
MDM Integrationtab 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 IPaddress (
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 Viewer
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 Timeoutsetting.
Recommended For You
Recommended videos not found.