none
Task Sequence appears to stop after applying OS WIM RRS feed

  • Question

  • I'm trying to image a Lenovo e555 with MDT but no matter what I've tried it seems to stop at the same point with out error. For context I'm using a standard task sequence with a custom WIM. I have had no issues with this setup in previous deployments for other models. I added the drivers for this deployment just like I have for other models. I am not using selection profiles. At this point the only drivers on my MDT server are the drivers for this particular model laptop. 

    So I boot as normal and start the task sequence. It injects the drivers and applies the OS. When it restarts after applying the OS it comes to a blank screen with no cursor. I've left the laptop on for several hours with no movement. I've go back and looked at the smsts.log and it appears as if the task sequence is creating a system partition and assigning it to C:. It then creates the OSDisk partition and assigns it to D:. I'm not sure why this is happening as previous deployments did not exhibit this formatting. I've attached the log for investigation. If anyone can assist I would appreciate it!  

    SMSTS.log http://1drv.ms/1PaZMg6

    Thursday, April 30, 2015 6:53 PM

Answers

  • I have no idea how this work but it does.

    1. I removed the AMD Display and Chipset drivers I added from the Lenovo website.

    2. I added the AMD Display and Chipset drivers from the AMD website.

    3. Updated deployment share and attempted task sequence again. Still nothing

    4. I decided to attempt imaging from a USB with the base ISO downloaded straight from the Volume license center.

    5. Instead of starting the image after the options come up I first wanted to go through the troubleshooting to see if I could get the previous MDT image to work. Restore and reset didn't work so I just clicked on continue to Windows 8.1. To my surprise the Windows logo popped up and the task sequence finished out.

    6. The odd thing now however is the USB with the base OS must be plugged in to boot to the OS. If the USB is removed it goes back to the same blank screen as previously mentioned.

    Something weird is going on and I didn't have time to investigate it as the laptops needed to be working on site Monday morning. I've never experienced any issue like this before and hope to never again. It has to be something with this particular model of Lenovo and drivers. I will not be going down this path further as I've switched to Dell Latitudes. I hope this info, if they go down this same path, will make someone life much easier.

    • Marked as answer by CALaboratory Tuesday, May 5, 2015 6:16 PM
    Tuesday, May 5, 2015 3:46 PM

