Has anyone on this forum ever gotten a Lenovo X1 Carbon to successfully build via CM2012 OSD?    I have not met or spoken to anyone that has gotten this device to work.  If you did get it working how?  

WinPE works.  It has a network connection but once the system reboots into Windows the network adapter drivers don't load and you have no network connectivity.  We have tried many things to fix it and nothing works.

Microsoft tech support won't help since it is a Lenovo issue.
Lenovo tech support won't help since we building the device in a "non standard way"

So we need help and if you have the answer we are all

I deploy X1 Carbons with SCCM 2012 R2. This might seems like a dumb question but, did you add the following driver to your boot image and your X1 Carbon driver package?

http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS030606

• Edited by Brandon M. White Wednesday, July 16, 2014 5:11 PM Clarification

I deploy X1 Carbons with SCCM 2012 R2. This might seems like a dumb question but, did you add the following driver to your boot image and your X1 Carbon driver package?

http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS030606

• Edited by Brandon M. White Wednesday, July 16, 2014 5:11 PM Clarification

Yes, we have that driver and many others in our X1 Carbon Driver Package.   I have even removed all X1 Carbon drivers and the driver package and re-added them and that did not work either. 

As I said the WinPE part works.  It boots off of the network, finds the CM2012 DP, installs the OS, sets the local Admin Password.  It lays down the X1 Carbon Driver Package and then reboots.  When it comes back from the reboot it is now running Windows 7 and I have no IP address.   

so far you are the only tech I've spoken too who has gotten a X1 Carbon to work via CM2012 so any advice you can provide would be awesome!

Yes, we have that driver and many others in our X1 Carbon Driver Package.   I have even removed all X1 Carbon drivers and the driver package and re-added them and that did not work either. 

As I said the WinPE part works.  It boots off of the network, finds the CM2012 DP, installs the OS, sets the local Admin Password.  It lays down the X1 Carbon Driver Package and then reboots.  When it comes back from the reboot it is now running Windows 7 and I have no IP address.   

so far you are the only tech I've spoken too who has gotten a X1 Carbon to work via CM2012 so any advice you can provide would be awesome!

One thing I've noticed, in the WinPE part of the install I do have a step called "apply network settings"  this step is set to "stop on error".  the TS goes by this step and does NOT join the system to the domain.  

I ran a CM2012 report to look at the running TS.   On this same step it reports the following.

DNS Domain

DNS domain search order: IP filter, sec enabled: false no adapters found in environment.  Performing global configuration only.   

And again, it reboots after it installs the X1 Carbon drivers package and I lose my network adapter and IP address.  

One thing I've noticed, in the WinPE part of the install I do have a step called "apply network settings"  this step is set to "stop on error".  the TS goes by this step and does NOT join the system to the domain.  

I ran a CM2012 report to look at the running TS.   On this same step it reports the following.

DNS Domain

DNS domain search order: IP filter, sec enabled: false no adapters found in environment.  Performing global configuration only.   

And again, it reboots after it installs the X1 Carbon drivers package and I lose my network adapter and IP address.  

I'm not sure if this will help, but it is the exact task sequence that I run on my X1's;

1. Restart in Windows PE
2. Format and Partition Disk
3. Apply Operating System
4. Apply X1 Carbon Drivers (With WMI Query)
5. Apply T440p Drivers (With WMI Query)
6. Apply T430 Drivers (With WMI Query)
7. Apply T420 Drivers (With WMI Query)
8. Apply X230 Drivers (With WMI Query)
9. Run PowerShell Script
10. Apply Windows Settings
11. Setup Windows and Configuration Manager
12. Restart Computer (The currently installed default operating system)
13. Join Domain or Workgroup
14. Run PowerShell Script
15. Install Software
16. Restart Computer (The currently installed default operating system)

I'm not sure if this will help, but it is the exact task sequence that I run on my X1's;

1. Restart in Windows PE
2. Format and Partition Disk
3. Apply Operating System
4. Apply X1 Carbon Drivers (With WMI Query)
5. Apply T440p Drivers (With WMI Query)
6. Apply T430 Drivers (With WMI Query)
7. Apply T420 Drivers (With WMI Query)
8. Apply X230 Drivers (With WMI Query)
9. Run PowerShell Script
10. Apply Windows Settings
11. Setup Windows and Configuration Manager
12. Restart Computer (The currently installed default operating system)
13. Join Domain or Workgroup
14. Run PowerShell Script
15. Install Software
16. Restart Computer (The currently installed default operating system)

Our TS looks similar

We are using MDT and UDI in our task sequence.  

1. restart into winpe
2. set some UDI variables
3. format partition
4. run UDI wizard (which captures some user input)
5. apply operating syste
6. apply windows settings
7. apply network settings
8. apply drivers based on WMI query for 8 different models (which works except X1)
9. setup Windows and ConfigMgr
10. join machine to domain (another post said to do this for the X1)
11. restart
12. install applications
13. run powershell scripts to move machine/user to OU's specified in UDI steps.  
14. reboot

