Known Issues

• Currently, on MSP endpoints, ShadowControl's Push Install issues the perpetual license version of the agents rather than the MSP version To avoid this, manually update MSP-licensed endpoints to the MSP version.
• Push install backup jobs fail on a Windows endpoint until the endpoint reboots. (This is normal ShadowProtect behavior after a new install.) Once rebooted, ShadowProtect runs the backup job at its next scheduled runtime and then performs a Full backup. In other words, the Full backup does not start immediately after the endpoint reboots.
• An SPX job policy that uses the All Volumes option might detect an external USB drive when it is attached and dynamically add it to the SPX job. This can impact SPX backup performance. Removing and reconnecting this external drive may result in SPX performing a DiffGen incremental rather than a simple incremental when processing this drive's volumes.
• A few strings might not be localized.
• Reassigning an endpoint to a new policy might not start a new full backup at its scheduled time. The workaround is to unsubscribe and then re-subscribe the endpoint to the appliance.
• ShadowControl reports a multi-volume backup job as completing successfully if at least one volume backs up successfully, even if one or more volumes actually fail to back up.
• ShadowControl does not properly recognize the ShadowProtect 5.x MSP trial license, so it does not display the remote activation option in Endpoint Details.
• Subscription and API Tokens might not expire on the date specified.
• ShadowControl does not properly notify of an expired SPX trial license. The license status sticks at "Expiring soon".
• Updating a CSV source which already has scheduled an active push install will cancel all pending endpoint installs. Installs that have already started will complete normally