Hi Guys,

I have prepared a test lab of MDT 2013 update2 with ADK 1511. My aim is to prepare a standalone media which will have standard win10 client upgrade task sequence and office 2016 applications.

I am using win10 1607 in TS to upgrade win 7. Selection profile is ready it contains TS, application and all required components. I created offline media and have cut in USB. I am running litetouch.vbs on win7 machine and upgrade from win7 to win10 is going smooth, no issues.

However post upgrade  - Application installation is not happening.

I found that this group had a condition to check regsitry key of upgrade status which was failing as upgrade was not creating that registry, so I removed that condition from TS and updates deployment share and prepared new media however still application is not installed post upgrade. please help

thanks!

Guys, will anyone suggest something. I have a script that checks the computers' serial number and model, to be used basically on placing a strict computer name assignment that will stop the loading process if no details were found.  This script was placed as an "application" for better manageability.  Now I used that scripts same DB (text files) from its current location and added another script (verify.exe) to be used solely to verify and stop the process if no details were found.

The script works although I placed it after the formatting and OS loading which takes time.  I want to place the verification script earlier (even before formatting). I used (both with and without cmd.exe /c ) "%DeployRoot%\Applications\AutoRename PC\verify.exe"  run command line on the task sequence, but kept on getting error (similar to path not found error).  It seems the "%deployroot% is still assigned to drive X at the time it was executed, whereas the script is on the deploymentshare\application folder.

The target is to check the PCs validity for OS loading on the shortest time possible and without destroying the current OS loaded on the said PC.

TIA!

Still fairly new to MDT but am learning. I am trying to add a Reg delete to the task sequence. The command line I have is:

reg.exe delete HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate /f

This does not work but if I enter it in the command prompt afterwards it works fine.

I have tried looking through the logs and searching for reg.exe but cannot find any trace of it. Everything else in my TS works fine but this. Do I have to specify C:\Windows\System32? I thought I had tried that but could try it again. I just didn't know if there was anything obvious I am missing.

Where can I look for my problem at?

Thanks,

Scott

When trying to roll out Windows 7 (anny version/edition) Or windows server 2012 R2(anny edition). Using MDT 2013 update 2 on windows server 2012 R2, I get the following errors. 

NOTE: These are taken from the DDB LOG.

<![LOG[FindFile: The file LTIBootstrap.vbs could not be found in any standard locations.]LOG]!><time="02:17:59.000+000" date="11-28-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument (5)]LOG]!><time="02:17:59.000+000" date="11-28-2016" component="LTIApply" context="" type="3" thread="" file="LTIApply">

When looking in the  '%DeploymentShare%\Scripts\' Folder There is no LTIBootstrap.vbs to be copied to the machine the os is deployed to. In fact no where on the server there is an LTIBootstrap.vbs (in the images neither).  

Im not sure if im looking in the correct location.

In the LTIApply.wsf The folling line about the bootmgr is listed:

If not oFSO.FileExists(sBootDrive & "\Bootmgr") then
oLogging.CreateEntry "Copying " & oEnvironment.Item("DeployRoot") & "\Boot\" & sArchitecture & "\bootmgr to " & sBootDrive & "\bootmgr", LogTypeInfo
oFSO.CopyFile oEnvironment.Item("DeployRoot") & "\Boot\" & sArchitecture & "\bootmgr", sBootDrive & "\", true

Ive tried work arounds like change the Line to the following:

