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. Make sure that both the Smartdeploy conosle, and clients are on version 3.0.2030 or newer first.
- Make a backup of your current SmartDeploy directory (Note C:\SmartDeploy is the default but you could be using D:\ or E:\SmartDeploy)
- 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?- Once this deployment is pushed to the target client computer. The client will no longer be able to receive commands from the old console.
- Once this deployment is pushed to the target client computer. The client will no longer be able to receive commands from the old 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.
Legacy Steps with the attached script:
- See the attached PowerShell script to assist with that. Downoad the script, open the script in a text editor or PowerShell ISE, and modify the $servername variable to have the new console host system server name (eg desktop-82lqmsb from the screenshots). Then save the file as a .PS1 file and run it as admin on the endpoints.
- Please test with a small subset of endpoints before rolling out to larger groups.