Not anymore. I think the reasoning was that agents by default were being configured to update the server automatically when they got a new ip address and therefore would be more accurate than DNS itself. Not always the case though.
You need to look into why they aren't reporting in since there isn't a configuration option anymore.
The One-Stop Shop for LANDesk Enhancements
We have this problem as well, but most support staff understand that if they fail to connect to a machine by name, they should just perform a ping step and use the IP they get back. Occasionally, there'll be a DNS refresh issue where the wrong IP is returned. Those are few and far between usually.
I would think that it would be easy enough for LANDesk to offer a choice of DNS resolution with a simple checkbox or something, so that this function was at least optional. I get that they're picking perhaps the lesser of two evils, but why limit it? Might make a good ER (idea).
Unfortunately LANDesk removed this option with 9.0 SP2...
It would be really great if LANDesk could reintroduce this feature. We have some customers that require this configuration ability.
Since we're talking about ideas here, this is what i'd like to see.
First try: attempt to contact machine via inventoried IP (fastest step in theory)
Second try: attempt to ping the device by its name. if successful, and if a windows box perform an NBTSTAT -A %IPADDR% command to determine that the device name matches to the target. (Might only be good for windows, but if there's similar capability for other platforms, insert platform specific double-check here.)
The big problem with the DNS of course is the stale DNS entries that can linger. One can accidentally connect to the wrong computer, and that can actually turn into a political hot button, since security/communication issues start to pop up. Users can get paranoid if they think someone is spying on them, so i can see why landesk might have opted to do away with this method. I think they should still offer the feature though, and let admins decide whether or not to use it.
If someone writes up this idea, let me know, and we'll vote it up. If no one does this week, I will next week.
We have a neat feature called LDPing that will return the OS type and Computer name.
You can get this feature in the right-click menu by installing the LANDesk Support Tools (Console Add-on: LANDesk Support Tools ).
I've been thinking about updating RCR (old and coded very quickly do to need) http://community.landesk.com/support/docs/DOC-5151 . You can use IP addresses in the utility and maybe it will help you. I'm thinking about some commandline options (e.g., accept ip/dns name on command line good for console extenders), automagically install the LANDesk remote control viewer, GUI option to use resolved IP address if computer name is entered, gateway options, etc...
We have a tool similar to this, and has many of the features that you're talking about. Very handy. I coded it in winbatch though, not AutoIT.
I want to see LANDesk incorporate the behavior into the product over all though. Not just for Remote control, but tasks as well. I don't like seeing "different computer responded" as a message on device names. It should just be "failing to contact OFF" instead, but because its not taking the extra steps to test by device name via DNS, it just throws the wrong device error. Its cheesy for LANDesk to not support a resource like DNS. I understand it could make things more complex, but seems quite silly to not at least provide the option to people. Course this is off topic from this particular discussion, since it was started specifically about RC I apologize in advance for the rant! :-)