Here are some new features and caveats to be aware of:
- An active maintenance agreement is required for updating the SDA past version 6.1. There are multiple locations throughout the appliance, including the Appliance Maintenance page (Settings | Appliance Maintenance) and Registration and Licensing (Settings | Registration and Licensing) that will display if the license in use is Active or Inactive. If you have an Inactive status, this is generally due to an older license key being used instead of one that has been issued at a later time. Our Licensing team can assist you with obtaining the correct/current license key for your appliance. Please visit https://support.quest.com/contact-us/licensing for assistance.
Once the correct license is entered, the maintenance status will be updated and you can upgrade at your convenience.
- A Backup Integration Services (BIS) check was added for Hyper-V customers in the SDA Status Overview report (Audit Log | Reports | SDA Status Overview) along with some additional SDA details. The BIS setting is a critical setting to verify in order to prevent corruption on your appliance, please see this KB for more information.
- Expanded functionality and customization on the Network Settings page
- Added support for 10 gigabit network adapters
- New wizard to migrate your SDA appliance to another instance (e.g. physical->virtual or virtual->virtual) without needing to go through the export/import process
- User interface improvements to deployment detail pages (e.g. pre/mid/post task filtering, etc)
- Improved deployment performance to physical devices when using WinPE 10 1803 and newer boot environments built with the v6.1 SDA Media Manager
- Images synced to an RSA are now viewable from the RSA web interface
- Once PXE booted, Windows KBEs will display the WinPE and ADK versions used to create them.
- Links to popular Deployment Workbench tools are now available on the Library Overview page and elsewhere throughout the appliance.
- PXELINUX was removed in SDA v6.0.425, so if you are using the k2000.0 or kbox2000.0 boot file, your DHCP configuration will need to be updated to leverage the iPXE boot file(s). Please see this KB for more information.