CUSTOM_FIELD1 being ignored by AMT template used with host entry

Implemented

CUSTOM_FIELD1 being ignored by AMT template used with host entry

avatar

I have created a host entry and entered a "management IP" address in CUSTOM_FIELD1 under information. I've then created a template for an Intel AMT connection, and in the host field I have entered $CUSTOM_FIELD1$. However, when connecting using the host entry and selecting the Intel AMT KVM template, RDM still tries to connect to the IP address in the host field of the entry.

To test whether or not the CUSTOM_FIELD1 variable has the correct value, in the template I have added a custom VBScript to the "Before Connect" event that simply creates a message box with argument 0, which in this case I have configured CUSTOM_FIELD1. The message box appears and I see the correct IP address from CUSTOM_FIELD1, however the Intel AMT VNC connection still uses the IP address from the underlying host entry "Host" field.

Is this a bug or am I doing something wrong here?

RDM Free Edition: 2020.1.10.0


RDM Template.png

RDM Host Entry.png

All Comments (2)

avatar

Hello,

I believe this is a bug. We'll open a ticket to investigate.

Regards,

Hubert Mireault

avatar

Hello,

Turns out that this wasn't a bug per se. What happened was that it used the "information" (including custom fields and whatever else was in the information tab) of the Host entry rather than the template. To work with your scenario, I've added a checkbox in the Host entry for "use template information". You will need to check this and it should properly resolve the host for your Intel AMT template. This should be available in our next version (probably a beta), RDM 2020.1.18.0

Regards,

Hubert Mireault