Remote Support 24.3.1 Upgrade Pending

Forum|Forum|1 year ago
November 22, 2024
15 replies
3850 views

We have 50+ jump clients that are showing in an Active [Upgrade Pending] state and are inaccessible. The devices are on the network, pingable, and I’m able to open a remote PowerShell session on them using enter-pssession, however, they’re not completing the jump client upgrade process. I’ve been able to get a few to complete the upgrade after forcing multiple reboots. In two cases I had to gain physical access and uninstall the old client and manually install the new one.

Is anyone else seeing these issues?

Remote Support

Show previous replies

E

EdM

Apprentice

We had similar issues with 24.3.1: dozens of pinned endpoints stuck at “Upgrade Pending.” We opened a ticket and the tech pulled some logs. In the end he advised downgrading back to 24.2.4 which we did by rolling back the VM snapshot. All the pinned endpoints, including the ones that were “Upgrade Pending” for 5 days came back online fine.

M

MSP01

Apprentice

Greetings - we had a similar experience as others. We are RS only. Our upgrade was automatically applied by BT because of the SaaS incident. We had 25 out of ~1300 clients stuck in Upgrade Pending. It looks like the service stopped somewhere along the line. We pushed a PS script to start the service and within seconds the clients upgraded. The PS code. “Get-service -DisplayName "BeyondTrust*" | where {$_.Status -eq "Stopped"} | Start-Service”

C

craig.brennan

Apprentice

Greetings - we had a similar experience as others. We are RS only. Our upgrade was automatically applied by BT because of the SaaS incident. We had 25 out of ~1300 clients stuck in Upgrade Pending. It looks like the service stopped somewhere along the line. We pushed a PS script to start the service and within seconds the clients upgraded. The PS code. “Get-service -DisplayName "BeyondTrust*" | where {$_.Status -eq "Stopped"} | Start-Service”

I attempted to start the service on my locally installed Jump Client and the service started but immediately stopped again. I’m working with a number of customers who are also having this problem.

M

Markw

Apprentice

Hello, any update on this from anyone?

K

kmkarthick

Rising Star

we ran into the same issue on few devices…. Support suggested to

Export the Root certificate from the /appliance -> Certificate section and update the trusted root store of the endpoint machine.

This resolved the issue.