I am able to reproduce the same thing running "C:\Program Files\LANDesk\LDClient\sdclient.exe" /E /Ac /EXE /P="C:\windows\notepad.exe" on our version 9 SP2 agents.
We do some very similar things related to our packages and are having some issues since upgrading from 8.8 SP4 to 9 SP2. We have been passing some custom error codes back to the console via scripting and using the SDClient.exe. The majority of our packages are EXEs that we are distributing and we have messages being displayed to the users as well.
Now when deploying software to a machine and it tries to pass one of the custom error codes back, the console status of the machine will go from Active->Done->Active and the task will then end and list the task with the caution symbol by it. I am not sure if this is related to your repeating issue or not.
The majority of our environment is still running our 8.8 SP4 agents and some are running the new agents. We are experiencing from the console perspective the machines going from Done back to Active on both the old and new agents though.
Well that's at least two of us with the problem then!
Anyone from LANDesk want to comment?
For the problem that batch files stays on active with result 0xDB50000,3509:0, exists a Patch.
We already received it and now the batch files are running good....
CLEARQUEST NUMBER: CR52811
Unknown status code (0xDB50000,3509:0) appears in Results field
Add a 15 second delay after your last SDClient.exe /msg command, to give it time to report the message before your script exits.
The patch appears to fix the msg problem, I don't have a problem with returns codes. My problem is simply that if I use SDclient for fire up an EXE, the EXE fires up twice.