We help top organizations stay competitive, by implementing the latest disruptive technologies.

Latest Posts
 

Gain Additional Inventory Insights by Manually Executing the OS X Inventory Scanner

Gain Additional Inventory Insights by Manually Executing the OS X Inventory Scanner

Have you ever had a device that won’t update the core server with its latest inventory scan?  While there are a numerous reasons as to why a scan may not process, unless you execute the inventory scanner manually, or peer into the landesk.log, it can be pretty tough to figure out what the cause might be.

In addition to seeing a real-time view into the scanner, when executing the Inventory Scanner manually, you can add command line switches to customize the scanner.

When I am troubleshooting an inventory issue, I always use the -e -s switches.  The –e switch forces a full hardware and software scan.  By default, the inventory scanner sends up a delta scan (the difference between the current scan and the previous scan), unless being directed to re-baseline the machine.  Using the –e switch will ensure I am forcing a full scan.

The –s switch is signals to the core server that it is to accept this scan, regardless of what it was previously expecting.  Again, because the scanner sends up delta scans, if a device gets out of sync with the core, the sync switch forces the core to accept this scan as the new baseline for the device.

So, to run a scan manually, all you need to do is open up Terminal on a Mac and type:

sudo /Library/Application\ Support/LANDesk/bin/ldiscan -s -e

After hitting Return and providing your admin password, you should see the inventory scanner start posting  all of its actions to the Terminal window.  If the scanner is hanging, you’ll see what action it was on.

If the scanner is able to successfully finish, at the bottom of the output you should see a couple of lines to give additional insight as to why the server might be rejecting the scan.  Look for the lines:

Sending scan file to server: fullyqualfied.domain.name
Status from core = HTTP/1.1 503 Service Unavailable

Pay attention to the status from core line.  The Mac scanner is simply making a standard post to IIS on the core server, so all of your standard IIS return codes apply.  See https://community.landesk.com/docs/DOC-1086 for more information on the IIS status codes.

Also, just for added info, below is a list of all of the command line switches for the Mac inventory scanner.

ldscan [-v1|2|3] [-F ][-R][-c alt_ldms_core] [-l alt_ldappl_path][ -o alt_output_dir][ -t ] [-m mode][-w wait_time][ -h ]
   -c      <name>               - specify which core to send inventory to
   -D                       - force a delta scan.
   -e                       - force a full hardware and software scan
   -F                       - force a full inventory scan
   -h                       - this help screen
   -i                       - ignore user and server preference settings
   -l  <path>               - path to alternate ldappl.ini path
   -L                       - limit downloading of ldappl3.ini
   -m <mode>                - set the scan mode
   -N <name>                - use <name> as the device name in the scan
   -o <path>                - write the scan data to <path> instead of sending it to the core
   -p                       - output full product definitions
   -P                       - don't really scan, just display the scan settings.
   -R                       - reset scan database
   -s                       - perform a synchronization scan
   -T <file>                - send <file> to the core
   -t                       - perform a mini scan
   -u                       - unfiltered output (debugging)
   --v1|2|3                 - report formatted version information
   -V <n>                   - set verbosity level (debugging)
   -w <n>                   - wait <n> seconds  before continuing
No Comments

Post A Comment