[1903, au] Blue Screen on PCs Following Initial WDS Image

[JRA]

Hi everybody - this I didn't need...

 

My crawling W10 deployment crawls along, but hit a major snag. The golden image we built and tested on a single PC and then VMs from then on. Over the summer we tried one of every sort/generation of PC we have with a W10 disc install just to make sure they'd all run it at least and they did.

 

Tried to deploy it to my first staff test machine and hit the following:

 

 

Crap. So, tried a slightly different PC and then another, and the same thing. In fact, this now happens to anything that ISN'T the original PC or a VM.

 

Yuck.

 

I'm completely unfamiliar with WDS/MDT and W10 itself but getting there. My kneejerk is to say drivers, is it sensible to proceed that way and try and inject those with MDT?

 

Anyone got any ideas on the best way to start?

 

Thanks everybody.

[Cache]

I had that problem with conflicting USB3 drivers on Windows 7 machines, there were 2 different models of hardware where if you forced installed both drivers it would bluescreenduring deployment.

 

I'd try bring up the c drive and take a log in c:\windows\panther\ and the setup.log / setuperr.log and see if there's anything logged in there. Not sure about the MDT side of things as mines still pure WDS with additional deployment scripts.

[JRA]

Seemed to be a group policy of all things. Move OU or don't elect to rename PC to original name when WDS-ing and all is fine.

 

Okay then computer, whatever makes you happy...

 

Thanks too Cache.