K2000 3.6 Server Task Engine gets stuck "in progress" while PCs Task engine completes successfully
Since upgrading to the 3.6 version of K2000 we have been having frequent issues with the task engine.
On the K2000 3.6 Server Task Engine it gets stuck "in progress" while PCs Task engine completes successfully.
It began with no mid task and only 1 Post install tasks that renamed the PC using WSname, install the KACE agent, and join the domain, but it would try to run the ne built-in Cleanup Task right after renaming the PC and then would never finish Cleanup even though everything was done.
Then I created 3 separate tasks to do the above and it would often get stuck right on the task right after the wsname task no matter what that task was (like reboot, Ksleep, etc), but the PC would complete successfully.
Sometimes it gets stuck on Setup engine run key on the "server Task engine", but on the PC it's task engine checks off each task successfully and it completes successfully. Of couse the server says the deployement never completed. It's as though the pC doesn't communicate it's task engine info back to the server sometimes or let it know it has completed that task.
There's nothing special about our setup really except our PCs all have SSD drives in them. Pretasks are: partition and format. No mid tasks altough I did finally add the DPinst-no reboot. Post install is just to rename the PC using WSname, install the KACE agent, and join the domain (vbs).
I've also noticed with version 3.6 that it takes about twice as long, about 16-20 minutes to deploy an image now compared to before.
Is anyone else having these experiences or does anyone have any ideas?
There are no answers at this time