I don't provisioning offer that. Is there a reason why you want for one machine to start and finish before continuing to the next one, as oppose to letting them all run at the same time? Network Bandwidth issue?
Actually I'm not really concern about the task can run all machine at the same time or one by one.
I'm now facing to problem which the task really cannot make all machine start installing the apps from the provisioning task at the same time.
I've created the provisioning Apps package and made a schedule to let target machine to drag in. however, when I start the task schedule ...
only one machine can start install apps and others can't.
The machine that started, were you logged in at the time. Based on what I know there is about 10 min delay for provisioning to start if no user is logged into a machine.
Try loggin into all four of them, then start the provisioning process and see what you get?
if I add one more target machine to the schedule ... but the schedule is already running and installing apps in previous target machine.
How can I call the schedule startup for the new target machine??? I just can see the status is "Waiting..." for the new.
I have tried to click Start now again for the same schedule but it will terminate other running target machine, some will show "Delayed" but still running...
some of them will terminated!
You cannot add additional machine to the task once you have already started it. You either have to wait for it to be in a completed or successful state before adding more machine into the task, and under the shedule task option pick "devices that did not try to run the task" that way it doesn't re run the completed task. Or better yet just create a new task and drop in the machine.