You can use the same local scheduler scripts on Mac as you do on Windows. It should parse them properly on Mac and do what you are wanting it to do.
That's what I thought at first, but after deploying some test scripts (on 9.6SP2 devices), it didn't seem to be working. I looked around at the various XML files and whatnot and could not for the life of me figure out where all of this configuration is being kept or logged. I also could not find any documentation on the Mac local scheduler. Any help figuring out how to troubleshoot this would be appreciated.
Also, if I create a "New Local Scheduler Configuration Script" using the console, I get the following:
REMEXEC0=<qt/>%LDMS_CLIENT_DIR%\LocalSch.exe<qt/> /del /range=%quote%1001|2000%quote%
REMEXEC1001=<qt/>%LDMS_CLIENT_DIR%\LocalSch.exe<qt/> /exe=%quote%/usr/bin/osascript%quote% /cmd=<qt/> -e 'say \""Local scheduler script has run.\""'<qt/> /taskid=1001 /freq=3600 /start=%quote%18 Jun 2015 10:50:00%quote%
Obviously, this isn't going to do anything as the remote executable doesn't exist. How does one update the Mac Local Scheduler?
Ok, so I was right to look in /Library/Application Support/LANDesk/scheduler. I created a XML file here named ldcron-sayhello.xml:
<Task xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task"><Triggers><TimeTrigger id="1"><Enabled>true</Enabled><StartBoundary></StartBoundary><Repetition><Interval>PT60S</Interval></Repetition></TimeTrigger><IPV4Trigger id="2"><Enabled>true</Enabled></IPV4Trigger></Triggers><Queues><Queue>ldiscan</Queue></Queues><Actions><Exec><Command>/usr/bin/osascript -e 'say \"Hello\"'</Command></Exec></Actions></Task>
This makes the Mac say "Hello" every minute or when the IP address changes.
The question now is - how can such scripts be deployed to existing devices and hopefully included in a distribution package? I can do this with OS X Profiles, but would prefer not to.
Some documentation would still be useful...