[PG-9085] - IE filter must be case in-sensitive
[PG-9020] - The agent occasionally connects a wrong NIC
[PG-8944] - High retransmissiontime
[PG-8683] - Double agent detection across multiple frontend servers defect
[PG-8146] - In rare cases the agent uses 100% CPU
- [PG-9357] - Techmanual CustomCounters section shall be updated
Furthermore, an issue has been discovered, where e-mails with reports do not get sent out. Instead the report e-mails queue up on the backend server.
This issue is caused by non URL-safe characters in the short report name.
To fix this issue, edit the short name of the report, so it does not contain characters, that will not work in a URL (space, etc)
Either delete the unsent e-mails from the database table pguard.notificationlist, or alter their 'parameter' in the DB, so the filename does not contain illegal (in URLs) characters, and corresponds to the filenames, that must also be edited.
An issue has been discovered, which results in missing database updates, when upgrading from earlier versions. This issue does not affect fresh installations of Performance Guard 6.3.104.
Users affected from this upgrade glitch will experience empty CPU Usage Charts (no values are graphed).
Hotfix:
Log in to your Frontend SQL database with credentials for the frontend.
Execute this script: (can be downloaded here)
EXEC ('alter table agent_total_counters alter column paging_low_free bigint')
EXEC ('alter table agent_total_counters alter column paging_average_free bigint')
EXEC ('alter table agent_total_counters alter column virtual_memory_low bigint')
EXEC ('alter table agent_total_counters alter column virtual_memory_average bigint')
EXEC ('alter table agent_total_counters alter column peak_context_switches bigint')
EXEC ('alter table agent_total_counters alter column average_context_switches bigint')
This hotfix must be applied to all your existing PG Frontend servers.