Users discussed best practices for upgrading ControlUp by moving it to a new VM; this includes backing up the Console machine’s appdata folder and republishing the configuration, as well as reusing the existing database. It was suggested that the platform’s consoles and monitors should logon to the new name and IP, while the agent auth key should be migrated using PowerShell commands. Uninstalling the monitors and data collectors was suggested because of the name change.
Read the entire ‘Best Practices for Upgrading ControlUp on a New VM’ thread below:
Has anyone done an upgrade of ControlUp and moved it to a new VM as well?
Its doable. You would have to backup the appdata folder on your console machine and republish the configuration on the new server. I would reach out to support for help on it.
And the database can be upgraded in place to the new version without issue, correct? Even though the cop server has a new name and IP?
Sure, you can reuse the DB.
That’s what I thought. I don’t know why I’m getting pushback about it
The only thing that would change in this instance is where the consoles/monitors go to logon.
Sure, makes sense
Everything else would be the same. Same license, same org name, same everything. The only other thing you’d need to do is migrate the agent auth key using powershell commands.
So would it be better to uninstall the monitors and data collectors because of the name change?
@member 👑
Continue reading and comment on the thread ‘Best Practices for Upgrading ControlUp on a New VM’. Not a member? Join Here!
Categories: All Archives