It's very simple to disable on that client.
Check this file out:
/opt/landesk/etc/ldconfig.xml
This is the configuration file that the inventory scanner uses to know what "component" scans to run, in effect.
You just need to comment the relevant section out with the normal XML "comment" tag, so "<--" in the beginning, and "-->" at the end... so from this
(...)
<component category="scanner" type="hardware" name="memoryscan" version="2.3" path="/opt/landesk/bin/map-memscan" provides="MEM">LANDesk memory scanner</component>
<component category="scanner" type="hardware" name="mountscan" version="2.3" path="/opt/landesk/bin/map-mountscan" provides="MFS">LANDesk mounted file system inventory scanner</component>
<component category="scanner" type="hardware" name="networkconfigscan" version="2.3" path="/opt/landesk/bin/map-networkconfigscan" provides="NETWORK">LANDesk network configuration scanner</component>
(...)
Into this:
(...)
<component category="scanner" type="hardware" name="memoryscan" version="2.3" path="/opt/landesk/bin/map-memscan" provides="MEM">LANDesk memory scanner</component>
<!--component category="scanner" type="hardware" name="mountscan" version="2.3" path="/opt/landesk/bin/map-mountscan" provides="MFS">LANDesk mounted file system inventory scanner</component-->
<component category="scanner" type="hardware" name="networkconfigscan" version="2.3" path="/opt/landesk/bin/map-networkconfigscan" provides="NETWORK">LANDesk network configuration scanner</component>
(...)
and then save the file (make sure it's still owned by "landesk:landesk") when you're done, or CHOWN it if need be.
This will enable you to disable the component scanner that's causing you grief on that device while figuring out what's going on. That's the "quick workaround".