Just a FYI if anyone finds this thread. We found a VMware host where everything worked just fine then found out the network driver files on the VMware hosts where I was having issues were out of date. So the root cause was the state of the VMware environment and had nothing to do with OSD.
From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Kaminski Sent: November 18, 2015 11:21 AM To: [email protected] Subject: [MDT-OSD] Driver Injection on vSphere Nightmare Just looking for some suggestions since I am wasting far too much time trying to get driver injection working in a vSphere environment (of all things). If I load a virgin ISO of Windows 7 SP1 x64 Enterprise from MSDN I can install the OS without a network driver. So no big deal I just need the network driver injected before I load VMware tools on the VM. But when I go into the SCCM environment I need to put the network driver into my boot media and SCCM I get this nice little error "Windows Setup could not configure Windows to run on this computer's hardware." I then dig through the setuperr.log and find this error that suggests that there is a storage driver issue. 2015-11-12 14:00:29, Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\System32\scecli.dll,SceSysPrep', returned error code 1208[gle=0x000003e5] 2015-11-12 14:00:29, Error [0x060435] IBS Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x4b8 So I found out how to get the driver files from the VMware tools installation after they are installed and no luck. I then go to try using driver magician to extract the drivers and that does not help at all. The customer was using the SCSI device LSI Logic SAS and I tried the LSI Logic Parallel with no luck. Recently I tried the paravirtualization configuration and driver with the same error. I am starting to mistrust the customer's WIM but when I open it up I see the default Windows 7 LSI Logic drivers in there but they don't seem to work if I only inject the network driver. I've set up imaging with VMware a number of times so I am puzzled as to why this is happening. Usually it is pretty easy. I'm basically out of drivers and VM configurations with the SCSI adapter and I am wondering if anyone can spot something I am missing.
