I am building a new program to assist me reduce the management overhead of doing certain tasks in our business. This task will give me the ability for a machine to decide for itself on login to download a package from our landesk server and then execute it (or multiple packages). The benefit I get using landesk to drag the file down instead of a file copy is I can harness its multicast capabilities to trickle the package down.
(Using policies etc is no use to me as I do not know what computer will need the software at the time of creating the policy. I have fully automated a single build for reimages which currently asks the user to contact the helpdesk to arrange for specific packages to be pushed down. If I can finish my program this makes the single build completely automated and self sufficient.)
I have talked to Landesk tech support and got the following command line which works great apart from 1 thing
Command line is :'"c:\Program Files\landesk\ManagementSuite\CustJobLaunch.exe" 2 "MYApplication.ini"'
The issue I get is my program may launch multiple jobs as the machine may need more that 1 package. To handle this scenario I simply log the pid of the CustJobProcess and keep checking to see when it closes. This is fine but I have come across an issue that the process seems to die off quite quickly and spawns a Custjob.exe. I can via a script find out what the parent pid of a process is however in doing this I discvered there is more to this than meets the eye.
It appears CustJoblauncher.exe does not spawn Custjob.exe. It in fact seems to tell Residentagent.exe to create the custjob.exe.
This gives me the following
CustJobLauncher - Spawns Resigentagent.exe which then spawns custjob.exe. I cannot back track the parents because the parent of residentagent.exe is always services.exe so there is not way to match the custjob.exe pid to the custjoblauncher.exe
This is where my question comes about ... so dont worry if you did not understand the above fully.
Q. Is there a way to tell residentagent.exe or preferabley custjob.exe directly to initiate a multicast push of a script with the computer_IDN similar to the way I can tell custJobLauncher without initiating custJobLauncher.exe in the first place. I figure there must be a way as this information gets passed all the way from the custjoblauncher to custjob.exe as I have realised in my workings of this new progam.
(I already know the computer_IDN from interrogating the SQL db in the Computer table)