1 of 1 people found this helpful
The Scheduler service's credentials only matter (pretty much) when you're trying to push agents - the rest works based on certificates. The fact that the client was trying to "do stuff" is a sign that the Core did manage to authenticate with it (you can check up the authentication in the SERVICEHOST.LOG in "C:\Program Files\LANDesk\Shared Files\").
Try creating a batch-file that's calling NOTEPAD.EXE and see how that works. If the batch-file is downloaded, we shouldn't have problems executing it (unless there's something like NTFS permissions or so getting in the way - a FILEMON or so should give you the lowdown on that pretty quickly).
Create a NOTEPAD-batch file in the same share, and see if that works ... if it does, re-try this task and have FILEMON running (log only errors) -- it may indicate to you what's going wrong...
Stuff like ADS (Alternate Data Streams) could be getting in the way - you may want to read this:
LANDesk EMEA Technical Lead
I have manged to get around this, but atill do not know how to write LANDesk script. Is there a website or PDF that can explain it to me?
Thanks heaps for your help. This look like what I'm looking for.
Thanks, just my opinion but I would probably use custom scripts as my last choice. Batch files, package builder, Autoit/Vbscripts off much more flexibility. Custjob (program that runs scripts on the core) is kind of old and does not have the advanced features as a scheduled task.
Thanks for the tip, but I have tried to create a BATCH file, and LANDesk keeps reporting that various machines are unable to run BATCH files, or it reports that the function failed - but it actually worked.
So was going to try scripting to see if that reports back better.
Usually can't process batch files is a sign of older clients that do not support this function. If you want post the batch file and version of LANDesk maybe we can see where it is failing.