- Fri, Jun 28 2013 at 12:21 am #14380
I have recently setup MDT 2012 and WDS for PXE booting.I also setup MDT with the driver folder structure and the selection profiles and task sequence entries and downloaded the Dell Cab files from here:
and imported them to the correct folders.
I am having a problem with the Dell E5420, it wont install any drivers except the LAN.This morning I tested on a Latitude E6400 ATG and it worked except for the base system device and Broadcom USH.
I also cant get it to load the Product key from the answer file, when I add the product key in the Shell setup specialize pass it fails at “setting up computer for first use”.I remove the key and it works again.
So to summarize:
1.E5420 Driver problem
2.Specialize pass product key problem
attached is the xml file of my task sequence
- Fri, Jun 28 2013 at 1:20 am #14381
- Fri, Jun 28 2013 at 8:25 am #14395Joseph MoodyModeratorMember Points: 1,918Rank: 3
Let’s tackle the first problem right now. Your task sequence looks good. The only difference I saw was that you specify all drivers should be installed from the selection profile where I specify only matching drivers. That shouldn’t make a difference though.
Can you take a screenshot of your Out of Box Drivers folder and post it? Make sure every folder is completely expanded. I am only interested in the folder layout.
- Fri, Jun 28 2013 at 9:20 am #14397
- Fri, Jun 28 2013 at 10:17 am #14401
I also found this regarding the license problem. I am just worried if this is actually legal?especially since we do not have VL for Windows 7
- Mon, Jul 1 2013 at 3:55 am #14426
Ok worked around the license problem by reverting back to MDT 2010.
Still struggling with the driver problem though, the task sequence does not install any drivers if I use my custom made image.But when I use the Win7 source files it works fine.
Custom built XP works fine aswell regarding the drivers.
- Mon, Jul 8 2013 at 3:59 am #14543Joseph MoodyModeratorMember Points: 1,918Rank: 3
Did you find a workaround for your custom image? You might want to look at editing the devicepath registry key manually.
Add your deploymentshare to the end of that key’s value. Let me know if this helps you work around it.
- Mon, Jul 8 2013 at 4:07 am #14544
At the moment the custom image is a no-go.I have reverted back to MDT 2010 and using the source files from the Dell Disk.As soon as I use a WIM that I customized and captured from my referenced computer the license and the drivers don’t work.
This is not ideal as it adds alot of time to the whole reimaging procedure.
- Mon, Jul 8 2013 at 6:11 am #14547
A copy of the BDD.LOG and ZTIDrivers.log would be helpful to troubleshoot the problem.
Also, what OS and bitness are you using? You mentioned Windows 7 and XP, but you haven’t mentioned whether they are x86 or x64. Have you double-checked that you got the right drivers? Dell’s support site has this nasty habit of changing OS on you if you’re not looking. Just last year I tried to deploy a Server 2012 box with Server 2003 R2 drivers. (For the record, it didn’t work!) It’s very common for the LAN drivers to be bundled x86 and x64 together. So, there’s a possibility that you may have the wrong bitness drivers.
- Mon, Jul 8 2013 at 6:29 am #14548
Currently only X86.I downloaded the Dell Cab files made specifically for deployments, and the drivers do install when I use the Dell source files from the disk.As soon as I use a Sysprepped image nothing works.
And yes I know what you mean when you talk about the Dell website changing OS selection, very irritating.
Some sites where saying that there might be a “C:\Drivers” folder that needs to be removed before sysprepping but I have no such folder.
I will have to do a deployment with the old Image to get you those log files.
- Wed, Jul 10 2013 at 11:45 am #14629danny chungParticipantMember Points: 0Rank:
I am new to this windows server 2012 environment and need people’s advice if you can.
I too just install the MDT 2012 and the SCCM 2012 on Server 2012. I was troubleshooting why the config mgr 2012 unable to push the windows 7 image to the machines but it could perform the WOL. Anyhow, I was troubleshooting the pxe boot image and so forth.
Some how, when I reboot the Server 2012 and log back either on the domain or locally. It took me to the command prompt screen c:\users\danny. It would not let me see any other desktop screen like application icons, control panel, search, start, settings, etc… no matter I press ctrl + esc, move my mouse trying to point the right bottom corner and nothing happen. It looks so abnormal.
How do I get back to normal windows screen environment? many thanks in advance..
- Fri, Jul 12 2013 at 8:01 am #14667Michael PietroforteKeymasterMember Points: 32,919Rank: 4
Danny, could it be that you somehow switched to Server Core? This is possible in Windows Server 2012.
- Fri, Jul 12 2013 at 9:06 am #14668
Here are the logs
- Fri, Jul 12 2013 at 9:09 am #14669
- Sat, Jul 13 2013 at 2:10 pm #14683
In your ts.txt that you posted, you have a task sequence that is setting the Task Sequence Variable DriverGroup001 to Windows7\x86\%Model%.
In line 602 of the BDD.log, the variable DriverGroup001 is being set to Windows7\Latitude E5420.
So, when the task is looking for drivers, it is looking in a non-existant location based on the screenshot you posted.
- Mon, Jul 15 2013 at 4:53 am #14686
That is an old TS sorry, it has changed in the meanwhile since whe only use one architecture x86
Like I said it installs the drivers when I use the unmodified, not-sysprepped and captured image.
- Mon, Jul 15 2013 at 4:56 am #14687
Should I make that registry setting change before sysprep?
- Mon, Jul 15 2013 at 6:53 am #14688
Then something is happening during your OS deploy or sysprep that is causing this issue. It doesn’t sound like your OS deploy task is the problem… it sounds like the problem may be somewhere in your process for creating your base image. Are you creating your base image in a VM? Is the process automated or do you make them manually?
I create a monthly ‘gold’ image in MDT 2012 every month that includes base OS, Office, and all of the updates up to that month in a Hyper-V VM. We then use that image on several different hardware types using a process very similar to Joseph’s article. I’ve never had any kinds of problems with drivers when we deploy that image to physical hardware.
- Mon, Jul 15 2013 at 7:42 am #14690
I create the custom image in HyperV, install all the programs and windows updates
and then sysprep and capture with MDT “Sysprep and capture” task sequence.
Only thing I might be doing differently is I use the DELL OEM disk that comes with the computers for the license to work.
- Tue, Jul 16 2013 at 6:39 am #14720
Your MDT install is in a state of flux and the screenshots, logs, etc. are all from varying states/versions of the environment. That is making it very hard to troubleshoot the issues you’re having.
At this point, you may want to engage Dell or Microsoft support on the issue. Another option would be to switch to VL media/licenses in the future since it is very common for OEM media to contain vendor customizations that could be the cause of your problems.
- Tue, Jul 16 2013 at 10:28 am #14739
Thanks for all the help so far guys.
- You must be logged in to reply to this topic.