How to get the IGEL Device Name vs. the MAC Address with ControlUp Remote DX?

The user asked about how the naming of an IGEL thin client works, as it appears in the COP and in scripts. The network name had not been set, so it appeared differently in UMS and COP, and the scripts gave an error. By setting the Network Name, it should appear consistently across the platform. For more information, please see https://kb.igel.com/endpointmgmt-6.08/en/renaming-igel-os-devices-47711460.html.

Read the entire ‘IGEL Device Naming Explained’ thread below:

Other ControlUp Remote DX question : would it be possible to get the "Name" of the Igel TC (in my case) instead of the MAC Address as the "Client Name" ?

Cheers

my Client name shows the Host name of the Igel thin client

@member not for me! 😉

I’m on 8.8 beta, but it worked in 8.7 as well.

By default IGEL devices are named by their UnitID (ITC)…

Maybe you have to check on IGEL side:

https://kb.igel.com/endpointmgmt-6.08/en/renaming-igel-os-devices-47711460.html

I have both of those unchecked

@member I have "Adjust network name if UMS-internal has been changed" checked.

Would that explain it ?

Hello,

Following on this IGEL issue for me, here’s what I get:

in UMS, the "Name" of my device is "GVETCIG420", it’s "Unit ID" is "00E0C51D4506".
in the COP it is reported as "Client Name" as "ITC00E0C51D4506"
When I use an IGEL script I get an error "Unable to find device "ITC00E0C51D4506"

I found that the "Network Name (at Boot Time)" of part of my devices (for the main location actually) is not set as the "Name". It is OK for all subsidiaries (I just took over this so I didn’t know), and the scripts are working in this case.

I will have the Network Name set and all should be OK.

Cheers,

JCM