Same issue here.
Try to deploy a single machine per task, seems that adding more then one machine in a provisioning task "breaks" the software distribution.
Same issue here. Has anyone contacted support?
Hello, yes, but until now, there is no result. They are analysing the logs. I report to you, when i have further information.
we have an open case (#00668765) now escalated to PSE.
There is a defect and you can refer to it (TFS 89097).
2 workaround possible:
A: you can create a provisioning task with only a machine as target.
B: create a template that stops before software deployment (it should end with agent installation and reboot) and perform the software distribution as a scheduled task
In the 2nd workaround you can add more than 1 machine per task.
We all are waiting for a fix
wie don't have more than one Client in our tasks and have this problems.
...we only have one task for our complete application-set...because we use a provisioning template to deploy our software, after the os deploy. so i think there is a missunderstanding between us amagi
Of course we can change our method to deploy our application after the os deploy via individual Software Tasks, but that would be not the fastest and preferd workaround for us.
Ok Amagi you have totally confused me.
You say you have the same problem and deploying more then 1 machine seems to break the software deployment but in your next reply you say a workaround is to add more then 1 machine per task?
Sorry hrz-dtmaint, we have the same issue only with multiple targets and the workaround A works fine.
MrGadget, I said that you have 2 workaround:
option A or option B.
Option A: single machine
Option B: more of 1 machine
I had the same issue, too. But with 9.5 SP2.
It was a task with 9 clients and one had this problem and a few days before I had the same issue again with 3 clients in a task and one has a succeeded status, but didn't installed the software...
Is this "bug" still present?
I am seeing the same thing on my new core but only after the upgrade to SP2. When I was on SP1 the tasks would fail and show the red X. Now that I am on SP2 I am experiencing this problem. I have a bunch of Dell CCTK operations at the beginning of my provisioing templates. The files are not present on the WinPE image yet so all the tasks should fail like they did before I upgraded to SP2, but now they all get the flase positive success.
I have this issue in the System Configuration Section. When I check the sdmcache on the client, I could see that the source isn't present, so I should get an failed or something like this, but it is successful and thus it was a redist I have problem with a few software to install later...
And thus it is succeeded the logs schow a successfully completed, too. So it is hard to see, what is wrong.