Where is your APPLY NETWORK SETTINGS step?  and what does your powershell script do in your step 9?  

Our TS looks similar

We are using MDT and UDI in our task sequence.  

1. restart into winpe
2. set some UDI variables
3. format partition
4. run UDI wizard (which captures some user input)
5. apply operating syste
6. apply windows settings
7. apply network settings
8. apply drivers based on WMI query for 8 different models (which works except X1)
9. setup Windows and ConfigMgr
10. join machine to domain (another post said to do this for the X1)
11. restart
12. install applications
13. run powershell scripts to move machine/user to OU's specified in UDI steps.  
14. reboot

Where is your APPLY NETWORK SETTINGS step?  and what does your powershell script do in your step 9?  

After you've got the X1 with Windows 7 installed, install all the drivers manually and use this tool http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d to grab the drivers and create a new driver package and do test with it. This sounds like a driver issue to me...

• Edited by Narcoticoo Wednesday, July 16, 2014 8:55 PM

After you've got the X1 with Windows 7 installed, install all the drivers manually and use this tool http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d to grab the drivers and create a new driver package and do test with it. This sounds like a driver issue to me...

• Edited by Narcoticoo Wednesday, July 16, 2014 8:55 PM

7/16/2014 1:39:46 PM 3532 (0x0DCC)
CLibSMSMessageWinHttpTransport::Send: URL: MGH-SCCM12-01.acme.org:80  CCM_POST /ccm_system/request TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
Error. Received 0x80072ee7 from WinHttpSendRequest. TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
unknown host (gethostbyname failed) TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
hr, HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8919) TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
sending with winhttp failed; 80072ee7 TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
End of retries TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
Send (pReply, nReplySize), HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,1950) TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
failed to send the request TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
DoRequest (sReply, false), HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,4048) TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
Failed to send status message (80072ee7) TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
smStatusMessage.Send(), HRESULT=80072ee7 (e:\nts_sccm_release\sms\fr

the repeating log entries above are a sure sign that the network driver isn't loading, or is loading but is connected to a network that isn't working, or the driver is too slow to initialise.

check the Panther setupact and setuperr logs etc - is Windows setup finding the correct driver for the USB NIC (it's a Lenovo USB Ethernet adaptor? probably using an ASIX chipset driver?)

when the pc is in a failed-to-build state, logon to it with the local admin account and check if a device driver is loaded or not. you could place a pause in the TS and open a console during the TS to see what the state of play is.

7/16/2014 1:39:46 PM 3532 (0x0DCC)
CLibSMSMessageWinHttpTransport::Send: URL: MGH-SCCM12-01.acme.org:80  CCM_POST /ccm_system/request TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
Error. Received 0x80072ee7 from WinHttpSendRequest. TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
unknown host (gethostbyname failed) TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
hr, HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8919) TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
sending with winhttp failed; 80072ee7 TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
End of retries TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
Send (pReply, nReplySize), HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,1950) TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
failed to send the request TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
DoRequest (sReply, false), HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,4048) TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
Failed to send status message (80072ee7) TSManager 7/16/2014 1:39:46 PM 3532 (0x0DCC)
smStatusMessage.Send(), HRESULT=80072ee7 (e:\nts_sccm_release\sms\fr

the repeating log entries above are a sure sign that the network driver isn't loading, or is loading but is connected to a network that isn't working, or the driver is too slow to initialise.

check the Panther setupact and setuperr logs etc - is Windows setup finding the correct driver for the USB NIC (it's a Lenovo USB Ethernet adaptor? probably using an ASIX chipset driver?)

when the pc is in a failed-to-build state, logon to it with the local admin account and check if a device driver is loaded or not. you could place a pause in the TS and open a console during the TS to see what the state of play is.

Sounds like a really bad driver.. what's the hardware id for the device? Have you tried Google/Bing to search for alternative driver? Who's the NIC vendor? What's the model?

Sounds like a really bad driver.. what's the hardware id for the device? Have you tried Google/Bing to search for alternative driver? Who's the NIC vendor? What's the model?

I've dealt with this on the first X1 that we built.  To troubleshoot, I let the TS fail, logged into the OS, pulled up device manager, chose the network device that wasn't starting and pointed the drive install to my drivers folder in SCCM.  I got an error trying to install that way so I knew it was one of my drivers.  It turned out that there were missing files in extracted set of driver files that I was using.  So, I ended up finding the driver straight from the manufacturer of the LAN device.  Once imported, everything loaded correctly. 

I would start in device manager and see if it will install from your driver repository. 

We only brought 3 into the environment for testing and I built because we were going to bring that in as a standard.  It was halted and replaced so I've removed them from the repository. 

You say you've tried every driver.  Are you trying these drivers from Device Manager or are you funneling new drivers into your driver repository and running the TS again?

Read my post above. Find a driver that works through device manager.

so we've built a bunch of these successfully with sccm.

not sure if this would apply, but how well patched is your image?

dell referenced this on their site:

http://en.community.dell.com/techcenter/b/techcenter/archive/2013/10/07/kernel-mode-driver-framework-1-11-update-what-it-is-and-why-you-need-it.aspx

not sure if it would affect you, but could impact the injection of drivers.

as for us, we don't use the traditional task sequence based driver injection method, cause 80+ models would make for a dang long task sequence.

our TS just maps a drive to a driver location that has directories broken out by model, make, os, etc, and we just point dism at the corrrect driver dir for the model being built.

we also, just for speed sake, don't use the lenovo adapters, though I could probably test one if need be. we use the faster startech usb ethernet adapters, and those seem to work pretty reliably.

this has been working for us, and I manage the os build tools and currently have a carbon gen two that recently replaced the original x1 I had.

so we've built a bunch of these successfully with sccm.

not sure if this would apply, but how well patched is your image?

dell referenced this on their site:

http://en.community.dell.com/techcenter/b/techcenter/archive/2013/10/07/kernel-mode-driver-framework-1-11-update-what-it-is-and-why-you-need-it.aspx

not sure if it would affect you, but could impact the injection of drivers.

as for us, we don't use the traditional task sequence based driver injection method, cause 80+ models would make for a dang long task sequence.

our TS just maps a drive to a driver location that has directories broken out by model, make, os, etc, and we just point dism at the corrrect driver dir for the model being built.

we also, just for speed sake, don't use the lenovo adapters, though I could probably test one if need be. we use the faster startech usb ethernet adapters, and those seem to work pretty reliably.

this has been working for us, and I manage the os build tools and currently have a carbon gen two that recently replaced the original x1 I had.

If you haven't done what org-wiz recommended, then you will have a problem with almost every new Lenovo machine released in the past year or so.  I used DISM to inject KDF 1.11 into my images.  http://support.microsoft.com/kb/2685811/en-us

You should be seeing the "Windows could not install one or more components" during your TS. 

If you haven't done what org-wiz recommended, then you will have a problem with almost every new Lenovo machine released in the past year or so.  I used DISM to inject KDF 1.11 into my images.  http://support.microsoft.com/kb/2685811/en-us

You should be seeing the "Windows could not install one or more components" during your TS. 

I've taken a read through all of this and these last posts I believe are bang on. although to test without making any permanent changes to your OS WIM I recommend you read through this http://deploymentramblings.wordpress.com/2013/10/24/osd-injecting-the-windows-7-kernel-mode-driver-framework-kmdf/

I use this during my OSD TSs and it works brilliantly but without it you will run into issues exactly as you are describing. Good Luck.

I've taken a read through all of this and these last posts I believe are bang on. although to test without making any permanent changes to your OS WIM I recommend you read through this http://deploymentramblings.wordpress.com/2013/10/24/osd-injecting-the-windows-7-kernel-mode-driver-framework-kmdf/

I use this during my OSD TSs and it works brilliantly but without it you will run into issues exactly as you are describing. Good Luck.

I am having the same problem. Which type of Lenovo Carbon X1 do you have the problem with,.

Ours are the 20BT Model. With the Carbon X1 20A8 I have no problems booting to PXE and the deployment works great with all the task schedules and software install.s

I have a ticket into IBM Lenovo support to see what the problem is with their driver and SCCM. Even when in import the drivers in SCCM with the package from Lenovo's website you get and error that states.

drivers\Carbon X1
20BT\TP_X1Carbon_MT20BS-20BT_WB64_201502\Ethernet\N10RW10W\e1d64x64.inf - The
selected driver is not applicable to any supported platforms.

But if you install the windows 8.1 using boot dvd and install the network driver the driver works.

Will let you know if Lenovo provides a solution to this.

I am having the same problem. Which type of Lenovo Carbon X1 do you have the problem with,.

Ours are the 20BT Model. With the Carbon X1 20A8 I have no problems booting to PXE and the deployment works great with all the task schedules and software install.s

I have a ticket into IBM Lenovo support to see what the problem is with their driver and SCCM. Even when in import the drivers in SCCM with the package from Lenovo's website you get and error that states.

drivers\Carbon X1
20BT\TP_X1Carbon_MT20BS-20BT_WB64_201502\Ethernet\N10RW10W\e1d64x64.inf - The
selected driver is not applicable to any supported platforms.

But if you install the windows 8.1 using boot dvd and install the network driver the driver works.

Will let you know if Lenovo provides a solution to this.

Try the method I provided to this thread earlier.

Try the method I provided to this thread earlier.