Certain Dell models are not enjoying my Universal image
-
@mlnancejr8808 I edited your posting because you did not clear out your password and your product key was plainly visible. I also put it in a code statement to make it easier to read/follow.
-
When I’ve seen this happen it is because a device driver fails to install. Its been a while since I broke an install, but at the screen where it says setup can’t complete and before it reboots, you can hit something like shift f10 or something like that and break out to a command shell so you can look at the setup files.
Actually I was just pulling the updated driver cabs from dell for win10.
You may want to look at this page: http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.dell-command-deploy-driver-packs-for-enterprise-client-os-deployment -
OK I found the steps
-
On the same error screen press SHIFT+F10 and it will open up a black Window. (a command prompt window)
-
In the black windows type the word “regedit”(without the inverted commas and hit enter. That will open the registry editor.
In the Registry Editor…
Browse to…
HKLocal machine/SYSTEM/SETUP/STATUS/ChildCompletion, and after highliting childcompletion,on the right hand side check for setup.exe. if the value is 1 change it to
3 (by double clicking on setup.exe and changing the value shown in the box).
Then close the registry editor and then also close the black window.
Then click on OK for the error and the computer will restart and the installation may complete. just try it and let me know if it worked.
That will let the system reboot. Once that is done you can get into the installer logs to figure out what driver did not install correctly.
-
-
Now to moving forward: How do you create your reference image (one for all)? Are you doing that through MDT? If so lets dig into that a bit more.
-
@george1421 I am building my reference image on a VM and then the unattend.xml in Windows System Image Manager.
-
@mlnancejr8808 You are hand editing the unattend.xml file? Eeek…
How are you injecting the drivers? Are you installing every driver for every hardware into that vm or are you injecting the drivers through some other method?
Just for full disclosure I have one image for 14 Dell computers
-
I am using driverpacks. Placing them in C:\Windows\inf\Drivers
-
@mlnancejr8808 said:
I am using driverpacks. Placing them in C:\Windows\inf\Drivers
Again are you installing all drivers for all models? (not being difficult, the path forward is different based on how you answer)
-
@george1421 No I am not installing all drivers for all models.
-
@mlnancejr8808 How then are you deploying to a 755, 380 and 390 system (assuming they would install correctly)?
I’m going to bump this to chat since we can get faster turn around. Look for the red mark next to the balloon comment near your icon at the top of the browser window.
-
@george1421 This didn’t work.
-
OK from the chat session, the OP is downloading the drivers from driverpacks.net and stuffing them into the c:\windows\inf\drivers folder. My bet is that he is missing or have a driver that is close to what he needs but it is crashing.
My recommendation would be to download the driver packs from the Dell using the link I provided earlier.
In addition I can give you some hints on how to load these drivers how we do it.
I have a task sequence in MDT that does this to the reference image on the VM.
REM Create directory to load drivers if NOT EXIST "C:\Drivers" mkdir "C:\Drivers" REG ADD "HKLM\Software\Microsoft\Windows\CurrentVersion" /v DevicePath /t REG_SZ /d "C:\Drivers;%SystemRoot%\inf;" /fFirst I create a directory to hold the drivers and then I update the registry to tell the computer to look in the C:\Drivers folder first before looking in the C:\Windows\inf folder. This will allow windows to find the vendor specific drivers first before using the windows built in drivers.
-
@george1421 What is MDT that you are referring to?
-
Now I can tell you in concept what I do. I go to the dell site and download the cab files for each model I want to support. Those cab files contains all of the drivers for that specific model. I use 7Zip and extract the driver files from the cab file. Through the magic of a bash shell script I push the contents of that exact hardwares expanded cab file to the target computer post image deployment. When the sysprepp’d image boots for the first time it finds all of its drivers in the c:\drivers folder.
-
@mlnancejr8808 said:
@george1421 What is MDT that you are referring to?
Microsoft Deployment Tools. It is a free tool from MS used to build reference images. Using the lite touch method I build a new reference image every quarter. I just launch the MDT deployment and come back a few hours later with a reference image ready to sysprep.
-
@mlnancejr8808 To do the C:\Drivers folder and update the registry you don’t need MDT. You can do this manually or via a cmd file when you build your reference image in Audit mode. I love MDT because our reference image is exactly the same every time we create it.
If you were going the MDT route to build your reference image I would also say to include the WinPE drivers right in the MDT reference image.
-
@george1421 The only Drivers I am seeing for the Op755 is the WinPE Cab…will that work?
-
@mlnancejr8808 said:
@george1421 The only Drivers I am seeing for the Op755 is the WinPE Cab…will that work?
Yeah, that’s pretty old. Its not certified for Win7 only XP. With that said, I would bet the windows built in drivers will work for that. Or just load the 780 drivers for Win7. Since this until is about 10 years old, all you can do is wing it.
-
@george1421 HAHAHAH! Thats awesome cause I have about 350 units Im gonna have to wing it on!
-
@mlnancejr8808 Make one work, then all will work.
