Think Innovation Minute: X1 Carbon - Connectivity. New ThinkPad X1 Carbon: Design Heritage. The New ThinkPad X1 Carbon: Incredible Engineering. Meet the New ThinkPad X1 Carbon: #Lenovohangouts. Lenovo First Look: New ThinkPad X1 Carbon. If it bombs, verify what's being returned as %model% and be sure your driver folder name matches EXACTLY (case sensitivity, spaces, and all).Lenovo ThinkPad X1 Carbon (2014 2nd Gen) Lenovo ThinkPad X1 Carbon (2014, 2nd Generation, Gen 2)
I'd be sure to make backups before altering the scripts, and be sure to check BDD.log after making the mods to verify it's picking up a usable name for your driver folder. I don't have any lenovos in my fleet any more, but here's some info on scripting tweaks that should tame the lenovo beast.
The Lenovo naming scheme has been problematic in that %model% (for otherwise identical hardware) can change mid-run and so MDT has a hissy about it because the drivers that worked yesterday can't be located.
If it's windows drivers causing the problem, the rest of the essay is in play. WinPE driver issues are a separate problem that gets addressed differently. If so, its a windows driver problem as opposed to WinPE.
圆4 drivers, 圆4 OS, enabled in the deployment share which it most likely is.įirst off, just for clarity - Does it PXE OK, lay down the image, and THEN die? You also want to make sure platforms match, 圆4 usually. You also need to make sure your selection profile is set to the correct driver folder in out of box drivers. If you are using selection profiles(may be easier to start with but harder to manage down the line with many models), your inject driver step should have the correct selection profile selected and I still tell it to inject all drivers here. The driver group in out of box drivers must match exactly to how it is on the device, its a simple text string so it must match exactly. If using total control, it should be set to inject all with nothing as the selection profile with a prior step that sets the driver group task sequence variable. You want to check the driver step in your task sequence, make sure its set correctly. It really depends how you are managing your drivers, if you are doing total control and choosing by model name then its slightly more complex. If you are at a desktop, you've already net booted, laid down an OS and went through OOBE. You need to look at your driver management, not boot images. For some reason my home lab didn't require them to be manually entered, but they were required here at the office.īoot images only come into play when you are trying to PXE boot. SOLVED: I looked up the Lenovo WinPE driverpacks for our specific models and injected those and that was the problem. When I check the device manager, none of the drivers are installed, including the ethernet driver, which would make sense why it's not connecting (despite the fact that it says the connection is OK). When I get this error, I click cancel and it kicks me to the desktop.
I'm at a complete loss as to what this could be, and I'm not sure where to go from here.ĮDIT: I'm thinking that it's a driver issue. performing diskpart clean on the affected laptop deleting the Audit.log file within the share and recreating it with the same name but as a blank file
verifying the passwords and accounts are correct in the Rules and I'm the bootstrap.ini making all references to the share as IP instead of NetBIOS names. Yesterday, we successfully deployed the image to a Hyper V VM, and this morning it worked again however, when we went to test the Deployment on our physical laptops, we started getting this error. I recently set up an MDT image along with a WDS server. If you have suggestions for the sidebar, let us know! We're always looking for great resources.