Return
-
Title
Migrate to new SDA -
Description
How to migrate Scripted Installations, System Images, Boot Environments and other KACE SDA (Systems Deployment Appliance former K2000) packages from existing SDA to a new SDA. This procedure covers physical to physical and physical to virtual migrations. The SDA does not have a full backup option to migrate all settings and packages to a new SDA all at once. The supported method of migration is a backup and restore of SDA packages, with a manual transfer of SDA General and Network settings. -
Resolution
Prior to Migration- Evaluate your SDAPackages and note any System Images, Scripted Installations, Pre and Post Installation tasks, Source Media and Boot Environments that are no longer current or needed. Migration is a good time to clear out the system.
- Some customers find the migration to be a good time to start over fresh as well, with brand new images, KBEs or Scripted Installations and only migrate necessary Pre and Post-Installation tasks.
- If using Off-Board Storage with your current SDA, the process is no different. It is not possible to move the offboard storage from one SDA to another. The files must be transferred using the backup and restore method below.
- If using RSAs, please note which packages are sync'd to each RSA and make sure each of these are restored to the new SDA. Additional processes for RSAs during the Migration is below.
NOTE - If choosing to start fresh with images or significantly reduce the number of images on the K2000 during the migration, it may be easier to start over with new RSAs instead of matching packages between the devices.Migration Process
Both the old and new SDA servers can be setup simultaneously, but must have different DNS Hostnames and IP Addresses. Also, if both SDA are online, only the server defined in your DHCP setup will be able to receive PXE boot requests for imaging. Any tests of imaging from the other SDA will need to use a USB boot method or a different DHCP scope.Exporting components from the SDA appliance is an internal task and cannot run in tandem with other internal tasks, such as re-caching drivers, creating scripted installations, or rebuilding boot environments.Attention: The new SDA 6.1 (and higher) - Appliance Migration feature instructions can be viewed from the KACE Kontinuing Education (KKE) Recording: What's New - SDA 6.1 - Appliance Migration (263598) article.
Package Type Recommendations
- Database
- The database can be exported, but not re-imported. It is not necessary to export this.
- Scripted Installations/System Images
- Each Scripted Install and System Image export will contain all the Pre and Post-Installation tasks associated with the image, so migrating these first is recommended. It is also recommended to only export and import these individually, as doing several at once can cause the export process to hang.
- KBEs
- If not planning to change the new SDA to the same IP address and DNS Hostname, or keeping the same SAMBA share password, consider rebuilding the KBE instead of migrating.
- Pre and Post-Installation Tasks not migrated with the images
- After migrating the Scripted Installations and System Images to the new SDA, migrate any of these additional tasks that were not associated with images that you need on the new SDA.
- USMT Templates
- Some users find these easier to set up new instead of migrating. However, these can be exported as outlined below.
- Drivers
- Dell Drivers available in the feed should only be migrated if you have made significant customizations to the packages. Best practice is to download the latest Driver Feed Packages for your current systems and OSs on the new SDA. Procedure for migrating non-Dell drivers will be found at the end of the article.
- Source Media
- If not associated with a specific Scripted Installation, Source Media cannot be migrated. This will need to manually be uploaded to the new SDA.
Export Packages
- On the left navigation pane, click Settings | Package Management to display the Package Management page.
- Click Export SDA Packages to display the Export List page.
- Select only a few components at a time; otherwise, the export cannot complete.
- If the package is green, you cannot export it until you change the version number of the package. Please see KB article 138012 for information on this.
- The selected export items are compressed and placed in the \\SDA_hostname\restore share directory. The SDA appliance creates a .pkg file for each component that you select.
- NOTE: While the export is processing, changing any Network, Security, or Date and Time settings causes the appliance to reboot, terminate the export process, and lock the Exports feature.
- Select Choose Action | Export Selected.
- Ensure that export completes before selecting a different export.
- The packaging process starts. Exporting packages might take a few minutes to several hours to complete depending on the size of the file. The Status column indicates when each export completes.
- NOTE: If the status column shows Completed or Exporting next to each component, but the Currently : status in the upper-right corner displays Idle, contact the Quest KACE Technical Support to access your SDA appliance through the tether and clear the error.
Import Packages
Before you begin, copy the exported packages from the Restore Share of the old SDA to the Restore Share of the new SDA. \\SDA_host_name\restore
- On the left navigation pane, click Settings | Package Management to display the Package Management page.
- Click Import SDA Packages to display the Import List page.
- Select the check box next to the package you want to import.
- Select Choose Action | Import Selected.
- The import process starts. Be sure to allow any import operation to complete before altering any package or database configuration.
NOTE: Depending on the size and number of components in the package, the import process can take several minutes to several hours. Importing images takes longer than exporting images. When you export an image, the appliance locates and packages all of the files associated with that image in to one .pkg file. When the process is reversed, the image files are checked against the K2000 image store to ensure that only new files are uploaded.
Drivers
For non-Dell or customized Dell Driver Feed packages, use this procedure to migrate the drivers.
- Navigate to the \\SDA_hostname\drivers_postinstall directory on the old SDA.
- Copy the folders (except the feed tools folder) of the manufacturer, OS and model systems to the \\k2000_host_name\drivers_postinstall directory on the new K2000.
- Recache the drivers on the new K2000 web interface (Drivers | Choose Action | Manage Drivers | Recache)
Migrate SettingsAfter the packages and drivers have all been migrated to the new SDA, make sure to update the new SDA settings for Users or LDAP settings, network configuration, SAMBA share, boot manager and VNC passwords, and other settings.Remote Site Appliances
During your migration, take note of exactly which packages are currently sync'd to each RSA. Make sure to migrate each System Image, Scripted Installation and KBE that is also stored on the RSAs.Once the migration is complete to the new SDA, connection between the old SDA and RSAs should be broken and the connection to the new RSA completed. Please follow the steps in KB Article 118668 to unlink the RSA from the old SDA and link to the new SDA.