tes-com

This is realy Strange. for me to press F8 i had to modify the customsettings.ini and remove the line hideshell=yes. Now the deployment gives no errors more on the screen during the deployment. Also o errors more in the Logfiles. if i set the line hideshell back errors are back. This is very strange.

No i'm not using your script. Boot wim is build throug the MDT. First boot to PXE is ok. After the initial install i got the error. but with a retry the deployment continues. Looks like some kind of timeout loading the driver.

Hello i'm Deploying a Surface PRo 3 with MDT 2013. Using the Microsoft Driver pack Surfacepro3_150519.zip. The Surface is in the microsoft dock. I Get a error after very reboot that sayes can't connect to the deployment share. with the option retry or cancel. If i retry the deployment goes on. I included a part of the BDD.log of the Machine. can someone please help me i have to deploy 50 Surface pro 3 tablet. Event 41017 sent: LTI initiating task sequence-requested reboot. LiteTouch 5-6-2015 13:22:46 0 (0x0000) Creating RunOnce registry key to run LiteTouch.wsf for the next reboot. LiteTouch 5-6-2015 13:22:46 0 (0x0000) Property BootPE is now = LiteTouch 5-6-2015 13:22:46 0 (0x0000) Microsoft Deployment Toolkit version: 6.2.5019.0 LiteTouch 5-6-2015 13:23:07 0 (0x0000) ZTIUtility!GetAllFixedDrives (Onwaar) LiteTouch 5-6-2015 13:23:07 0 (0x0000) New ZTIDisk : \\MOSMD1003\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LiteTouch 5-6-2015 13:23:07 0 (0x0000) New ZTIDisk : \\MOSMD1003\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LiteTouch 5-6-2015 13:23:07 0 (0x0000) New ZTIDiskPartition : \\MOSMD1003\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #2" \\MOSMD1003\root\cimv2:Win32_LogicalDisk.DeviceID="C:" LiteTouch 5-6-2015 13:23:07 0 (0x0000) New ZTIDisk : \\MOSMD1003\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LiteTouch 5-6-2015 13:23:07 0 (0x0000) ZTIUtility!GetAllFixedDrives = C: LiteTouch 5-6-2015 13:23:07 0 (0x0000) Found existing task sequence state information in C:\_SMSTaskSequence, will continue LiteTouch 5-6-2015 13:23:07 0 (0x0000) Not running within WinPE. LiteTouch 5-6-2015 13:23:07 0 (0x0000) DeploymentMethod = UNC LiteTouch 5-6-2015 13:23:07 0 (0x0000) Validating connection to \\WDS-01\DeploymentShare$ LiteTouch 5-6-2015 13:23:07 0 (0x0000) No physical adapters present, cannot deploy over wireless LiteTouch 5-6-2015 13:23:07 0 (0x0000) Unable to connect to the deployment share \\WDS-01\DeploymentShare$. DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection. LiteTouch 5-6-2015 13:23:08 0 (0x0000) ValidateDeployRootWithRecovery: Retry LiteTouch 5-6-2015 13:25:30 0 (0x0000) Validating connection to \\WDS-01\DeploymentShare$ LiteTouch 5-6-2015 13:25:30 0 (0x0000) Mapping server share: \\WDS-01\DeploymentShare$ LiteTouch 5-6-2015 13:25:30 0 (0x0000) Mapped Network UNC Path Z: = \\WDS-01\DeploymentShare$ LiteTouch 5-6-2015 13:25:32 0 (0x0000) Found Existing UNC Path Z: = \\WDS-01\DeploymentShare$ LiteTouch 5-6-2015 13:25:32 0 (0x0000) Successfully established connection using supplied credentials. LiteTouch 5-6-2015 13:25:32 0 (0x0000) DeployRoot = \\WDS-01\DeploymentShare$ LiteTouch 5-6-2015 13:25:32 0 (0x0000) Property DeployDrive is now = Z: LiteTouch 5-6-2015 13:25:32 0 (0x0000) DeployDrive = Z: LiteTouch 5-6-2015 13:25:32 0 (0x0000) Phase = STATERESTORE LiteTouch 5-6-2015 13:25:32 0 (0x0000)

Hello, The Deployment for my surface pro 3 with the Microsoft Dock Worked Fine (got about 20 Surface pro tablets in Production). But !! There is a firmware update. Now i got a error that the network adapter is not found. Lucky it gave me the option to Retry. Then it goes on. So this looks like a driver bug. Does anyone have the solution for this problem ? Greetings Ronald