REMEXEC0=cmd /c net stop "Intel Local Scheduler Service"
REMEXEC1=C:\Progra~1\LANDesk\LDClient\LOCALSCH.EXE /taskid=1001 /del
REMEXEC2=cmd /c net start "Intel Local Scheduler Service"
1 of 1 people found this helpful
I think you are good not having to stop the service first.
Just the one line you have in the middle should be enough:
[MACHINES] REMEXEC1=C:\Progra~1\LANDesk\LDClient\LOCALSCH.EXE /taskid=1001 /del
I have had issues in the past with whacking tasks and found killing and restarting the service helped. May have just been antidotal ?:| However, there are some risks with stopping and starting the service. As we all say ... TEST and see what way works the best in your environment.
Is there a way to know for sure?
How can you tell what tasks are locally scheduled on the client?
Run this command from the ldclient directory on the agent workstation:
localsch.exe /tasks | more
Run an full inventory scan and then look at the values in inventory.
I knew you could run something on the client...
But I was wondering what Management Console report or query you could run to see which had the job scheduled??
You would have to create a Query.
The data is in Inventory as I mentioned. Look for it under "LANDesk
You will have to create the query to look for multiple values using AND
Executable path = <something here> AND Command line = <something here>
You may even have to add a third option if you are differentiating
between the same two commands but only one runs on IP Address change.
Awesome thank you!
Yep- i didn't read the last half of your note... sorry!