Hello ​@TZoltan - as a general rule, Jump Clients should not be directly installed on to the Golden image itself. The Jump Client installer should either be placed in a directory to be auto-installed on first log in, or be pushed out as part of a Software Deployment set up.

Every Jump Client requires it’s own connection to the appliance and to collect its own information, which they create when they first come check-in. If you now copy this image / Jump Client, you may end up with a very confused entry in the Rep Console, with multiple machines all attempting to connect in with the same details.

We have a KB article about this topic here: https://beyondtrustcorp.service-now.com/csm?id=kb_article_view&sysparm_article=KB0017470

Hello ​@PhillC ,

Thank you for the answer and the KB article. Yes, we don’t copy a deployed Jump Client, only the installer file.

I maybe have a wrong knowledge, so what we have done in the past is that after every PRA update we created fresh Jump Client installers, because we had the information that it will not work with later version. Is that information wrong? If a Jump Client installer has been created on a previous version of PRA, will it still be able to work with a new version?

Hello ​@TZoltan - in our newer versions SRA, you can expect a Jump Client installer to work for one or two upgrades. However, it is always best practise to keep your Jump Client installers as up to date as possible as the installers themselves also expire after a time.

These days, if you install a Jump Client using an older installer, then the Jump Client will install then immediately attempt an auto-update to the latest version. So long as this works, you’ll have a working installed Jump Client.

Understood, thank you very much for the information!