Veritas™ System Recovery 18 Service Pack 3 Management Soution Readme
- Veritas System Recovery 18 Service Pack 3 Management Solution Readme
- About this readme
- System requirements for software delivery policies of Veritas System Recovery 18
- System requirements
- What's new in Veritas System Recovery 18 Service Pack 3 Management Solution
- What's new in Veritas System Recovery 18 Service Pack 1 Management Solution
- Features No Longer Supported in Veritas System Recovery 18 Management Solution
- Installing Symantec Installation Manager (as a part of installing Veritas System Recovery Management Solution)
- Known issues
- Updating distribution points for Veritas System Recovery 16, Symantec System Recovery 2013 R2, or LightsOut Restore 2013 R2, packages
- About manually uninstalling packages of Veritas System Recovery 16, Symantec System Recovery 2013 R2, or LightsOut Restore 16 or 2013 R2
- Legal Notice
Compatibility issues
The following are the compatibility issues that you may encounter:
Veritas System Recovery 18 Management Solution does not support Backup Exec System Recovery 8.0, 8.5, 2010, Symantec System Recovery 2011 and 2013 package deployment and client management. You must upgrade Backup Exec System Recovery 8.0, 8.5, 2010, 2011 and 2013 on client computers to Veritas System Recovery 18.
Veritas System Recovery 18 Linux Management Solution does not support management of the client computers that run Backup Exec System Recovery 2010 Linux Edition.
Veritas System Recovery 18 Service Pack 3 supports the VHDX disk type for Physical to Virtual conversion only on Windows 10, 8, 8.1, 2012, 2012 R2, 2016, and 2019 operating system. Veritas recommends that using Veritas System Recovery 18 Service Pack 3 Management Solution, in the Physical to Virtual conversion task, you only assign a VHDX disk type for managed clients with the Windows 10, 8, 8.1, 2012, 2012 R2, 2016, and 2019 operating system. If you assign a VHDX disk type in the virtual conversion task for managed clients with all other operating systems, the VHDX files may not work properly.