All replies

  • Is your custom wim captured on a VM?  It will probably be interesting to see if any 3rd party drivers are in the WIM.  There have been several threads where the Intel RSTe drivers have been causing issues.  Can you post the BDD.log and setupapi.dev.log also?

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, April 30, 2015 8:21 PM
    Moderator
  • Is your custom wim captured on a VM?  It will probably be interesting to see if any 3rd party drivers are in the WIM.  There have been several threads where the Intel RSTe drivers have been causing issues.  Can you post the BDD.log and setupapi.dev.log also?

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Yes it was captured from a VM. I will post those logs as soon as I can gather them.
    Thursday, April 30, 2015 8:32 PM
  • Did you modify anything to make it to look for D:\? Your logs show "User specified local data drive d:" but there is no D: drive listed

    User specified local data drive D:	TSManager	4/27/2015 7:51:52 AM	1380 (0x0564)
    D:\_SMSTaskSequence does not exist	TSManager	4/27/2015 7:51:52 AM	1380 (0x0564)
    Creating directory D:\_SMSTaskSequence	TSManager	4/27/2015 7:51:52 AM	1380 (0x0564)
    uRet == ERROR_ALREADY_EXISTS, HRESULT=80070003 (e:\nts_sms_fre\sms\framework\tscore\utils.cpp,916)	TSManager	4/27/2015 7:51:52 AM	1380 (0x0564)
    Failed to create D:\_SMSTaskSequence (3)	TSManager	4/27/2015 7:51:52 AM	1380 (0x0564)
    Failed to create user-specified local data path D:\_SMSTaskSequence. Error 0x80070003	TSManager	4/27/2015 7:51:52 AM	1380 (0x0564)
    Volume C:\ has 499425984512 bytes of free space	TSManager	4/27/2015 7:51:52 AM	1380 (0x0564)
    Volume E:\ is not a fixed hard drive	TSManager	4/27/2015 7:51:52 AM	1380 (0x0564)
    Volume V:\ has 489168896 bytes of free space	TSManager	4/27/2015 7:51:52 AM	1380 (0x0564)
    Volume X:\ is not a fixed hard drive	TSManager	4/27/2015 7:51:52 AM	1380 (0x0564)
    Volume Z:\ is not a fixed hard drive	TSManager	4/27/2015 7:51:52 AM	1380 (0x0564)
    TSM root drive = C:\	TSManager	4/27/2015 7:51:52 AM	1380 (0x0564)
    


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Thursday, April 30, 2015 9:20 PM
  • I was able to get rid of the by removing the check on the Format Disk step to "Create extra "Active" partition. Unfortunately the issue still persists. Attached are the logs from the latest attempt.

    BDD: http://1drv.ms/1Ivbv9B

    SMSTS: http://1drv.ms/1PaZMg6
    Friday, May 1, 2015 12:41 PM
  • Why don't you try creating a new task sequence, but don't modify the "Format and Partition Disk" tasks, MDT will handle it just fine on it's own. You can copy and paste other tasks from your original sequence into the new one. You might have something else going on that could take too much time to track down.

    If this post is helpful please vote it as Helpful or click Mark for answer.

    Friday, May 1, 2015 1:44 PM
  • You're missing drivers

    Skipping Device USB\ROOT_HUB20&VID1022&PID7808&REV0011 No 3rd party drivers found. 3	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device ROOT\mssmbios No 3rd party drivers found. 1	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device PCI\VEN_1022&DEV_1426&SUBSYS_511017AA&REV_00 No 3rd party drivers found. 13	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device PCI\VEN_1022&DEV_1426&SUBSYS_511017AA&REV_00 No 3rd party drivers found. 13	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device PCI\VEN_1022&DEV_1426&SUBSYS_511017AA&REV_00 No 3rd party drivers found. 13	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device PCI\VEN_1022&DEV_780E&SUBSYS_511017AA&REV_11 No 3rd party drivers found. 11	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device ROOT\SWENUM No 3rd party drivers found. 1	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device ACPI\VEN_PNP&DEV_0C02 No 3rd party drivers found. 3	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device ACPI\VEN_PNP&DEV_0B00 No 3rd party drivers found. 3	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device ACPI\VEN_PNP&DEV_0C01 No 3rd party drivers found. 3	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device ACPI\VEN_PNP&DEV_0000 No 3rd party drivers found. 3	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    

    Also try removing your UFD once you get to the wizard when you first boot up. It looks like the computer rebooted and then booted to back to where you have your PE image instead of to the hard drive.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Friday, May 1, 2015 1:50 PM
  • You're missing drivers

    Skipping Device USB\ROOT_HUB20&VID1022&PID7808&REV0011 No 3rd party drivers found. 3	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device ROOT\mssmbios No 3rd party drivers found. 1	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device PCI\VEN_1022&DEV_1426&SUBSYS_511017AA&REV_00 No 3rd party drivers found. 13	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device PCI\VEN_1022&DEV_1426&SUBSYS_511017AA&REV_00 No 3rd party drivers found. 13	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device PCI\VEN_1022&DEV_1426&SUBSYS_511017AA&REV_00 No 3rd party drivers found. 13	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device PCI\VEN_1022&DEV_780E&SUBSYS_511017AA&REV_11 No 3rd party drivers found. 11	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device ROOT\SWENUM No 3rd party drivers found. 1	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device ACPI\VEN_PNP&DEV_0C02 No 3rd party drivers found. 3	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device ACPI\VEN_PNP&DEV_0B00 No 3rd party drivers found. 3	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device ACPI\VEN_PNP&DEV_0C01 No 3rd party drivers found. 3	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)
    Skipping Device ACPI\VEN_PNP&DEV_0000 No 3rd party drivers found. 3	ZTIDrivers	4/30/2015 11:11:56 PM	0 (0x0000)

    Also try removing your UFD once you get to the wizard when you first boot up. It looks like the computer rebooted and then booted to back to where you have your PE image instead of to the hard drive.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    My apologies, I forgot to mention that in a effort to rule out drivers I disabled the injection step. As mentioned previously it had no affect on the image process. 

    Additionally i'm using PXE instead of a UFD to boot to WinPE. Also the Hard drive is set first in the boot order.

    I will attempt to recreate the task sequence and report back with the results. Thank you for the assistance.

     

    Friday, May 1, 2015 2:04 PM
  • I have no idea how this work but it does.

    1. I removed the AMD Display and Chipset drivers I added from the Lenovo website.

    2. I added the AMD Display and Chipset drivers from the AMD website.

    3. Updated deployment share and attempted task sequence again. Still nothing

    4. I decided to attempt imaging from a USB with the base ISO downloaded straight from the Volume license center.

    5. Instead of starting the image after the options come up I first wanted to go through the troubleshooting to see if I could get the previous MDT image to work. Restore and reset didn't work so I just clicked on continue to Windows 8.1. To my surprise the Windows logo popped up and the task sequence finished out.

    6. The odd thing now however is the USB with the base OS must be plugged in to boot to the OS. If the USB is removed it goes back to the same blank screen as previously mentioned.

    Something weird is going on and I didn't have time to investigate it as the laptops needed to be working on site Monday morning. I've never experienced any issue like this before and hope to never again. It has to be something with this particular model of Lenovo and drivers. I will not be going down this path further as I've switched to Dell Latitudes. I hope this info, if they go down this same path, will make someone life much easier.

    • Marked as answer by CALaboratory Tuesday, May 5, 2015 6:16 PM
    Tuesday, May 5, 2015 3:46 PM
  • Are you using a custom wim on the machines that are having issues?  I have seen a number of threads with Lenovo boxes having driver issues and several of them were root caused down to some drivers in the captured image.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, May 5, 2015 5:43 PM
    Moderator
  • It was a custom WIM captured from a VMWare workstation VM.
    Tuesday, May 5, 2015 6:16 PM