ADCS: fixed terminal id

Hello all,

I'm going to cut to the chase right away: Our client, who uses the ADCS granule (with the VT100 plugin), has just lost two of his 1.600€/piece handheld terminals (well, he didn't lose them, one of his employees did). Since this is not the first time this has happened, he wants to set up some kind of log to know which users logged on to which handheld and to discover which handhelds are missing and who used it last. That way he might be able to pinpoint the responsible employee and take actions accordingly, while at the moment he doesn't have a clue who did it.

Now, the problem for setting up some kind of device logging is that it appears that each handheld does not have a fixed terminal id assigned to it (or we don't know how to get that terminal id in Navision). We DO get the ID node which is considered to be some kind of a unique terminal id, but we noticed that this ID can change when, for instance, the handheld disconnects from the network or when the telnet-session is restarted. Since this sounds more like a session id rather than a real terminal id, we cannot assign that id to one specific handheld (think of it this way: we want to physically label each handhelds with his own id).

Has anyone of you experts encountered the same problems and is there a way around them? Are there some nodes or attributes in the communication XML that I haven't heard about, or is there a way to reconfigure the handheld so that the Terminal ID remains the same, no matter what the user does on the handheld (log-off, reboot, disconnecting from the network, ...)? I was thinking perhaps a fixed IP for the handheld might solve the problem, but it all depends on to what extend the IP-address of the terminal has any influence on the terminal id it gets assigned.

Thanks in advance, and best regards.

Maarten