Troubleshooting Upgrading Issues in ControlUp

A user experienced issues with upgrading monitors and connectors after upgrading from V9.0.01680 to V9.0.5.143. They had to manually RDP into each server to upgrade and couldn’t log in to the ControlUP console after upgrading 8 collectors. Other users suggest using the Invoke-CUMonitorUpdate cmdlet or checking for domain-joined machine status. ControlUp also recommended upgrading to the latest version, 9.0.5.423, which may not solve the issue but is generally advised. A support ticket was recommended to address the initial issue.

Read the entire ‘Troubleshooting Upgrading Issues in ControlUp’ thread below:

I just upgraded from V9.0.01680 to V9.0.5.143 and had issues with the upgrade of the Monitors and Connectors, instead of clicking on them and selecting Upgrade (which failed with an error) I had to manually RDP into each server (18) and open ControlUP from that Server to upgrade? As for the 8 Collectors, even though I can RDP to them manually and I am unable to login to the ControlUP Console, as the webpage comes up to login and Microsoft Azure is selected, it allows the username and password to be entered, then it wants my elevated account password but before I even have a chance to hit one key on the keyboard it refreshes the web page and brings me back to the initial login screen with an error message of Google Capture does not think you are human.

Hi @member Are you running the console on a domain-joined machine? Deploying monitors from the console requires WMI

If you run the console on a workgroup machine (non-domain joined) then upgrading monitors (or basically any monitor action from the console) will fail

In this case, I highly suggest the Invoke-CUMonitorUpdate cmdlet from the ControlUp Automation module

All the servers are connected to the same domain @member

So there is no reason why upgrading the monitors from the console should not work

what is the error message you receive?

Also before the upgrade (This could be a coincidence) I had full control over all the servers in ControlUP, I could stop them all (Monitors) and then restart them. Now I can stop them all but I am unable to restart them unless I logon via RDP to update it from that server?

Connecting to each monitor machine via RDP should not be necessary. We haven’t changed anything in the upgrade procedure from the console. It should work the same as in 9.0

Can you please open a support ticket for this issue?

I am going to do that, but I thought I would see if anyone else had this issue first.

By the way, it would be great if you could upgrade to 9.0.5.423 (available in our Download Center)

Not that this will fix the issue you have, but I think it’s always good to use the latest version

Continue reading and comment on the thread ‘Troubleshooting Upgrading Issues in ControlUp’.  Not a member? Join Here!