SCCM Image Deployment - Massive Delay in Applying WIM

[Tefters]

Morning all,

 

Throwing this one out there to any SCCM peeps as this is one issue I have not seen before (and I thought I had seen them all).

 

Have a Lenovo M73 Tiny PC which has been building fine through our environment for 2 years up to about 5 weeks ago (no major changes on a system level).

During the WIM download/install phase I am seeing a MASSIVE delay of about an hour straight after the download of the WIM to when it should then go straight into Applying the WIM.

Anyone seen this before? All other machines and Images are fine so cant be a server issue, any image that's applied to this model of machine now has this hour long pause/hang.

 

I have attached a portion of the log staring out the server name for security and have spaced out the middle section of interest.

SCCM_Delay_Build.txt

[Sagima]

Do you get the delay on a machine that isn't already in sccm's list of computers? (one that is picked up as an unknown)

[Tefters]

All my deployments are done through Unknown

[ITJS2015]

Have you tried just one machine rather than bulk, it could be one of the machine doing a bulk process.

 

Its worth testing out to see how long It takes and to see if it hangs during one image process

[Tefters]

I'm only building this machine on its own at the moment while testing.

All other machines though again are fine.

[ReadTheNetwork]

Bit of a long shot, but I notice the authentication errors, double check your SCCM certificates are not past the due date and up to date also try allowing anonymous access?

[free780]

Could be a hash check delay.

[Tefters]

@free780 I was going down the hash check delay route, need to think a little more about it today but that's certainly what it looks like. Dunno why on this specific unit though and especially after its been building fine for 2 years. Also this isn't just 1 machine, I have tried multiple of this model to rule out a 1 off issue. All other models appear to be fine regardless of the image I use which still causes my brain to hurt.

[Tefters]

Bumping for any ideas on this one.

 

Revisited this today for 2 hours and created 2 brand new boot images both x86 and x64 from Windows 10 ADK to no-avail, same issue.

Next step is to try injecting some storage drivers into the boot image but the only one available for the unit is the Intel Rapid Storage driver which I cannot see working...

 

Posted on both Technet and Windows Noob as well but yet to get any decent leads on this.

 

Again to highlight, this unit used to build absolutely fine and that's the only thing that has me stumped is that it takes 2 to 3 hours to do the file hash check before proceeding. Built 3 other models of PC (HP, Lenovo, and Dell) today with no issue.

[free780]

You can enable verbose logging for the boot image. Might show you what's happening.

[ReadTheNetwork]

You might have tried this already but I'd look at updating the BIOS.

Also try enabling debug, to allow you to get a command prompt up. Then mount the share containing the wim file (e.g. net use V:\myserver\mywimlocation\) manually run the imagex/dism command to see if that takes a long time to do when done manually.

 

Which log file is the one you uploaded is the the client's DISM.log?

[Tefters]

SMSTS log file from the F8 advanced build diagnostics.

 

BIOS is on the list to update, don't need verbose logging due to log file access.

[ReadTheNetwork]

Next step is to try injecting some storage drivers into the boot image but the only one available for the unit is the Intel Rapid Storage driver which I cannot see working...

 

Have you tried swapping the HDD out of a machine which works fine? Help rule out a HDD issue.

[Tefters]

Have you tried swapping the HDD out of a machine which works fine? Help rule out a HDD issue.

 

Grabbed another 8 units and built with a 80% success rate so after then reading your post decided lets go back to basics and yes I have a bunch of faulty hybrid drives!

GG

 

Always miss the simplest of things. 4 units that i randomly grabbed initially while testing rebuilds all exhibited the issue, sods law luck!

[ReadTheNetwork]

Ah that sucks! Well congrats you found out what the problem was. Sods law that you had quite so many HDDs with the same problem. Would check disk repair do any good for them?

[Tefters]

Ah that sucks! Well congrats you found out what the problem was. Sods law that you had quite so many HDDs with the same problem. Would check disk repair do any good for them?

 

Lenovo warranty Dude out today to replace them...