Skip to main content

We recently implemented Remote Support and have been impressed with its ease of use. We're deploying Jump Clients to all of our end-user machines to continue providing unattended support, as we did with our previous remote tool.

However, one key piece of information we've relied on in the past is the machine's serial number, which is currently not captured by Remote Support. It would be incredibly helpful if the serial number could be added to the list of information collected by the Jump Client. This would assist in verifying potential duplicate machine names at a given site.

Additionally, while I can search through the captured information in the Jump Items section of the Rep Console, I haven't found a way to customize the columns displayed in the list. Would it be possible to allow customization of the displayed columns to include fields like the user, IP address, and serial number when the list is refreshed? This feature would significantly streamline our workflow.

This has been a “suggestion” in the ideas portal for… a long time.

https://beyondtrust-public.ideas.aha.io/ideas/T2SRM-I-1736

https://beyondtrust-public.ideas.aha.io/ideas/T2SRM-I-2286

https://beyondtrust-public.ideas.aha.io/ideas/T2SRM-I-3162

https://beyondtrust-public.ideas.aha.io/ideas/T2EPM-I-1759

https://beyondtrust-public.ideas.aha.io/ideas/T2EPM-I-1616

I suggest upvoting some of them?  Maybe they’ll implement them :)

 

 


i upvoted all of them(one of them is mine 🙂 ) and also planning to bring this up in our support renewal discussion. Looks like they already capture this information and available via API… Its just needs to show up in the Console.


This may not work for your scenario, but it might get your creative juices flowing to make something similar - I have an API that runs through our jump clients on a schedule, compares to a separate dataset, and populates the Comments field for each jump client with info such as Assigned to username, user ID, title, workstation model, etc.. Maybe you can get creative and do something similar with the information you are wanting.

Limitations:

  • We only have a few thousand jump clients, so it doesn’t take long to loop through them once an hour. If you have more, it may not be quick enough.
  • It will be slightly delayed data since it would be a separate job running on a schedule

You probably already thought of this as well, but you could potentially set the Name of the jump client to the serial number during the installation. You’d just need to wrap the installer up in a script to grab the serial number at run time and pass it as a parameter to the installer. 


I like your idea about “wrap the installer up in a script to grab the serial number at run time and pass it as a parameter to the installer. “ This will be just one time action. Thank you for this idea


Reply