2012 R2 Task Sequences - Random Failures

[Hilla01JSJ]

I've been having an ongoing issue that may eventually make me bald with how much hair I've been pulling out, looking for any insight in where I should be looking, or what I should be doing to try to resolve this.

I have a Windows 10 task sequence (With a PE image cobbled together) and it works fine. Most of the time. (And now, same with our Win 7 sequence)

My server goes through File/Package validation every Wed. During this time utilizing this distribution point (Which is also our main server) I will get many packages failing validation stating the files are not found in those errors.

I've generally left it alone. The files are there on the drivers if I look for them. We have revalidated them in the past, but I let it float for awhile. During this time, I'd say I was 80/20 on successful imaging.

Friday, I redistributed the packages. This server is now green, but my imaging has probably plummited to less than 50/50 for success. I had someone report to me that they had to image the same machine 3 times to get it to work.

I've got two SMTS logs so far, looking to get more, but if anyone has any insight on these two that'd be great.

LOG 1 - I can see the clear failure here, it failed running a Powershell script. The reason however, doesn't make much sense to me. The powershell script is absolutely present on distribution point in question, I checked immediately afterwards.

LOG 2 - This one failed running the standard package PS scripts via MDT 2013.

Again, the biggest problem/hurdle I'm experiencing here is not the validity of the task sequence. It works. It works randomly. Sometimes it works more often than not. But these failures so far haven't given me any real window into WHY they're occurring.

I have the full set of logs from both PCs, so any additional logs for review, or if someone can point me in the right direction...Anything would be helpful.

Thanks!

LOG1.log

LOG2.log

[anyweb]

from log1

 

<![LOG[Error. Received 0x80072ee7 from WinHttpSendRequest.]LOG]!><time="09:20:26.379+240" date="11-04-2016" component="TSManager" context="" type="1" thread="4392" file="libsmsmessaging.cpp:9044">
<![LOG[unknown host (gethostbyname failed)]LOG]!><time="09:20:26.379+240" date="11-04-2016" component="TSManager" context="" type="3" thread="4392" file="libsmsmessaging.cpp:779">
<![LOG[hr, HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9093)]LOG]!><time="09:20:26.379+240" date="11-04-2016" component="TSManager" context="" type="0" thread="4392" file="libsmsmessaging.cpp:9093">
<![LOG[sending with winhttp failed; 80072ee7]LOG]!><time="09:20:26.379+240" date="11-04-2016" component="TSManager" context="" type="3" thread="4392" file="libsmsmessaging.cpp:9093">
<![LOG[Will retry in 6 second(s)]LOG]!><time="09:20:26.379+240" date="11-04-2016" component="TSManager" context="" type="2" thread="4392" file="libsmsmessaging.cpp:1917">
<![LOG[Retrying...]LOG]!><time="09:20:32.823+240" date="11-04-2016" component="TSManager" context="" type="2" thread="4392" file="libsmsmessaging.cpp:1921">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: scm1001001.jsjcorp.com:80 CCM_POST /ccm_system/request]LOG]!><time="09:20:32.823+240" date="11-04-2016" component="TSManager" context="" type="1" thread="4392" file="libsmsmessaging.cpp:8778">
<![LOG[Error. Received 0x80072ee7 from WinHttpSendRequest.]LOG]!><time="09:20:32.823+240" date="11-04-2016" component="TSManager" context="" type="1" thread="4392" file="libsmsmessaging.cpp:9044">
<![LOG[unknown host (gethostbyname failed)]LOG]!><time="09:20:32.823+240" date="11-04-2016" component="TSManager" context="" type="3" thread="4392" file="libsmsmessaging.cpp:779">
<![LOG[hr, HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9093)]LOG]!><time="09:20:32.823+240" date="11-04-2016" component="TSManager" context="" type="0" thread="4392" file="libsmsmessaging.cpp:9093">
<![LOG[sending with winhttp failed; 80072ee7]LOG]

 

 

that means it cannot communicate with the mp due to network issues (no ip, or dns problems), so you need to pause the task sequence mid action, and verify if it indeed is able to communicate with the dp/mp otherwise of course it will fail

 

most likely cause, lack of network drivers in the boot image for the hardware involved

 

cheers

niall