Skip to main content
Answer

JC_SUPPORT_BUTTON_DIRECT_QUEUE=team:blah_tc

  • October 24, 2025
  • 4 replies
  • 52 views

25.2.2 trying to assign a direct queue for the jump client button does not seem to like this “JC_SUPPORT_BUTTON_DIRECT_QUEUE=team:blah_tc”. This is the syntax provided in the docs. Has anyone else see this? Other similar options are working “JC_JUMP_GROUP=jumpgroup:blah_jg”.

Best answer by PhillC

Yes, appropriate overrides were selected. I’ve attached a screenshot taken when the installer was built.

 

Hello!

OK, understood - best thing to do then is to collect logging from one the Jump Clients as you try to install it - our logging output should show what error is being presented or options it is trying. The KB on how to enable logging and what this process involves is here: https://beyondtrustcorp.service-now.com/csm?id=kb_article_view&sysparm_article=KB0020193

I would then open a Support Case to get them reviewed for the issue.

 

4 replies

Forum|alt.badge.img+1
  • BeyondTrust Employee
  • October 27, 2025

Hello ​@SRT - Can you please confirm this Jump Client was created with that field selected to “override is allowed”. This can only be set when the Jump Client is created, so if you are unsure, it is best to recreate the Jump Client installer, and ensureing this option is set.

Otherwise, you would get this issue, where the Jump Client installer is effectively ignoring this addtional input.


  • Author
  • October 27, 2025

Yes, appropriate overrides were selected. I’ve attached a screenshot taken when the installer was built.

 


Forum|alt.badge.img+1
  • BeyondTrust Employee
  • Answer
  • October 27, 2025

Yes, appropriate overrides were selected. I’ve attached a screenshot taken when the installer was built.

 

Hello!

OK, understood - best thing to do then is to collect logging from one the Jump Clients as you try to install it - our logging output should show what error is being presented or options it is trying. The KB on how to enable logging and what this process involves is here: https://beyondtrustcorp.service-now.com/csm?id=kb_article_view&sysparm_article=KB0020193

I would then open a Support Case to get them reviewed for the issue.

 


  • Author
  • October 27, 2025

While we will for sure be submitting a ticket for bug, for reference after pulling logs we found this when attempting to leverage the Support Button Direct Queue:

From JC Log (blog.ini on system drive):

PINNED_CLIENT:WARNING>Failed to authenticate using key [blah] with reason The #CALLBACK_BUTTON profile may not be specified at deploy time for this deployment.
 
[void]$jc_MSI_Install_Params.Add('JC_PUBLIC_SITE_ADDRESS="blah"')

[void]$jc_MSI_Install_Params.Add('JC_SUPPORT_BUTTON_PROFILE=blah')
[void]$jc_MSI_Install_Params.Add('JC_SUPPORT_BUTTON_DIRECT_QUEUE=team:blah') #broken