locked
MDT Deployment stops due to missing variable RRS feed

  • Question

  • Hello everyone,

    we are using MDT for deployment of Win10/Server2016 at customer site. In one case, the deployment stops at the Windows Desktop without any further activity. Investigating BDD.log shows the last line

    Copying E:\Deploy\Control\\TS.XML to C:\MININT\Tools\x64

    Not running within WinPE.	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Property DeployRoot is now = E:\Deploy	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Property ResourceRoot is now = E:\Deploy	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Property DeploymentMethod is now = MEDIA	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    DeploymentMethod = MEDIA	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Property OEMDeploy is now = False	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Using OEM Deployment method (only valid for first step.)? 0	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Property OemDeployStarted is now = False	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    DeployRoot = E:\Deploy	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Property DeployDrive is now = E:	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    DeployDrive = E:	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Phase = STATERESTORE	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Using a local or mapped drive, no connection is required.	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Property DeployDrive is now = E:	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    DeployDrive = E:	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Using a local or mapped drive, no connection is required.	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    DeploymentType = 	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    ResourceRoot = E:\Deploy	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Property ResourceDrive is now = E:	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    ResourceDrive = E:	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Property _SMSTSPackageName is now = Parking System Installation	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Property Architecture is now = x64	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    SMS Task Sequencer found at E:\Deploy\Tools\x64, copying to C:\MININT\Tools\x64	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Tools\x64\CcmCore.dll to C:\MININT\Tools\x64\CcmCore.dll	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Tools\x64\CcmUtilLib.dll to C:\MININT\Tools\x64\CcmUtilLib.dll	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Tools\x64\Smsboot.exe to C:\MININT\Tools\x64\Smsboot.exe	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Tools\x64\SmsCore.dll to C:\MININT\Tools\x64\SmsCore.dll	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Tools\x64\TsCore.dll to C:\MININT\Tools\x64\TsCore.dll	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Tools\x64\TSEnv.exe to C:\MININT\Tools\x64\TSEnv.exe	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Tools\x64\TsManager.exe to C:\MININT\Tools\x64\TsManager.exe	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Tools\x64\TsmBootstrap.exe to C:\MININT\Tools\x64\TsmBootstrap.exe	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Tools\x64\TsMessaging.dll to C:\MININT\Tools\x64\TsMessaging.dll	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Tools\x64\TsProgressUI.exe to C:\MININT\Tools\x64\TsProgressUI.exe	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Tools\x64\TSResNlc.dll to C:\MININT\Tools\x64\TSResNlc.dll	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Tools\x64\msvcp120.dll to C:\MININT\Tools\x64\msvcp120.dll	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Tools\x64\msvcr120.dll to C:\MININT\Tools\x64\msvcr120.dll	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Tools\x64\CommonUtils.dll to C:\MININT\Tools\x64\CommonUtils.dll	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Tools\x64\ccmgencert.dll to C:\MININT\Tools\x64\ccmgencert.dll	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Tools\x64\00000409\tsres.dll to C:\MININT\Tools\x64\00000409\tsres.dll	LiteTouch	04.06.2019 17:12:51	0 (0x0000)
    Copying E:\Deploy\Control\\TS.XML to C:\MININT\Tools\x64	LiteTouch	04.06.2019 17:12:51	0 (0x0000)

    It seems that the variable for the specified task sequence is missing. Furthermore, the log shows that at the beginning, deployment starts with Litetouch but then immediately jumps to ZTIDiskpart and continues from there. In particular, it seems that no Gather step is performed at all:

    Property LogPath is now = X:\MININT\SMSOSD\OSDLOGS    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    Microsoft Deployment Toolkit version: 6.3.8330.1000    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    Property Debug is now = FALSE    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    No additional parameters . Run enhanced environment checks.    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    ZTIUtility!GetAllFixedDrives (False)    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDiskPartition : \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #1, Partition #0"    \\MININT-32IHP0H\root\cimv2:Win32_LogicalDisk.DeviceID="D:"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDisk : \\MININT-32IHP0H\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE1"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDiskPartition : \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"    \\MININT-32IHP0H\root\cimv2:Win32_LogicalDisk.DeviceID="C:"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDisk : \\MININT-32IHP0H\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDiskPartition : \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\MININT-32IHP0H\root\cimv2:Win32_LogicalDisk.DeviceID="E:"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDisk : \\MININT-32IHP0H\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDiskPartition : \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #2"    \\MININT-32IHP0H\root\cimv2:Win32_LogicalDisk.DeviceID="F:"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDisk : \\MININT-32IHP0H\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDiskPartition : \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #2, Partition #0"    \\MININT-32IHP0H\root\cimv2:Win32_LogicalDisk.DeviceID="G:"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDisk : \\MININT-32IHP0H\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE2"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    ZTIUtility!GetAllFixedDrives =  C: E: F:    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    Current Folder of Running script: X:\Deploy\Scripts\LiteTouch.wsfTrue    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    Property AutoLoadError is now = 0    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    Property AutoLoadConfigFile is now = na    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    ZTIUtility!GetAllFixedDrives (False)    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDiskPartition : \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #1, Partition #0"    \\MININT-32IHP0H\root\cimv2:Win32_LogicalDisk.DeviceID="D:"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDisk : \\MININT-32IHP0H\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE1"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDiskPartition : \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"    \\MININT-32IHP0H\root\cimv2:Win32_LogicalDisk.DeviceID="C:"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDisk : \\MININT-32IHP0H\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDiskPartition : \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\MININT-32IHP0H\root\cimv2:Win32_LogicalDisk.DeviceID="E:"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDisk : \\MININT-32IHP0H\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDiskPartition : \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #2"    \\MININT-32IHP0H\root\cimv2:Win32_LogicalDisk.DeviceID="F:"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDisk : \\MININT-32IHP0H\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"    LiteTouch    04.06.2019 16:47:41    0 (0x0000)
    New ZTIDiskPartition : \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #2, Partition #0"    \\MININT-32IHP0H\root\cimv2:Win32_LogicalDisk.DeviceID="G:"    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    New ZTIDisk : \\MININT-32IHP0H\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE2"    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    ZTIUtility!GetAllFixedDrives =  C: E: F:    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    No task sequence is in progress.    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    New ZTIDisk : \\MININT-32IHP0H\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE1"    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    Found Possible NonOS Disk: \\MININT-32IHP0H\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE1"    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    New ZTIDisk : \\MININT-32IHP0H\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    Found Possible OS TargetDisk: \\MININT-32IHP0H\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    GetPartitions: 3    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    Found Possible OS Target Partition: \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    New ZTIDiskPartition : \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"    \\MININT-32IHP0H\root\cimv2:Win32_LogicalDisk.DeviceID="C:"    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    Target Partition not big enough: \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    Found Possible OS Target Partition: \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    New ZTIDiskPartition : \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\MININT-32IHP0H\root\cimv2:Win32_LogicalDisk.DeviceID="E:"    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    Found Drive: E:    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    Found Possible OS Target Partition: \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #2"    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    New ZTIDiskPartition : \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #2"    \\MININT-32IHP0H\root\cimv2:Win32_LogicalDisk.DeviceID="F:"    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    Target Partition not big enough: \\MININT-32IHP0H\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #2"    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    New ZTIDisk : \\MININT-32IHP0H\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE2"    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    Found Possible NonOS Disk: \\MININT-32IHP0H\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE2"    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    Found FirstPossibleSystemDrive: E:    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    Property SMSTSLocalDataDrive is now = E:    LiteTouch    04.06.2019 16:47:42    0 (0x0000)
    Property LogPath is now = X:\MININT\SMSOSD\OSDLOGS    ZTIDiskpart    04.06.2019 15:48:23    0 (0x0000)

    As a workaround reported by our customer, it is possible to resume the installation by copying TS.xml to the correct folder and starting Litetouch.wsf manually.

    We assume this issue to be caused by relics of an older deployment still existing on disk, e.g., an old variables.dat file which is wrongly used for the current deployment. However, according to our customer, the disk is clean at the start of deployment.

    Does anyone have an idea what could be wrong here?

    Thanks in advance!

    PS I cannot link the full log as my account is not verified. I try to link it when possible.

    Tuesday, August 6, 2019 1:47 PM