![]() I was starting to think there might be something wrong with the WDS server, and had resigned myself to re-build it today. I may not have tried hard enough in that respect. At the very least, I couldn't find any logs, or any way to enable logging to find the problem. There's no indication this early on in the process that nails down exactly which driver is causing the issue. I disabled all but the drivers for the specific model. I completely deleted and re-created the driver database on WDS, it was overdue anyway. ![]() ![]() I loaded the fresh image from WDS, and BSOD. So I started fresh, built a shiny new Win7 image (2 days to install all of the updates.ugh) with the latest drivers and software, sysprepped and captured it. ![]() This indicated that it was likely a driver issue, maybe something in the image conflicting with drivers installing from WDS. It happened right after devices initialized, and right before OOBE. My first course of action was to re-create the issue, and to pay attention to when the BSOD was happening. After some investigation, it seems that laptops weren't imaging correctly, and were coming up with a blue screen before the imaging process was complete. On Friday afternoon our technicians informed me that the imaging server had stopped working. I just resolved an imaging issue that has been a pain in my butt all week.
0 Comments
Leave a Reply. |