2 Replies Latest reply on Mar 15, 2010 3:20 PM by tdavenport

    Mini Scans with New Agents


      LD 8.8 SP3


      I have recently deployed 14K nodes and have a small issue concerning mini scans.


      From All devices view, I have about 100 machines that are "managed" but only show basic information (IP address , name, device ID, etc...). These are mini scans. I can remote control these devices. The agent appears to be fully installed. The agent has been resident for several weeks now. The "Last Updated By Inventory Server" date is current.


      If I deploy the "Inventory Scanner" Managed Script., they all fail. The script has been modified to force a full scan. See below:


      REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\LDISCN32.EXE<qt/> /NTT=%server%:5007 /S="%server%" /I=HTTP://%server%/ldlogon/ldappl3.ldz /NOUI /NOCD /F /Sync


      The scheduled task results show "The system cannot find the path specified.


      However, if i remote control a device in this group and manually kick off a full scan, the full inventory scan completes and I no longer have a mini scan inventory for that device. I have the full inventory. The command used is:


      "C:\Program Files\LANDesk\LDClient\LDISCN32.EXE" /NTT=XXX-LDCORE:5007 /S=XXX-LDCORE  /I=HTTP://XXX-LDCORE/ldlogon/ldappl3.ldz /V /Sync /F

      (I edited the server name for the purposes of this thread.)


      Thinking it might be an issue with the variables, I modified the inventory script and specified the core server by name and redeployed with no success. That script was:

      REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\LDISCN32.EXE<qt/> /NTT=XXX-LDCore:5007 /S="XXX-LDCore" /I=HTTP://XXX-LDCore/ldlogon/ldappl3.ldz /NOUI /NOCD /F /Sync


      Question: Why does manually firing off the full inventory scan work and pushing the same command via Managed Scripts fail?


      Thank you for taking the time to read this. Any and all suggestions are welcome.