not oFSO.FolderExists(sBootDrive & "\Boot")
oFSO.CreateFolder(sBootDrive & "\
End if

To no avail however.

MDT 2012 Server is up and running. I mistakenly deleted a Task Sequence step called "Install Application" that I thought was not needed (I know I should have disabled it and tested).

I have a problem now, when I went to image a computer I did not get application list (This used to work before I deleted the above TS step) with items to check and uncheck for installation.  "Install Application" TS was readded but now when I try to image I get this error:

"The task sequence has been suspended. LiteTouch is trying to install applications. This cannot be performed in Windows PE."

I've tried moving it to different positions on the list (Higher and lower) to no avail, I always get the same error. Please advise.

-Thanks in advance!

I have just upgraded MDT 2013 to Update 2 (skipped Update 1) and tested one of many self contained Media deployment ISO images we have. These use a specific Task Sequence ID which is hidden from the Wizard using "SkipTaskSequence=YES" and"TaskSequenceID=..." in CustomSettings.ini.

Unlike the previous MDT2013 (non-updated) version, the install now fails to proceed past the "Wizard Ready" stage with the error 'Invalid DeploymentType of "" '.

The Deployment Type (NEWCOMPUTER) is not set in CustomSettings.ini (never has been), but the logs clearly show it is discovered correctly set (to NEWCOMPUTER) by ZTIGather and LiteTouch; but the Wizard log then reports it as equal to "" at the very end of the Wizard run. Same thing happens if I actually add "DeploymentType=NEWCOMPUTER" to customsettings.ini.

I reinstated the TaskSequence Wizard page based on a previous posting, selected my Task Sequence in the Wizard at install and voila it worked!

So what has changed? Why can I no longer skip the TS Wizard page? What is resetting DeploymentType from NEWCOMPUTER to blank? Where should I be looking? Why does an update make things worse?

Logs available, any and all help appreciated!

STEVE

Hi All,

First of all, some history behind my issue:

We had fully working MDT 8443 release, with Windows ADK for Windows 10, version 1511.

We then decided to roll out the anniversary update of Windows 10 v1607, and due to this, we replaced ADK 1511 with 1607.

We have added new Windows 10 OS v1607, along side with a newly created package which includes the latest CU for this Windows 10 OS version (kb3200970).

When we try to update the deployment share or completely regenerate the image, it fails every time with the following error (attached below) after injecting a package with the latest CU for Windows 10. I also tried to reboot this server several times to see if that fixes the problem, however no luck. Same issue after the reboot.

As a part of this troubleshooting, I've also disabled Microsoft Data Access Components (MDAC/ADO) support under Features for x86/x64 for this deployment share.
----------------------------------------------------------------------------------------------------------------------------

Error: 1726

The remote procedure call failed.
An error occurred closing a servicing component in the image.
Wait a few minutes and try running the command again.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Exit code = 1726

DISM /Add-Package failed, rc = 1726.
Injected package Package_for_RollupFix neutral amd64 14393.447.1.5
ERROR: The process cannot access the file because it is being used by another process.
Exit code = 1

REG LOAD failed, rc = 1.

System.Management.Automation.CmdletInvocationException: Unable to open the specified WIM file. ---> System.Exception: Unable to open the specified WIM file. ---> System.ComponentModel.Win32Exception: The process cannot access the file because it is being used by another process
   --- End of inner exception stack trace ---
   at Microsoft.BDD.Core.BDDWimFile..ctor(String wimPath, Boolean forUpdate)
   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName)
   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at Microsoft.BDD.Wizards.UpdateProgress.WizardProcessing()
   at Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()

----------------------------------------------------------------------------------------------------------------------------

When then we removed the update package from the MDT, and image generated just fine so must be something related to this package.

I tried removing the package and adding it again but no luck. While it's on 'Injecting package Package_for_RollupFix neutral amd64 14393.447.1.5, I will receive a window saying 'Dism Host Servicing Process has stopped working' with the following error details and 'Close the program' button.

----------------------------------------------------------------------------------------------------------------------------

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    dismhost.exe
  Application Version:    10.0.14393.0
  Application Timestamp:    57899b20
  Fault Module Name:    cmifw.dll
  Fault Module Version:    10.0.14393.0
  Fault Module Timestamp:    57899838
  Exception Code:    c0000005
  Exception Offset:    0000000000006caa
  OS Version:    6.3.9600.2.0.0.272.7
  Locale ID:    2057
  Additional Information 1:    b613
  Additional Information 2:    b6130c53ab7c1f5795a469873fb1d675
  Additional Information 3:    5fe4
  Additional Information 4:    5fe4b80a1967253d1918c64f42947e5c

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=280262

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

