Update on this, so far i've only seen it when deploying w10 machines, we rarely deploy w7 so i can't say if it happens there.
This still happens randomly, i've tried to manually run the ztigather script from the client and rebooting afterwards, that does seem to fix the problem, but it should not happen at all in the first place. I've also gathered some logs from the server and client, it might look like the client thinks it's done deploying at this stage, i'm not 100% sure. The logs can be found here: http://www.filedropper.com/minint-nq61702 Från: [email protected]<mailto:[email protected]> [mailto:[email protected]] För Michael Niehaus Skickat: den 10 februari 2016 08:50 Till: [email protected]<mailto:[email protected]> Ämne: [MDT-OSD] RE: ZTIGather problems. I doubt MDT 2013 Update 2 will change this. The biggest thing is trying to figure out about where the script is hanging - the logs on the client would likely narrow it down (although depending on how you recover from the situation, the last few lines of the log might be lost). If you manually run ZTIGather.wsf on the machine (e.g. cscript \\server\deploymentshare$\scripts\ztigather.wsf<file://server/deploymentshare$/scripts/ztigather.wsf>) does it complete successfully? Thanks, -Michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David Nylund Sent: Tuesday, February 9, 2016 11:37 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] ZTIGather problems. Hello, i just noticed that a few times when deploying the computer that was deployed seem to "hang" when running this script, i checked the logs on the server and also on the client itself. The computers where Dell, i think it was one E7450 and a E7270, restarting them did nothing it was came back to the same spot in the sequence and hung again. It could be a hardware thing, but i've diaged those comps and they seem to be fine, i later resumed deploying apps in a more manual manner and that seems to work just fine. I'm still using update 1 mdt 2013 and winpe .240 i belive, not sure if it would help to update to update2, those scripts might not have been touched anyhow so.... This was when deploying a windows 10 image, not sure if it does the same wit ha w7, but we're trying to move away from that. (w7) Does anyone have simmilar experience and if so any good way to troubleshoot it besides looking at the logs?
