I've been using Smart Deploy and need some help. We need to redirect our clients from an old server to a new one that's running Smart Deploy. I understand there's a PowerShell script that can do this, and I'm wondering if I can implement this as a startup script through Group Policy. Has anyone successfully done this? Also, I want to make sure that this script runs only once on each machine and that users don't see the script executing. Any advice would be appreciated!
3 Answers
To ensure the script runs only once, you could create a registry key when it runs for the first time. When the script launches, it should check for that key. If it doesn't exist, the script runs, and if it does, the script exits. For invisibility, consider running it as a hidden admin task or through a .bat file which can execute the script in a concealed window. As for Smart Deploy, I'm not entirely familiar with it, but I'd assume a PowerShell script can adjust configuration files or possibly registry keys, which should be documented somewhere.
There's actually a pretty straightforward way to migrate your clients directly to the new Smart Deploy console. You can select the clients from the old console, choose the migrate action, enter the new SmartDeploy API service URL, and confirm it. This should make the transition smooth without needing complex scripts. If you run into any hiccups, just let me know!
It should still work if you have the right permissions. Ideally, this migration just updates the clients without needing to reinstall anything.
I found a helpful resource that might assist you with the transition. You can check out this link: https://smartdeploy.pdq.com/hc/en-us/articles/25936250108443-How-can-I-migrate-my-SmartDeploy-Console-application-from-one-host-system-to-another. While I can't guarantee your method will work, I suggest looking into using Immediate Scheduled Tasks in Group Policy. There's a solid guide on executing PowerShell scripts as scheduled tasks, which could help with your setup. Also, ensure your PowerShell execution policy is set correctly to allow the script to run.
What if we can't access the new console for that?