----------------------------------------------------------------------------------------------------------------------------

Anyone, any ideas on this issue?

Your help would be greatly appreciated!

Thanks

Hi. I've been trying to solve this issue for days now.

I was trying to deploy Windows 7 Professional using MDT 2012U1 on HP Pro 3400/3500 workstations. I've generated x64 Lite Touch WIM with network and chipset drivers integrated in it.

When Lite Touch image is loaded, target computer reboots shortly after default splash screen. By starting Lite Touch with command line (F8 button) and running

cscript.exe x:\\deploy\\scripts\\litetouch.wsf

I've came across this error: ZTIUtility!GetAllFixedDrives (False).

I've also tried replacing mentioned function in ZTIUtility.vbs using function version from MDT 2010, but with little success (error was slightly different but drive related as well).

So any help is appreciated.

PS. Network is fine, NIC gets it's IP; HDD is running in AHCI mode.

Hi All,

Does anyone know how to create in-place upgrade task sequence to inject CU package or run Windows Update (WSUS) afterwards the OS deployment is completed? I'm running 8443 version.

I'm purely relating to TS setup, and not how to add a package or configure WSUS with MDT.

The default In-Place Upgrade TS will only run the upgrade, doesn't include any option to configure what packages to add, and skips WSUS even though it's specified within the TS by default which seems odd.

Thanks

At the end of my deployment I am getting

FAILURE: False: Verify %OSSKU% is defined.

I am deploying Windows 10 Enterprise LTSB. 

What am I doing wrong here?

Sometimes with certain laptop models we have problems with automatic MDT Bitlocker provisioning during OSD. I'm not sure what causes this. When you manually enable Bitlocker from OS afterwards it works fine.

FAILURE ( 6739 ): False: Check to see if TPM is enabled

Hi

When am trying to deploy any image from MDT 2012, am geting below error.

can some help me on this please...

Unhandled error retuned by LTI Apply; Invalid procedure call or argument (5)

Thank's in advance..

Hello MDT Pro's:

Can anyone help me with the error below?

I followed the steps by Johan Arwidmark for updating my existing MDT 2013 to Update1 (8298) without any issues.

http://deploymentresearch.com/Research/Post/504/A-Geeks-Guide-for-upgrading-MDT-2013-to-MDT-2013-Update-1

1. Before the upgrade, my TS to deploy custom Windows 7 Std SP1 x64 is working fine. After the upgrade, I recreated the TS and modified it to be like my old TS.

