Remote Control Issues

Usage and Config
1

Hey guys,

How long after deploying the Remote Control Target to a bunch of endpoints, should they become visible on the Remote Control Server GUI?

I deployed a task pushing the settings with the ServerURL filled in this morning and they’re still not showing up (it’s now late in the afternoon).

Do you have any idea on how to solve this?

Thanks,
Raphael

2

Hi Raphael,
If the targets are not showing up in the server UI then the targets have trouble connecting to the server. Once the target is connected it reports back to the server every 24h by default. This is managed by the key HeartBeatTimeout on target which is set by default to 1440 ( minutes ). In case that the target fails to report back to the server it waits a fixed amount of time before trying again. This is managed by the key HeartBeatRetry which is set by default to 10 ( minutes ) .

So this means that in your case the target might be trying every 10 minutes to connect to the server. The related server key which can be set to enforce those values on the target are rc.heartbeat_timeout and heartbeat.retry.

You can find more here:

https://www.ibm.com/support/knowledgecenter/SS63NW_9.5.0/com.ibm.bigfix.lifecycle.doc/Lifecycle/Remote_Control/RC_Admin_Guide/rcadmtrcprops.html

Can you attach please one the target log after you restarted the service “IBM BigFix Remote Control - Target”

You should find the log in C:\ProgramData\IBM\Tivoli\Remote Control
The log files are those named like trc_base_XXX.log

Are the server and targets on the same subnet ?
Do you have firewalls ?

3

Hi Federico,

Thanks for answering.

Server and targets are on the same subnet. Internal inbound traffic is allowed on all ports as far as I can tell.

Attached, the log file trc_base_do.pdf (265.2 KB)

Please rename it to txt.

Thanks for your help

4

Thank you Raphael,
I just reviewed the log and I think the reason why the target is failing to connect to the server is this:

Server has refused the callhome with reason: (-1) Invalid secure registration token

You have to either provide a secure registration token using the related fixlet or set to false the property rc.enforce.secure.registration in Admin -> Edit properties file -> trc.properties

I hope this will help
Federico

5

Hi Federico,

This solved my problem indeed. Clients are showing up now.

Thanks so much for your help
Raphael

1 Like