Skip to main content

We often hear from our techs that Jump Clients stay offline even though the PC is only and reachable.
Trying to restart the sra-pin Service or the whole PC does nothing.
The only way you get this client back online is with the user clicking onto “Reconnect now”.
As soon as you click reconnect now the client comes back online.

Does anyone else have this problem or has an idea how we can get around this?

Another problem is that after a reboot the Jump Client often takes more than 10 minutes to get back online.
 

Hello ​@leonoehlinger - I would strongly recommend opening a Support Case with our Support Team on this matter. You would need to gather logs from an affected endpoint, and thye would need to review them for issues/errors.

In our environment the jump client service is set to delayed start by default. To get around this I change that startup to “Auto”. NOTE: BeyondTrust does not recommend this as a best practice. 

 

Not having a delayed start allows us to better support our road warriors that 1) Don’t have much downtime to troubleshoot and 2) Connect and disconnect from the network many times a day. This data is also handy for creating scripts (using the api) to alert you when a machine comes online so you can connect right away. 

In our environment the jump client service is set to delayed start by default. To get around this I change that startup to “Auto”. NOTE: BeyondTrust does not recommend this as a best practice. 

 

Not having a delayed start allows us to better support our road warriors that 1) Don’t have much downtime to troubleshoot and 2) Connect and disconnect from the network many times a day. This data is also handy for creating scripts (using the api) to alert you when a machine comes online so you can connect right away. 

During our installation routine we also change the startup to auto since our servicedesk and other colleagues just don’t have the time to sometimes wait more than 10 minutes just for a client to get back online after a reboot.

Hello ​@leonoehlinger - I would strongly recommend opening a Support Case with our Support Team on this matter. You would need to gather logs from an affected endpoint, and thye would need to review them for issues/errors.

I opened a case, thanks :)

Reply


Badge Earners

  • BCIE: Privileged Remote Access
    Flohas earned the badge BCIE: Privileged Remote Access
  • BCIE: Privileged Remote Access
    Ro-Manhas earned the badge BCIE: Privileged Remote Access
  • BCSE: Privileged Remote Access
    Ro-Manhas earned the badge BCSE: Privileged Remote Access
  • BCA: Endpoint Privilege Management - Linux
    Mudupurihas earned the badge BCA: Endpoint Privilege Management - Linux
  • BCIE: Privileged Remote Access
    vilasboashas earned the badge BCIE: Privileged Remote Access
Show all badges
Terms & ConditionsCookie settings