1 of 1 people found this helpful
Last Software Scan Date - When a specific scan related to software is run and registers with the core server. This can generally only happen once a day.
Last Updated By Inventory Server - Anytime an inventory scan is run and registers with the core. It can be software, hardware, mini etc...
Also take a look here for further info on this and others - http://community.landesk.com/support/docs/DOC-6928
I have a machine here that is showing a last software scan date of the 15th of this month. Th elast updated by inventory server is showing as todays date.
I have right clicked this computer and selected inventory scan (which completed) yet the software scan date remains for the 15th. Can you explain why this is?
How can I get the client to update the core on demand from the core itself?
Sounds like the software scan is failing or getting rejected by the core due to corruption. You should force the scan, i would go to the system exhibiting the issue and go to the Inventory Scan shortcut and add the following switches to the end /F /SYNC This will force a software scan and then you can see what issues popup. If that fails you can also use the following switch /O=<path> and have the scan file save to a file and then try and drop it in the inventory scan folder and see if it picks it up. There may be an issue with the scan that the system is creating.
This can all be done from the core as well using a managed script:
REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\LDISCN32.EXE<qt/> /NTT=%server%:5007 /S=%server% /I=HTTP://%server%/ldlogon/ldappl3.ldz /F /SYNC /PD
Sometimes the variable doesn't work and you have to explictly add the core server name into the command line:
REMEXEC1=<qt/>C:\Program Files\LANDesk\LDClient\LDISCN32.EXE<qt/> /NTT=<CoreSERVERNAME>:5007 /S=<CoreSERVERNAME> /I=HTTP://<CoreSERVERNAME>/ldlogon/ldappl3.ldz /F /SYNC /PD
And here it is for creating a file locally:
REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\LDISCN32.EXE<qt/> /debug /o=C:\LANDesk_LOG\INVScan.txt /noui
hope this helps
How do i go about a managed script? I've not been trained on this but perhaps thats because I'm only licenced for inventory?
Not sure how the licensing thing goes with just inventory, if it includes the managed scripts feature. Here is the link in the toolbox in 32bit console. This feature is also availble with enabling roles in the console, so if you are a limited admin you might not see it. I woudl check with your head LD admin.
Ahh.. I only have scheduled tasks so the managed script thing is out. I'm a full admin so if we're licenced i should see it
Well, then you might want to RC that system and do it manually then. check the logs for it as well:
- C:\Program Files\LANDesk\LDClient\ldiscn32.log
- C:\Program Files\LANDesk\LDClient\data\ldiscn32.log (This log appears when ldiscn32.exe is ran with the "/debug" switch)
- C:\Program Files\LANDesk\LDClient \ldiscnupdate.log
Here is a good article on inventory issues as well - it may help - http://community.landesk.com/support/message/18246#18246
Unfortunatly, this is happening on at least 200 computers so a manaul approach is'nt something I can do
If all else fails, you can reinstall the agent and see if that helps..