I can't financially, but mentally I retired already. What 60-year careers could look like: thank you! I am ready to retire right now. Full Stop! Ready to work until you are 80? IT & Tech Careers It would be nice if I had a driver that didn't crash an install. Besides, they need to go in and lock the BIOS before shipping anyway, might as well just re-check the enable box while they're there, it's faster than installing a driver. I don't want to manually install the driver either, though the techs do need to encrypt laptops, so the extra time isn't really an issue. I don't want to disable the driver and run the installer after imaging because automating that might cause problems with other models, and I don't want a bunch of model specific images.
So, I found the problem, and a workaround, but no real solution. One last google search, and I found a year old thread on Spiceworks where someone was discussing a BSOD on different hardware, and in passing the previous model of Latitude was mentioned having a problem with the free-fall sensor, and that disabling it in the BIOS solved the issue. 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 kommentar(er)
