none
Network link is disconnected during STATERESTORE_ RRS feed

  • Question

  • We keep running into an issue with the STATERESTORE phase of some deployment operations to newer Dell laptop models.  

    Once the local administrator is logged in and the STATERESTORE phase starts.  Sometimes it will just hang doing nothing, sometimes it recovers on its own and indicates an error in the summary screen, other times it errors out entirely, and sometimes it works fine.  

    What seems to be happening is a race condition for the network.  When it runs into a problem there is a consistent message in the system event log at the same time the BDD.log indicates something wrong that says: 

    Warning 11/7/2016 2:32:08 PM e1dexpress 27 None "Intel(R) Ethernet Connection I219-LM
     Network link is disconnected.

    Information 11/7/2016 2:32:09 PM Microsoft-Windows-UserPnp 20001 (7005) Driver Management concluded the process to install driver e1d65x64.inf_amd64_2305982aeee58c7f\e1d65x64.inf for Device Instance ID PCI\VEN_8086&DEV_156F&SUBSYS_06DC1028&REV_21\3&11583659&0&FE with the following status: 0x0.

    Information 11/7/2016 2:32:12 PM e1dexpress 32 None "Intel(R) Ethernet Connection I219-LM
     Network link has been established at 1Gbps full duplex.

    The BDD.log file indicating an interruption shows something such as:

    Microsoft Deployment Toolkit version: 6.3.8330.1000 LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    ZTIUtility!GetAllFixedDrives (False) LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    New ZTIDisk : \\LT332\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    New ZTIDiskPartition : \\LT332\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\LT332\root\cimv2:Win32_LogicalDisk.DeviceID="C:" LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    New ZTIDisk : \\LT332\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    New ZTIDisk : \\LT332\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    ZTIUtility!GetAllFixedDrives =   C: LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    Found existing task sequence state information in C:\_SMSTaskSequence, will continue LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    Not running within WinPE. LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    DeploymentMethod = UNC LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    Validating connection to \\DEPLOYLH01\MDT_Production$ LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    Mapping server share: \\DEPLOYLH01\MDT_Production$ LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    Mapped Network UNC Path Z:  = \\DEPLOYLH01\MDT_Production$ LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    Found Existing UNC Path Z: = \\DEPLOYLH01\MDT_Production$ LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    Successfully established connection using supplied credentials. LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    DeployRoot = \\DEPLOYLH01\MDT_Production$ LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    Property DeployDrive is now = Z: LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    DeployDrive = Z: LiteTouch 11/7/2016 2:32:07 PM 0 (0x0000)
    Phase = STATERESTORE LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    Validating connection to \\DEPLOYLH01\MDT_Production$ LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    Mapping server share: \\DEPLOYLH01\MDT_Production$ LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    Found Existing UNC Path Z: = \\DEPLOYLH01\MDT_Production$ LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    Found Existing UNC Path Z: = \\DEPLOYLH01\MDT_Production$ LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    Successfully established connection using supplied credentials. LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    Property DeployDrive is now = Z: LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    DeployDrive = Z: LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    Validating connection to \\DEPLOYLH01\MDT_Production$ LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    Mapping server share: \\DEPLOYLH01\MDT_Production$ LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    Found Existing UNC Path Z: = \\DEPLOYLH01\MDT_Production$ LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    Found Existing UNC Path Z: = \\DEPLOYLH01\MDT_Production$ LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    Successfully established connection using supplied credentials. LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    DeploymentType = NEWCOMPUTER LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    ResourceRoot = \\DEPLOYLH01\MDT_Production$ LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    Property ResourceDrive is now = Z: LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    ResourceDrive = Z: LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    SMS Task Sequencer found at \\DEPLOYLH01\MDT_Production$\Tools\X64, copying to C:\MININT\Tools\X64 LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    Copying \\DEPLOYLH01\MDT_Production$\Tools\X64\CcmCore.dll to C:\MININT\Tools\X64\CcmCore.dll LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)
    Copying \\DEPLOYLH01\MDT_Production$\Tools\X64\CcmUtilLib.dll to C:\MININT\Tools\X64\CcmUtilLib.dll LiteTouch 11/7/2016 2:32:08 PM 0 (0x0000)

    {Ends here}

    Depending on where the deployment process is at when the network disconnects, sometimes it auto-recovers, sometimes rebooting the computer will get it to pick up where it left off, and others it's just broken and easiest to start over.  

    I've tried various methods of specifying the driver version for selection from the Out-of-Box Drivers with selection profiles, and gone to the extent of inserting the driver into the WIM image offline with DISM.  Regardless, the OS appears to be updating the driver behind the scenes, taking down the network, and breaking the deployment process.  

    Any suggestions on how else to address this apparent network race problem, or other things to look at?



    Monday, November 7, 2016 10:07 PM

All replies

  • You can use PowerShell to export the drivers and use that version.

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it. Also if you don't post logs your problem won't be easily solved.


    Monday, November 7, 2016 11:19 PM
    Moderator
  • Sorry, I'm not sure what you're getting at here.  

    I've got the drivers in the deployment share.  I'm not sure what I would export them from or what I would do with them beyond what I've already done to include them in the selection profile and even pre-install them offline with DISM.  

    The issue seems to be with how the driver gets installed after the STATERESTORE phase starts causing a disconnect and reconnect while the LiteTouch tool is trying to do its thing.  
    Tuesday, November 8, 2016 3:41 PM
  • Never mind my other response.  This gave me enough of a seed to try something else that seems to have worked.  By using Export-WindowsDriver on the new model in question after the system was imaged to get a full set of current drivers, and using those to replace the driver set in the Out-of-Box set of drivers in the deployment share that's selected for the specific laptop model, my image appears to come up with the most recently available driver for the NIC.  So, after doing that, it didn't yank the network rug out from under the LiteTouch deployment tool.  I'll give it a few more attempts to verify I didn't just get lucky on my first go, but I'm optimistic this will solve my problem and very grateful for the pointer.  
    Tuesday, November 8, 2016 5:25 PM
  • Sorry for the brevity. What you did is what I was getting at.  It is also what I would consider best practice for driver management.

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it. Also if you don't post logs your problem won't be easily solved.

    Tuesday, November 8, 2016 6:07 PM
    Moderator