Skylar Compliance RPM Agent v5.6 20251119 is Released
Hello, We are pleased to announce the release of Skylar Compliance RPM Agent version 5.6 20251119. This release contains the rebranding updates (see IMPORTANT below) and addresses multiple issues including Addressed an issue that caused an error to display in the agent logs when attempting to insert a job into the database. (Case: 00575046) Addressed an issue that caused backups to fail incorrectly when the "Disable SSH Strict Host Key Checking" option was enabled. (Case: 00577892) Addressed an issue that prevented agents from updating properly and caused them to leave nonfunctioning processes behind during updates. (Case: 00574638) IMPORTANT: Please note that this version of the RPM Agent is rebranded, using the Skylar Compliance product name. Specific actions are required to view the rebranding changes. Please follow the instructions for your appliance settings. Online appliances with auto updates ON. No manual update action is needed, however, you must clear your browser cache to see the new branding changes. Online appliances with auto updates OFF. You must apply the update manually and then clear your browser cache to see the new branding changes. Offline appliances. You must update through your offline process and then clear your browser cache to see the new branding changes Refer to the latest Release Notes for more information about the Agent and the appliance. Thank you, Release ManagementRestorepoint RPM Agent 5.6 20250925 Release
Hello, We are pleased to announce the release of a hotfix for the Restorepoint RPM Agent. The Restorepoint RPM Agent 5.6 20250925 release addresses an issue that prevented RPM agents from using back connections after a restart. Note the following if you are using the back connection feature on a RPM agent: After installing this RPM update, then update your agentconf.json file, and add in the plain text BackConnectionPassword password. Remove the EncryptedBackConnectionPassword entry. After updating your agentconf.json file, then restart the rpagent. After the restart, the back connection password will get encrypted, and the feature will be working as intended. Thank you, Release Management
