You were right. Creating a small LANDesk Provisioning Agent with policy and security scans set to start in 3000 fixed the issue.
Our old provisioning scripts were using mostly execute file action rather than distribution software packages so that's why we didnt experience the issue before.
-Mike