I have progressed this further and it would appear that the agent is attempting to call the file SDCLIENT.exe from C:\LDCLIENT
Reviewing the configuration of the PC the only existence of SDCLIENT.exe is found in C:\Program Files\Landesk\LDCLIENT
It would appear that the problem is in the script and the location it is looking for the file... is this configurable?
I have resolved this. I had not deployed the SD client with the core agent. This is a necessity.
Imaging is now working again.