Not really. The initial communication with a running agent is to get the device to download the virtual boot environment. In this case the most likely causes are that there was a faulty agent, the address LANDesk had in the database was not correct (so couldn't communicate) or the agent was so old (you don't mention version) that it had no provisioning components at all to begin the process.
LANDesk Silver ESP
The One-Stop Shop for LANDesk Enhancements
Update - WoW & State Notifier now integrate for even more functionality
Update - State Notifier now detects machine and user Idle states
Thanks for your answer.