Task Sequence hangs on Dell models with SSD
Ok. I'm posting this hoping someone has an insight that I'm missing.
Running SCCM 2012 rtm with MDT 2012 integrated. I'm running a fairly basic MDT based Win7 64bit TS to load a thin WIM, and several apps (office, citrix, etc). So, now I'm testing driver injection on various models. I have driver packages setup for most of the Dell laptops models we have in production, and then I let the TS scan for drivers just in case we run up against a strange model that isn't standard but we might have a handful of these other models floating around someplace.
So, I run my TS on a Dell E6530. All works fine.. drivers load, TS loads great. Then someone hands me an E6530 with an SSD installed (Samsung SM841 SSD, which is a 128GB drive). I run the TS, and it runs through OS install and setup, driver injection, then it installs a couple packages (Adobe reader for example), then hangs during an application package install in the TS. The app install where it hangs is a traditional package (not a cm12 app). No errors, it just stops like it never completes. After the app hangs long enough for it's install time limit to pass, the TS fails saying it was cancelled.
So, I start digging around...thinking I must not be formatting the SSD right or something, and in tinkering I discover that if I do not install a video driver for the HD Graphics 4000 adapter, and just let windows install the generic VGA adapter, the TS completes just fine. The screen is 800x600 resolution when we're done, but its complete. So, that makes me think its NOT an SSD formatting issue, but a driver issue. I pull new drivers from Intel (mine was pulled from Dell's SCCM Cabs, and turned out to be a few years old), but that didn't help.
We're hanging on a Citrix offline plugin installation. Does anyone have any idea why a video driver would create this problem? As a workaround, I could put a video driver injection step at the end of the TS, and avoid the issue, but I'm hoping someone might have a clue what might be causing the issue. I did check and based on Intel's scans, all my Intel driver codes are up to date. (I had thought that maybe my Intel vid driver was conflicting with some other intel chipset driver or something weird).
Anyone have ideas on this?
post edited by EdwardKK - 2013/10/11 12:35:25