How can I migrate my SmartDeploy Console application from one host system to another?
This article contains screenshots of the SmartDeploy Web Console (see the SmartDeploy Web Console article for more info). The actions described can also be performed in the desktop console.
This article is intended to help you move your existing SmartDeploy Console Application from one host system to another as well as migrate your endpoints to the new SmartDeploy Console host.
Before you begin, confirm that both the SmartDeploy console and its clients are running version 3.0.2048 or newer. These versions include the built-in functionality used to move clients to a new console.
Pre-Migration Planning
Before beginning your migration, ensure the new server meets all SmartDeploy System Requirements. If the servers are on different networks, confirm that network security solutions won't block communication between the console and your deployed clients. Plan the migration during a maintenance window to minimize deployment disruptions.
Migration
Back up your current SmartDeploy directory before continuing (C:\SmartDeploy by default, though yours may be on a different drive). Skipping this step risks permanent loss of your images, packages, and settings if anything goes wrong during the move.
- Configure your new SmartDeploy console system by downloading and installing the Console application.
- Move the files from your previously backed up SmartDeploy directory to the corresponding locations on the new SmartDeploy directory.
- If a library is missing any files, you can bring the files back into the application by "rebuilding the library". Note, you cannot rebuild the library for deployment packages, you will need to recreate deployment packages and boot media. You can read more about when it is necessary to rebuild your SmartDeploy media here: When do I need to re-create my SmartDeploy media?
- Recreate your Answer Files to ensure they have the correct console hostname and are using correct credentials for the new host system.
- In Computer Management select a computer you wish to migrate. Then select the migrate button. Enter the Api Service Url of the new console you want the devices migrated to.
- We highly recommend you start with a single device first to verify that clients are able to reach the new console before pushing this out to a lot of devices at once. Also check out this article to test if clients you are migrating can reach the new console: How can I check whether a client with a Local connection is able to communicate with the SmartDeploy Console?
- We highly recommend you start with a single device first to verify that clients are able to reach the new console before pushing this out to a lot of devices at once. Also check out this article to test if clients you are migrating can reach the new console: How can I check whether a client with a Local connection is able to communicate with the SmartDeploy Console?
This step is irreversible from the old console's side: once the migration deployment reaches the target client, that client stops accepting commands from the previous console entirely.
Legacy method: migrating with the PowerShell script
- See the attached PowerShell script to point existing clients at the new console host. Download the script, open the script in a text editor or PowerShell ISE, and modify the
$servernamevariable to have the new console host system server name (egdesktop-82lqmsbfrom the screenshots). Then save the file as a.ps1file and run it as admin on the endpoints.
Test this script against a small subset of endpoints before rolling it out to larger groups.
