How to migrate System Deploy Appliance (SDA) using packages (4232606)

This KB article assumes the reader understands, how to manage virtual machines within Nutanix, VMWare VSphere, or Microsoft Hyper-V.

Quest only supports the platforms mentioned above. For support about vSphere, Nutanix or Hyper-V, contact VMWare, Nutanix or Microsoft accordingly.

For further information about Virtual KACE SDA and RSA host system requirements click here.

*** Important: Carefully read each step before moving to the next one. ***

A. Export the packages from the old SDA

1. From the SDA webui, go to Settings | Package Management | Export Packages
2. Select the packages to be exported, then Choose Action | Export Selected
   Note: While exporting, the SDA appliance cannot re-cache drivers, create scripted installs, or rebuild boot environments.
   Additional Information Do not export all packages at once. Select a few items at a time, or your Exports will not be completed.  Ensure Exports are complete before selecting your next Export.
3. Once the packages are exported, open a Windows File Explorer, go to SMB \\SDA_hostname\restore, and back up all XML and PKG files.
   *** If not able to access SMB share, see the following article ***
4. After exporting all the packages, Shutdown old/physical appliance

B. Deploy Hyper-V/VMware/Nutanix virtual template

1. Download the Hyper-V/OVF installation package from the Support Portal Releases page (update the appliance to match the version of the old one if needed.)
2. Follow the setup guide for VMWare, Nutanix, or Hyper-V accordingly.

                In this article, KACE Support lists all best practices for KACE Appliances running on Hyper-V.

C. Import the packages to the new virtual SDA

1. Copy the exported files from the backup location.
2. Open a Windows File Explorer and go to SMB of the new SDA: \\SDA_hostname\restore and paste all XML and PKG files
3. Go to Settings | Package Management | Import Package
4. Select the packages to be imported, then Choose Action | Import Selected (import packages in groups just as they were exported).
   
   Hyper-V important information: If deploying the appliance on a Hyper-V host, please this article.