These release notes document the most recent Skylar Compliance (formerly Restorepoint) 5.6 version maintenance release, followed by previous maintenance release notes, sorted by release date.
Notices:
- Restorepoint has undergone a corporate re-brand and is now known as Skylar Compliance. Going forward, these maintenance release notes document the most recent updates for Skylar Compliance version 5.6.
- Old user interface reports (Information > Reports > ) will be deprecated in upcoming releases. To prevent any data loss, you should migrate any old reports to the new reports (Information > Reports). For more information, contact ScienceLogic Support.
Most Recent Release: 20260326
-
Addressed an issue that prevented device backup transcripts successfully loading from logs.
For more information on Skylar Compliance, see the Skylar Compliance manual and the Skylar Compliance Release Notes.
Previous Issues Addressed
The following issues were addressed in 20260325
-
Added support for shell-style file name wildcard patterns (*, ?, [0-9], ...) and ** to match across directories.
-
Added a Description field to compliance rules, and as an option for relevant report types.
-
Added a Log Transcript checkbox to the tab of compliance policies. When selected, transcripts will be generated for each rule when a backup for the device runs.
-
Added a Transcripts Retention Policy field to the new Compliance Policies section under the tab of the System Settings page. The Transcripts Retention Policy field allows you to define how many days to keep compliance policy transcripts before they are automatically deleted.
-
When testing compliance policies or rules, you can now view the transcript for each rule below the result.
-
Compliance violations for backups are now logged separately (one log entry per violation).
-
Added the progress(string) function to Lua compliance rules. When the progress(string) function is added to Lua scripts, it prints the execution log on the rule transcript.
-
User and administrator allowed networks are now validated continuously. If you start using a restricted network, you will be logged out of Skylar Compliance. (Case: 00617542)
-
If you are an administrator user, and have not set an account recovery question and answer, you will now be prompted to set both after logging in.
The following issues were addressed in 20260311
-
Addressed an issue that caused backup failures due to SSH key management issues following a version upgrade. (Case: 00629409)
-
Addressed an issue that prevented some runtime compliance rules from running during backups and displaying on reports. (Case: 00616153)
-
Updated the Skylar Compliance API documentation to be more clear about the "download" method for some API endpoints.
-
Added new auto-apply filter option types when assigning a policy to a device:
-
Device Name Pattern
-
Agent
-
Label
-
Asset Field
For the Asset Field filter option type, you can select from a list of any custom created "text" and "textarea" asset fields.
-
The following issues were addressed in 20260302
-
Resolved an issue that caused appliances to run out of memory when listing logs.
The following issues were addressed in 20260225
-
Addressed an issue that prevented new variables from being correctly read by compliance rules, which caused errors during rule testing. (Case: 00482948)
-
Addressed an issue that prevented domain users that did not have the "ViewDeviceauth" permission from editing a device. (Case: 00610968)
-
Added paginated search and infinite scrolling to the regular expression (RegEx) global search. Additionally, updated the user interface of the search results header and the grouping of devices and configurations in search results. (Case: 00526431)
-
Added the new Status field to the View Output modal, which displays the count of commands that succeeded or triggered an error. Additionally, the outputs from commands that error or fail are retained and are accessible from the View Output modal.
-
Added the RuleType, Requirement, MatchType, and Value fields to the following reports:
-
Configuration Compliance Full
-
Configuration Compliance Latest
-
Configuration Compliance Summary
-
Compliance Violations
-
-
Added the DeviceLabels field to the following reports:
-
Configuration Compliance Full
-
Configuration Compliance Latest
-
Configuration Compliance Summary
-
Configuration Baselines
-
Current Configuration Baselines
-
Compliance Violations
-
Configuration Changes Summary
-
Backups
-
Assets
-
Compliance Device Passwords
-
-
Added the DeviceName field to the "Backups" report.
-
You can now add additional Info Commands to the "Assets", "Configuration Compliance", and "Configuration Changes Summary" reports.
-
Addressed an issue with device template variables that prevented the same variable from being used multiple times. As part of the fix for this issue, the following improvements were made to variables:
-
Multiple occurrences of the same variable are now tracked and you can see the number of occurrences.
-
You can add selected text as an entry for a variable by clicking under Actions.
-
You can no longer create new variables with the same name as an existing variable.
-
You can no longer mark or insert a variable that overlaps ranges with another variable.
-
You can expand a variable by clicking the arrow icon next to it to view its line number and relative line range.
-
You can mark or insert a variable by clicking on or before the word you want to mark or insert.
-
You can now delete an occurrence of a variable by selecting the occurrence and clicking the trashcan icon under Actions.
-
Hovering your cursor over a variable row will highlight all occurrences of the variable in the template.
(Case: 00561901)
-
The following issues were addressed in 20260211
- Updated the user interface when bulk editing devices to improve performance, scalability, and usability. For more information on bulk editing devices, see the section on Editing Multiple Devices in the Skylar Compliance 5.6 User Guide.
- Changes when bulk editing devices are now validated if you change the domain. If validation fails, an error message is displayed, and a warning message displays next to the fields that must be updated to save the changes.
- Addressed an issue that prevented backups from finishing successfully when "DisableStrictHostKeyChecking" was enabled. (Cases: 00584650, 00614013)
- Updated Device Control commands to more efficiently parse large outputs. This also helps avoid a potential error when running these commands, which could cause the command to end with an "OK" output. (Case: 00592926)
The following issues were addressed in 20260128
- The suggested results of a search on the Devices page now display properly beneath the search box. (Case: 00607713)
- Addressed an issue that caused an error when attempting to download a "Selected file only" configuration backup. (Case: 00540604)
- Addressed an issue that caused users without the "ViewPluginOptions" or "ViewDeviceCommand" permissions to see a "Forbidden" error message when attempting to view a device. (Case: 00606764)
- Addressed an issue that caused the wrong ID to be assigned to firmware uploads during archive and restore. (Case: 00561491)
The following issues were addressed in 20260123
- Addressed an issue where multiple firmware upgrades using the same agent caused the file to be transferred to the agent multiple times. This could lead to situations where the file system of the agent would get full if multiple devices were being upgraded in that agent, or could cause firmware upgrades on multiple devices to take longer than they should. (Case: 00607264)
The following issues were addressed in 20260114
- Added the new button to the tab of the Auth Servers page, which allows you to update the ACS URL and Entity ID fields based on the current URL in the address bar of your web browser. (Case: 00577946 )
- Addressed an issue that prevented the successful display and deletion of backups due to an error when scanning the "contextconfigtypes" database column. (Case: 00603378)
- Addressed an issue that caused reports with multiple filters to filter data incorrectly and return empty reports. (Case: 00596935)
- Addressed an issue that prevented an Until date from being selected when configuring the Disabled option on the tab of a device. This issue occurred when the timezone of your web browser was set to any option west of Coordinated Universal Time (UTC). (Case: 00589626)
- Addressed an issue that prevented command timeouts from being applied correctly when running commands as part of a backup. (Case: 00560244)
- Addressed an issue with the Skylar Compliance API that prevented the "DisableStrictHostKeyChecking": true flag from functioning correctly when making an API request to create a device. (Case: 00595624)
- The "DisabledReason" will now be displayed properly when pulling a list of all devices. (Case: 00595624)
The following issues were addressed in 20251231
- Addressed an issue that prevented correct response from the Skylar Compliance API when using the "LastSuccessfulBackup" and "LastSuccessfulBackupID" field filters. (Case: 00593869)
- Set the default temporary directory used by some packages to the one defined by Skylar Compliance. This change only affects agents.
Installing or Upgrading Skylar Compliance
For detailed steps about installing or upgrading to this version of Skylar Compliance (formerly Restorepoint), see the Installing Skylar Compliance chapter in the Skylar Compliance manual.
You should always upgrade to the most recent release of Skylar Compliance.