New agents are added to a correct subnet, but with a different subnet name

If new agents on the same subnet are added after renaming the subnet, they are automatically added, but to a to a duplicate subnet

(with the original, automatically generated subnet name)Renamed automatic networks groups reappear with original name

Symptoms: When an automatically generated network group is renamed under Administration / Agent / Groups and a new agent is added to the same network, the original Automatic Network Group name shows up in the list next to the renamed one.  

Temporary hotfix available. The bug will be fixed in a new build as soon as possible.

Hotfix:

• Download and unzip the hotfix .jar file link mangler stadig <link>
• Stop the ??? service in Windows Service Manager
• Rename the ???.jar file in the ??? directory
• Copy the downloaded .jar file (overwrite) into the ??? directory
• Start the ??? service again in Windows Service Manager

Frontend Server stops communicating, first with Backend, then after a while

Symptoms: The Performance Guard Frontend Server Service first stops communicating with the with the Performance Guard Backend Server, which will increase the memory usage on the Frontend Server. After a while the Frontend Server stops receiving data from agents and the agents goes offline indicated by a gray Agent icon in the tray.Some customers may experience unusually high memory consumption from the Frontend Service (up to 1 GByte)

Running this script file is a temporary workaround.  The bug will be fixed in a new build as soon as possible.

Hotfix:

• Download and unzip the hotfix file link mangler stadig <link>
• Logged in as administrator on a Frontend Server, run the hotfix batch file with administrative rights (Run as Administrator)

Running this script file is merely a temporary workaround. A patch for the error will be released as soon as possible