Hi,
So I moved everything back and downloaded all the updates (didn't want to copy them just in case) and reset the agent settings to no avail.
I've read through the document Jeff but I can't see anything with regards to agent replication. As I understand it the deployment template pulls the agent from the core, unless you specify a self contained agent install which I'm not. If I'm wrong in that understanding please let me know.
I've managed to find some errors now in the provisioning log on the Core, although it doesn't particularly help me understand what's wrong. I found a post that was resolved with a comment stating "had the 2017 beta and that's resolved the issue" or similar.
VERBOSE ProvisioningWebService 30/05/2018 16:46:03 : SetActionStatus (historyTaskIdn 209, historyEntryIdn 5560, next 5561): state FAILED
VERBOSE PHistoryTask 30/05/2018 16:46:03 : StopProvisioningJob (LDTaskId 357, computerId 407, historyTaskIdn 209), state Failed
VERBOSE PHistoryTask 30/05/2018 16:46:03 : update the history task state
VERBOSE ProvisioningWebService 30/05/2018 16:46:04 : SetActionStatus (historyTaskIdn 209, historyEntryIdn 5560, next 5561): state FAILED
VERBOSE PHistoryEntry 30/05/2018 16:46:04 : Unable to write to database. Altering history task Idn 209 state is not allowed. Failed.
ERROR ProvisioningWebService 30/05/2018 16:46:04 : Unable to set the action status (historyTaskIdn 209, historyEntryIdn 5560, next 5561): History task is not in the running state.
Any other potential suggestions?
Thanks
Gary