A user asked about switching organizations on ControlUp for migrated VMs and received advice from others. One user suggested contacting support for potential tricks and another shared a solution using the registry. The user also mentioned a way to upgrade via the console and issues with MSI installations. The registry keys mentioned are: HKEY_LOCAL_MACHINE\SOFTWARE\Smart-X\ControlUp\Agent and HKEY_LOCAL_MACHINE\SOFTWARE\Smart-X\ControlUp\Console\EnableAgentManagement = 1.
Read the entire ‘Switching Organizations and Upgrading in ControlUp’ thread below:
I’m migrating a few hundred VMs that were managed by one Organization into a different ControlUp organization.
Does anyone know an easy way to switch orgs? The issue is that they were already migrated over, so now I cannot connect to them.
Do they still have the agent installed but communicating to the wrong organization?
That is correct.
And the original Org does not "see" those VMs any longer.
There is a way I used to do it using the registry, but there are a lot of different complexities now. I would recommend contacting the support team to see if they have tricks.
I will PM you the solution I used to use just so you know
Thank You. I could always give it a try on a few.
did you get this? just need to clear this reg path and that will allow you to install the new agent:
HKEY_LOCAL_MACHINE\SOFTWARE\Smart-X\ControlUp\Agent
Thank you
Yep, we got it 🙂
One thing to note: We had a few installed via MSI, and I could not upgrade them via the Console. So I deleted this Registry Key on the machines, and it allowed me to upgrade. HKEY_LOCAL_MACHINE\SOFTWARE\Smart-X\ControlUp\Install
But now you have both in add/remove programs? For future reference, you can tell the console to ignore that an agent was installed via MSI with:
HKEY_LOCAL_MACHINE\SOFTWARE\Smart-X\ControlUp\Console\EnableAgentManagement = 1
Continue reading and comment on the thread ‘Switching Organizations and Upgrading in ControlUp’. Not a member? Join Here!
Categories: All Archives, ControlUp for VDI