Actually - the relationship is the other way around. It's not so much "Task => Computer" but "Computer => Task".
Basically "LDprovision" loads up, and contacts the Core (/tries to) and goes "Hey, what is there for me".
The fact that (re-)launching LDPROVISION works, indicates that the Core is keeping track of "where the client is" just fine.
My personal experience / expectation in similar situations tends to be "iffy DNS" / similar networking based problems. The other option is that IIS / the app-pool on your Core is struggling with responding / picking up the request and passing it on to the DB.
In effect usually the scenario is something like this:
- Client powers up (at some point in the provisioning process) ... as usual
- ... client tries to reach the Core ...
- ... client then either CAN'T reach the Core (DNS / networking problem)
- ... or the client CAN reach the Core, but IIS doesn't send the request on to the DB due to it having issues (usually seen as 503-s in the IIS log).
Check your IIS log when you have this problem to see...
- ... whether your client HAS reached the Core successfully ...
- ... whether IIS has had issues in handling the request.
... a basic process flow & "how to read IIS logs" can be found as part of a webinar here -- [Tech Brief On-Demand Webinar 2016] Provisioning with LANDESK Management Suite .
This is usually "infrastructure" problems (either networking (most common) and/or IIS-related (so resourcing, etc) ).