2. Tried deploying it to a VM (which I've usually done successfully in my old MDT 2013)

3. Error after "Applying Image" task.

Please let me know if you need other logs.

Thanks in Advance,

Alfred

Links to Logs from the VM placed after this image.

BDD.log

LTIApply.log

Hello,

it seems that I don't understand it fully - MDT and WDS.

I'm running MDT 2013 update 2 and a WDS server role on Windows Server 2012 R2 and want to capture Windows 10 physical pc's and deploy these images to other computers in the netwerk.

Task sequencing and other stuff is not important for me at the moment.

I tested MDT in virtual envirnment (without wds installed) and it worked. I pxe booted my pc and came into the mdt menu, coould capture my physcal pc and made an image of the machine.

Now I installed WDS also and I can not get into the mdt manu any more. I made wds ready to deploy an image of Windows 10 and after pxe booting a pc it starts immediately with installing this Windows 10. 

I want to be able to choose that I want to capture with MDT or deploy with WDS. Is it possible or do I see it wrong (do I use it the wrong way). I found a lot of manuals on the internet, but none of them answer my questions. Also I tested it (not in vmware but in real life - the MDT without wds) and my pxe-boot did find the pxe "server" but didn't started the system and gave a pxe-time out. I changed the option 067 on the Windows Server 2012 R2 DC with DHCP (settings) to so many thing that I don't know what is correct anymore. Now it sais: boot\x64\pxeboot.n12 (and it boots into wds immediately). I want the pc's to pxe-boot in MDT to capture.

Thanks in advance.

Hello

I have some Windows 7 Task Sequences which work fine.

I have made a windows 10 TS and this works but im finding when the machine is built it does not restart at the end of the Task Sequence unlike the Windows 7 one does.

I have placed a reboot at the end of the task sequence but still it does not reboot. Instead im left with two setup Google chrome windows. i see at this point that the folder Minint still exists at the root of the C drive. 

The last 6 lines of the bdd.log show as

Command completed, return code = -2147021886 

Property LTIDirty is now = false

if there is a drive letter defined, make sure we clear it now so we can force recalculation

Property OSDTargetDriveCache is now = DIRTY

LTI initialing task sequence-requested reboot

Event 41017 sent: LTI initiating task sequence-requested reboot

If i then close the googlechrome windows and restart all is well, i see upon next login that the Minint Folder is then deleted.

Any ideas ?

Could i be correct in saying it can not re-start as the google chrome windows are active?

The Google chrome application is the same one (application) as i use on my windows 7 build which does not have this issue.

Thanks

Ok so here's the issue I am getting.

After my image is installed using LiteTouch (booted from a USB) the final step where it is trying to apply unattend.xml with DISM, I get the following error:

ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument (5)

The system will then reboot, and it cannot find the file "LTIBootstrap.vbs" in standard locations.

Here is a portion of the code from BDD.LOG

<![LOG[ZTI Heartbeat: command has been running for 10 minutes (process ID 1300)]LOG]!><time="10:26:06.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > The operation completed successfully.]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Return code from command = 0]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Property LTIDirtyOS is now = TRUE]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[The image \\LIB-AU16640\Win10Deploy$\Operating Systems\Windows 10 Enterprise 2016 LTSB x64\Sources\install.wim was applied successfully.]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Find the boot drive (if any) [True] [10.0.14393.0] [False]]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[New ZTIDiskPartition : \\MININT-7AH5HU7\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"    \\MININT-7AH5HU7\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[New ZTIDisk : \\MININT-7AH5HU7\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Found bootable drive (No Boot File Test) [ V: ]: \\MININT-7AH5HU7\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Ready to Prepare boot partition: V:]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Property UILanguage is now = en-US]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[About to run command: cscript.exe //nologo "\\LIB-AU16640\Win10Deploy$\Scripts\ztiRunCommandHidden.wsf" ""\\LIB-AU16640\Win10Deploy$\Tools\X64\BCDBoot.exe" F:\windows /l en-US  /s V: /f UEFI"]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Microsoft Deployment Toolkit version: 6.3.8298.1000]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden"><![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden"><![LOG[About to run command: \\LIB-AU16640\Win10Deploy$\Tools\X64\BCDBoot.exe F:\windows /l en-US  /s V: /f UEFI]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden"><![LOG[Command has been started (process ID 600)]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden"><![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 600)]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden"><![LOG[  Console > Boot files successfully created.]LOG]!><time="10:26:09.000+000" date="12-01-2016" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden"><![LOG[Return code from command = 0]LOG]!><time="10:26:09.000+000" date="12-01-2016" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden"><![LOG[Command has returned: 0]LOG]!><time="10:26:09.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Run Command: X:\windows\SYSTEM32\bcdedit.exe /timeout 0]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[BCD> The operation completed successfully.]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Created scratch folder.]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Copy File: F:\MININT\unattend.xml to F:\Windows\Panther\Unattend.xml]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Copied unattend.xml to F:\Windows\Panther for image apply.]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[About to run command: dism.exe /Image:F:\ /Apply-Unattend:F:\Windows\Panther\Unattend.xml /ScratchDir:F:\MININT\Scratch]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Command has been started (process ID 1524)]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Deployment Image Servicing and Management tool]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Version: 10.0.14393.0]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Image Version: 10.0.14393.0]LOG]!><time="10:26:14.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > The operation completed successfully.]LOG]!><time="10:26:41.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Return code from command = 0]LOG]!><time="10:26:41.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[FindFile: The file LTIBootstrap.vbs could not be found in any standard locations.]LOG]!><time="10:26:41.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument (5)]LOG]!><time="10:26:41.000+000" date="12-01-2016" component="LTIApply" context="" type="3" thread="" file="LTIApply"><![LOG[Command completed, return code = -2147467259]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LiteTouch" context="" type="3" thread="" file="LiteTouch"><![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Property RetVal is now = -2147467259]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Unable to copy log to the network as no SLShare value was specified.]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[CleanStartItems Complete]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[TSCore.dll not found, not unregistering.]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[About to run command: wscript.exe "X:\Deploy\Scripts\LTICleanup.wsf"]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Microsoft Deployment Toolkit version: 6.3.8298.1000]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Removing AutoAdminLogon registry entries]LOG]!><time="10:26:43.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Re-enabling UAC for built-in Administrator account]LOG]!><time="10:26:43.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[VSSMaxSize not specified using 5% of volume.]LOG]!><time="10:26:43.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Logs contained 2 errors and 0 warnings.]LOG]!><time="10:26:43.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[No Windows PE image to delete.]LOG]!><time="10:26:43.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Checking mapped network drive.]LOG]!><time="10:26:43.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[testing drive Z: mapped to \\LIB-AU16640\Win10Deploy$]LOG]!><time="10:26:43.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Disconnecting drive Z: mapped to \\LIB-AU16640\Win10Deploy$]LOG]!><time="10:26:43.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Cleaning up F:\MININT directory.]LOG]!><time="10:26:44.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Cleaning up TOOLS, SCRIPTS, and PACKAGES directories.]LOG]!><time="10:26:44.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">

<![LOG[ZTI Heartbeat: command has been running for 10 minutes (process ID 1300)]LOG]!><time="10:26:06.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > The operation completed successfully.]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Return code from command = 0]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Property LTIDirtyOS is now = TRUE]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[The image \\COMPUTERNAME\Win10Deploy$\Operating Systems\Windows 10 Enterprise 2016 LTSB x64\Sources\install.wim was applied successfully.]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Find the boot drive (if any) [True] [10.0.14393.0] [False]]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[New ZTIDiskPartition : \\MININT-7AH5HU7\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"    \\MININT-7AH5HU7\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[New ZTIDisk : \\MININT-7AH5HU7\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Found bootable drive (No Boot File Test) [ V: ]: \\MININT-7AH5HU7\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Ready to Prepare boot partition: V:]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Property UILanguage is now = en-US]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[About to run command: cscript.exe //nologo "\\COMPUTERNAME\Win10Deploy$\Scripts\ztiRunCommandHidden.wsf" ""\\LIB-AU16640\Win10Deploy$\Tools\X64\BCDBoot.exe" F:\windows /l en-US  /s V: /f UEFI"]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Command has returned: 0]LOG]!><time="10:26:09.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Run Command: X:\windows\SYSTEM32\bcdedit.exe /timeout 0]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[BCD> The operation completed successfully.]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Created scratch folder.]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Copy File: F:\MININT\unattend.xml to F:\Windows\Panther\Unattend.xml]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Copied unattend.xml to F:\Windows\Panther for image apply.]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[About to run command: dism.exe /Image:F:\ /Apply-Unattend:F:\Windows\Panther\Unattend.xml /ScratchDir:F:\MININT\Scratch]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Command has been started (process ID 1524)]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Deployment Image Servicing and Management tool]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Version: 10.0.14393.0]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Image Version: 10.0.14393.0]LOG]!><time="10:26:14.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > The operation completed successfully.]LOG]!><time="10:26:41.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Return code from command = 0]LOG]!><time="10:26:41.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[FindFile: The file LTIBootstrap.vbs could not be found in any standard locations.]LOG]!><time="10:26:41.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument (5)]LOG]!><time="10:26:41.000+000" date="12-01-2016" component="LTIApply" context="" type="3" thread="" file="LTIApply">

I've noticed in these logs for whatever reason its looking for "F:" locations. My drive is C:

Any suggestions??