MDT 2013 - Deleted Litetouch.vbs

Alright, well... stupid mistake on my part. I was trying to clear litetouch.vbs from the recent files on a Win10 technical preview, and without fully thinking about it, just selected it and hit delete. At the same point, the realization that it was a network
location and I was logged into the client with domain admin privileges hit me. I've searched recycle bin on both the client and the server (not there). I've checked for "previous versions" of the folder, but none available, and unfortunately our
deployment server is not part of the backup schedule. 
What can I do to recover or recreate the litetouch.vbs? The .wsf is still present. 
I appreciate any suggestions. 

' // Copyright (c) Microsoft Corporation. All rights reserved.
' // Microsoft Deployment Toolkit Solution Accelerator
' // File: Litetouch.vbs
' // Version: 6.0.2149.0
' // Purpose: Start the lite touch deployment process
' // Usage: cscript LiteTouch.vbs [/debug:true]
'// Global constant and variable declarations
Option Explicit
Dim oShell
Dim oFSO
Dim iRetVal
Dim sCmd
Dim sScriptDir
Dim sArg
Dim sArgString
Dim sArchitecture
Dim oDrive
'// Initialization
Set oShell = CreateObject("WScript.Shell")
Set oFSO = CreateObject("Scripting.FileSystemObject")
sScriptDir = oFSO.GetParentFolderName(WScript.ScriptFullName)
For each sArg in WScript.Arguments
sArgString = sArgString & sArg & " "
Next
'Change the Architecture type from amd64 to X64 for consistency
sArchitecture = oShell.Environment("SYSTEM").Item("Processor_Architecture")
if lcase(sArchitecture) = "amd64" then
sArchitecture = "x64"
end if
' Clean up any existing C:\MININT directory
sArgString = " /CleanStart " & sArgString
oShell.Environment("PROCESS")("SEE_MASK_NOZONECHECKS") = 1
' Clean up any remnants of a previous task sequence
On Error Resume Next
iRetVal = oShell.Run("reg.exe delete HKCR\Microsoft.SMS.TSEnvironment /f", 0, true)
iRetVal = oShell.Run("reg.exe delete HKCR\Microsoft.SMS.TSEnvironment.1 /f", 0, true)
iRetVal = oShell.Run("reg.exe delete HKCR\Microsoft.SMS.TSProgressUI /f", 0, true)
On Error Goto 0
'// Check to see if the prereq's have been satisfied
sCmd = "cscript.exe """ & sScriptDir & "\ZTIPrereq.vbs"""
iRetVal = oShell.Run(sCmd, 0, true)
If iRetVal <> 0 then
oShell.Popup "This computer does not meet the prerequisites for deploying a new operating system. (" & CStr(iRetVal) & ")", 0, "Prerequisite Error", 16
WScript.Quit iRetVal
End if
'// Launch LiteTouch.wsf to do the heavy lifting
sCmd = """" & sScriptDir & "\..\tools\" & sArchitecture & "\bddrun.exe"" wscript.exe """ & sScriptDir & "\LiteTouch.wsf"" " & sArgString
iRetVal = oShell.Run(sCmd, 1, true)
' All done
WScript.Quit iRetVal
That's the entire contents of the litetouch.vbs on my MDT server. Just remake it. Additionally, make another share and just copy the script over?

Similar Messages

  • MDT 2013 - Litetouch.wsf continues to run at login

    Hi all! I recently imaged a server with MDT 2013 and after it booted into Windows one of the applications I configured to install crashed and we ended up with an incomplete deployment. In this case this was fine and we moved on, but now every time a user
    logs in something is attempting to launch the Litetouch.wsf script. I ran LTICleanup manually and removed the MININT folder, but I continue to get a pop-up at login that Litetouch cannot be found.
    I have tried every registry key I am aware of HKCU and HKLM Run and Runonce keys and also checked the startup folders for every user. What is calling Litetouch? How can I stop this from happening? Thanks!

    Hi Matt McNabb,
    I guess you must create some script execute Task Sequence in your deploy task and it not complete because the deploy error occur, you can delete this script then try again,
    this forum is mainly for WDS related issue it’s not the best place to talk about the MDT issue, there have a specific MDT support forum you can post in MDT support forum and get the MDT expert further support.
    MDT support 
    forum:
    https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
    Thanks for your understanding and support.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • MDT 2013 - Litetouch deployment failed, Return Code = -2147467259 0x80004005

    I'm attempting to deploy an image that I have recently captured with MDT.  I was able to capture the image without any problems and after capturing, it booted up properly.  But now when I go to deploy the image using a Standard Task Sequence it
    errors out.  It does boot into WinPE and gets to the installing operating system portion then spits out the following 8 errors:
    (5624):2: Run ImageX: /apply "\\PDC31089\DeploymentShare$\Operating Systems\Win7_BUP_1-31-14\Win7_BUP_1-31-14.wim" 1 C:
    Litetouch deployment failed, Return Code = -2147467259 0x80004005
    Failed to run the action: Install Operating System.
    Unknown error (Error: 000015F8; Source: Unknown)
    The execution of the group (Install) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)
    Failed to run the last action: Install Operating System. Execution of task sequence failed.
    Unknown error (Error: 000015F8; Source: Unknown)
    Task Sequence Engine failed! Code: enExecutionFail
    Task sequence execution failed with error code 80004005
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005After I receive the error messages if I attempt to restart the computer and allow it to boot up it just comes up with:"An operating system wasn't found. Try disconnecting any drives that don't contain an operating system"
    I have tried the following to resolve this issue:
    Create a new deployment share with only network drivers added and the one .WIM that was captured with MDT as well as one Task sequence.
    Update to MDT 2013
    Update Deployment share and completely regenerate Boot images
    Tried starting deployment from within Windows by mapping the drive and executing litetouch.vbs
    Also tried starting deployment using USB boot disk
    I'm running out of ideas and seem to keep getting the same 8 error messages.  It's very aggravating and am hoping that someone can point me in the right direction.
    I've included some log files on Skydrive at:  https://skydrive.live.com/redir?resid=6375A8F9E8089918%21105

    I came across this post recently. I am having the same string of errors suddenly when I try to deploy any image from my MDT 2013 server now. Previous images now fail to install soon after the Inject Drivers task sequence at the Install Operating System sequence.
    Each time I try to deploy an image(have tried several each with different task sequences), I get the same 7 errors.
    The errors produced are:
    Litetouch deployment failed, Return Code = -2147467259 0x80004005
    Failed to run the action: Install Operating System.
    Incorrect Function (Error: 00000001; Source: Windows)
    The execution of the group (Install) has failed and the execution has been
    aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)
    Failed to run the last action: Install Operating System. Execution of task
    sequence failed.
    Incorrect Function
    (Error: 00000001;
    Source: Windows)
    Task Sequence Engine failed! Code: enExecutionFail
    Task sequence execution failed with error code 80004005
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
    My HD size is 146GB with about 71GB being free.
    The BDD.log file is too large to post here apparently. Here are the
    last bits of it.
    <![LOG[Assume this disk is the destination Disk, and verify.]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart"
    context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[TargetPartitionIdentifier is set, find disk: SELECT * FROM Win32_LogicalDisk WHERE Size = '499577253888' and VolumeName = 'OSDisk' and VolumeSerialNumber = 'CA3BC8A9']LOG]!><time="11:36:58.000+000" date="09-26-2014"
    component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Search for Drive: TargetPartitionIdentifier  SELECT * FROM Win32_LogicalDisk WHERE Size = '499577253888' and VolumeName = 'OSDisk' and VolumeSerialNumber = 'CA3BC8A9']LOG]!><time="11:36:58.000+000" date="09-26-2014"
    component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Found Drive: C:]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Property OSDisk is now = C:]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Target Drive Letter Found: C:]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Found OS Drive: C   0]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[New ZTIDiskPartition : \\MININT-I3DUVLI\root\cimv2:Win32_LogicalDisk.DeviceID="C:"    \\MININT-I3DUVLI\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="11:36:58.000+000"
    date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Check Disk [0] <> [0] OK to skip.]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[####### NOTE:  If this is one of the  last lines in your BDD.log file, check C: for the most up to date bdd.log!!!]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart"
    context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[ZTIDiskpart processing completed successfully.]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Event 41001 sent: ZTIDiskpart processing completed successfully.]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread=""
    file="ZTIDiskpart">

  • Error when deploying LiteTouch image using MDT 2013 Media Flashdrive

    Please help! I have created a media flash drive (drive capacity: 64Gb) to deploy LiteTouch x86 and x64 images (Win7 and Win8, 8.1) to PCs but getting error for the 3rd time. I am using the following tools in my environment: i am using MDT 2013 on a Windows
    2k8 WDS server. PXE boot works fine deploying images but i keep getting this error after creating the Media flash drive). I first got the same failure with 14 errors but recreated the media on the WorkBench using a different selection profile but now i am
    getting this error: (by the way where is the BDD.LOG?)
    "Deployment Summary
    During the deployment process, 8 errors and 0 warnings were reported.
    Details...
    Failure ( 5456): Unable to determine destination disk, partition, and/or drive. See BDD.LOG for more information.
    Litetouch deployment failed, return code = -2147467259 0x80004005
    Failed to run the action: inject drivers.
    Unknown error (error: 00001550; source: unknown)
    The execution of the group (preinstall) has failed and the execution has been aborted. An acton failed. 
    Operation aborted (error: 80004004; xource: windows)
    Task sequence engine failed! code:enExecutionFail
    Task sequence execution failed with error code 80004005
    Error Task Sequence Manager failed to execute task sequence. code 0x80004005

    I am planning to build a WDS with Win2k12 and MDT2013 and perhaps will be lucky to create a successful media. I created one with my WDS Win2k8 it works on a HP laptop but failed on other machines like Dell...
    Did you get driver injection in configuration WDS and MDT?
    Considering if the incompatible drivers cause your issue.
    If you can post back the MDT log during the deployment on DELL computers, it would be helpful for us to determine your issue.
    Kate Li
    TechNet Community Support

  • MDT Wizard very slow to start when launching Litetouch.vbs

    Hi,
    For a few months, I have an issue when launching Litetouch.vbs, the Wizard initialisation il very slow. Normaly it takes 20 to 30 seconds to launch, now it takes about 4 minutes. The wizard hang 3 times for 1.5 minute. The problem is present on
    many computers here and even on a brand new installed computer.
    Something strange, when the Wizard have been launched a first time, then closed. The next time I launch Litetouch.vbs, I is fast (20 to 30 seconds).
    When I check the LOG : C:\MININT\SMSOSD\OSDLOGS\BDD.log, the lines that seems to hang are :
    <![LOG[Property definition is now = BDD_Welcome_ENU.xml]LOG]!>
    <![LOG[Property definition is now = WelcomeWiz_Initialize.xml]LOG]!>
    <![LOG[Property definition is now = DeployWiz_Definition_ENU.xml]LOG]!>
    Does anyone have an idea what can be the problem ?
    Thanks!
    Dominic

    The lines that are running slow above are when MDT is trying to write to the variables.dat file. There is nothing special about this operation, it's just reading/writing to a text file.
    I still think there is something else on this machine that is causing the litetouch.wsf scripts to run slowly. Perhaps you have some anti-virus programs causing problems.
    Best way to isolate the problem is to load a clean version of windows on a machine (without any corporate apps), and try running MDT litetouch again.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • MDT 2013: bootstrap.ini not applying username and password for share access

    I customized my bootstrap.ini file to skip the welcome screen, set keyboard locale, and enter a service account username and password for share access.  The welcome screen skip and keyboard locale work beautifully but it's not applying the share username/password/domain
    at all.  
    bootstrap.ini: 
    [Settings]
    Priority=Default
    [Default]
    DeployRoot=\\mydeploymentserver\DeploymentShare$
    UserID=myuserid
    UserDomain=mydomain.com
    UserPassword=mypassword
    KeyboardLocale=en-US
    SkipBDDWelcome=YES
    I verified that the unattend.xml file on the MININT volume during deployment had all of this information populated correctly:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
    <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
    <ImageInstall>
    <OSImage>
    <WillShowUI>OnError</WillShowUI>
    <InstallTo>
    <DiskID>0</DiskID>
    <PartitionID>2</PartitionID>
    </InstallTo>
    <InstallFrom>
    <Path>\\mydeploymentserver\deploymentshare$\Operating Systems\Windows 7 x64 with District Software - 06222014\Windows 7 x64 with District Software - 06222014.wim</Path>
    <MetaData>
    <Key>/IMAGE/INDEX</Key>
    <Value>1</Value>
    </MetaData>
    </InstallFrom>
    </OSImage>
    </ImageInstall>
    <Display>
    <ColorDepth>16</ColorDepth>
    <HorizontalResolution>1024</HorizontalResolution>
    <RefreshRate>60</RefreshRate>
    <VerticalResolution>768</VerticalResolution>
    </Display>
    <ComplianceCheck>
    <DisplayReport>OnError</DisplayReport>
    </ComplianceCheck>
    <UserData>
    <AcceptEula>true</AcceptEula>
    </UserData>
    </component>
    <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <SetupUILanguage>
    <UILanguage>en-US</UILanguage>
    </SetupUILanguage>
    <InputLocale>0409:00000409</InputLocale>
    <SystemLocale>en-US</SystemLocale>
    <UILanguage>en-US</UILanguage>
    <UserLocale>en-US</UserLocale>
    </component>
    </settings>
    <settings pass="generalize">
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <DoNotCleanTaskBar>true</DoNotCleanTaskBar>
    </component>
    </settings>
    <settings pass="specialize">
    <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
    <Identification>
    <Credentials>
    <Username>myusername</Username>
    <Domain>mydomain.com</Domain>
    <Password>mypassword</Password>
    </Credentials>
    <JoinDomain>mydomain.com</JoinDomain>
    </Identification>
    </component>
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
    <ComputerName>eos-vm-02</ComputerName>
    <RegisteredOrganization>Regional School District 19</RegisteredOrganization>
    <RegisteredOwner>Information Technology</RegisteredOwner>
    <DoNotCleanTaskBar>true</DoNotCleanTaskBar>
    <TimeZone>Eastern Standard Time</TimeZone>
    </component>
    <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <Home_Page>http://www.eosmith.org</Home_Page>
    <DisableWelcomePage>true</DisableWelcomePage>
    <DisableFirstRunWizard>false</DisableFirstRunWizard>
    </component>
    <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <RunSynchronous>
    <RunSynchronousCommand wcm:action="add">
    <Description>EnableAdmin</Description>
    <Order>1</Order>
    <Path>cmd /c net user Administrator /active:yes</Path>
    </RunSynchronousCommand>
    <RunSynchronousCommand wcm:action="add">
    <Description>UnfilterAdministratorToken</Description>
    <Order>2</Order>
    <Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path>
    </RunSynchronousCommand>
    <RunSynchronousCommand wcm:action="add">
    <Description>disable user account page</Description>
    <Order>3</Order>
    <Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE /v UnattendCreatedUser /t REG_DWORD /d 1 /f</Path>
    </RunSynchronousCommand>
    </RunSynchronous>
    </component>
    <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <InputLocale>en-US</InputLocale>
    <SystemLocale>en-US</SystemLocale>
    <UILanguage>en-US</UILanguage>
    <UserLocale>en-US</UserLocale>
    </component>
    <component name="Microsoft-Windows-TapiSetup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <TapiConfigured>0</TapiConfigured>
    <TapiUnattendLocation>
    <AreaCode>""</AreaCode>
    <CountryOrRegion>1</CountryOrRegion>
    <LongDistanceAccess>9</LongDistanceAccess>
    <OutsideAccess>9</OutsideAccess>
    <PulseOrToneDialing>1</PulseOrToneDialing>
    <DisableCallWaiting>""</DisableCallWaiting>
    <InternationalCarrierCode>""</InternationalCarrierCode>
    <LongDistanceCarrierCode>""</LongDistanceCarrierCode>
    <Name>Default</Name>
    </TapiUnattendLocation>
    </component>
    <component name="Microsoft-Windows-SystemRestore-Main" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <DisableSR>1</DisableSR>
    </component>
    </settings>
    <settings pass="oobeSystem">
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
    <UserAccounts>
    <AdministratorPassword>
    <Value>administratorpassword</Value>
    <PlainText>true</PlainText>
    </AdministratorPassword>
    </UserAccounts>
    <AutoLogon>
    <Enabled>true</Enabled>
    <Username>Administrator</Username>
    <Domain>.</Domain>
    <Password>
    <Value>administratorpassword</Value>
    <PlainText>true</PlainText>
    </Password>
    <LogonCount>999</LogonCount>
    </AutoLogon>
    <Display>
    <ColorDepth>32</ColorDepth>
    <HorizontalResolution>1024</HorizontalResolution>
    <RefreshRate>60</RefreshRate>
    <VerticalResolution>768</VerticalResolution>
    </Display>
    <FirstLogonCommands>
    <SynchronousCommand wcm:action="add">
    <CommandLine>wscript.exe %SystemDrive%\LTIBootstrap.vbs</CommandLine>
    <Description>Lite Touch new OS</Description>
    <Order>1</Order>
    </SynchronousCommand>
    </FirstLogonCommands>
    <OOBE>
    <HideEULAPage>true</HideEULAPage>
    <NetworkLocation>Work</NetworkLocation>
    <ProtectYourPC>1</ProtectYourPC>
    </OOBE>
    <RegisteredOrganization>Regional School District 19</RegisteredOrganization>
    <RegisteredOwner>Information Technology</RegisteredOwner>
    <TimeZone>Eastern Standard Time</TimeZone>
    </component>
    <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <InputLocale>en-US</InputLocale>
    <SystemLocale>en-US</SystemLocale>
    <UILanguage>en-US</UILanguage>
    <UserLocale>en-US</UserLocale>
    </component>
    </settings>
    <settings pass="offlineServicing">
    <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <DriverPaths>
    <PathAndCredentials wcm:keyValue="1" wcm:action="add">
    <Path>\Drivers</Path>
    </PathAndCredentials>
    </DriverPaths>
    </component>
    </settings>
    </unattend>
    ... and the bdd.log file appeared not to read the username and password at all:
    <![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ZTIUtility!GetAllFixedDrives = C: D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property LogPath is now = D:\MININT\SMSOSD\OSDLOGS]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property Debug is now = FALSE]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Cleaned up a dirty deployment.]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ZTIUtility!GetAllFixedDrives = C: D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[No task sequence is in progress.]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Possible OS TargetDisk: \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[GetPartitions: 2]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Possible OS Target Partition: \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Target Partition not big enough: \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Possible OS Target Partition: \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Drive: D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found FirstPossibleSystemDrive: D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property SMSTSLocalDataDrive is now = D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Unable to connect to BCDStore.]LOG]!><time="05:03:43.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Not running within WinPE or WinRE.]LOG]!><time="05:03:43.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property DeploymentMethod is now = UNC]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeploymentMethod = UNC]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property DeployRoot is now = X:\Deploy]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Using a local or mapped drive, no connection is required.]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeployRoot = X:\Deploy]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property DeployDrive is now = X:]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeployDrive = X:]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property PHASE is now = PREINSTALL]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property DeploymentType is now = NEWCOMPUTER]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Phase = PREINSTALL]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[About to run command: wscript.exe "X:\Deploy\Scripts\ZTIGather.wsf" /inifile:Bootstrap.ini]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property inifile is now = Bootstrap.ini]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[------------------------- Object Initialization -------------------------]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[------------------------- Initialization -------------------------]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Synchronizing the environments.]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property DeployRoot is now = X:\Deploy]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property DeployDrive is now = X:]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Finished synchronizing the environments.]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Getting OS info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property OSCurrentVersion is now = 6.3.9600]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property OSCurrentBuild is now = 9600]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property OSVersion is now = WinPE]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property IsServerOS is now = False]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property IsServerCoreOS is now = False]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Finished getting OS info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Getting HAL information]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property definition is now = BDD_Welcome_ENU.xml]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property HALName is now = acpiapic]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Finished getting HAL information]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Getting network info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Checking network adapter: [00000001] Intel(R) PRO/1000 MT Network Connection]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[MAC address = 00:50:56:85:38:B4]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[IP Address = 172.16.4.182]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[IP Address = fe80::c98:9fef:4305:51f0]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Default Gateway = 172.16.4.1]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property IPAddress001 is now = 172.16.4.182]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property IPAddress002 is now = fe80::c98:9fef:4305:51f0]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property MacAddress001 is now = 00:50:56:85:38:B4]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property DefaultGateway001 is now = 172.16.4.1]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Finished getting network info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Getting DP info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Unable to determine ConfigMgr distribution point]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Finished getting DP info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Getting WDS server info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Not Wizard = False]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property WizardComplete is now = N]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property WDSServer is now = mydeploymentserver.mydomain.com]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Finished getting WDS server info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property HostName is now = MININT-U1TGFAD]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Getting asset info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[FindFile: The file x86\Microsoft.BDD.Utility.dll could not be found in any standard locations.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[FindFile(...\Microsoft.BDD.Utility.dll) Result : 1]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[RUN: regsvr32.exe /s ""]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[FindFile(...\Microsoft.BDD.Utility.dll) Result : 0]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[RUN: regsvr32.exe /s "X:\Deploy\Tools\x64\Microsoft.BDD.Utility.dll"]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property AssetTag is now = No Asset Tag]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property SerialNumber is now = VMware-42 05 2b f7 cd 5b 63 fd-83 8a 77 84 7c ed 79 05]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property Make is now = VMware, Inc.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property Model is now = VMware Virtual Platform]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property Product is now = 440BX Desktop Reference Platform]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property UUID is now = F72B0542-5BCD-FD63-838A-77847CED7905]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property Memory is now = 2047]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property Architecture is now = X64]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property ProcessorSpeed is now = 2800]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property CapableArchitecture is now = AMD64 X64 X86]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property IsLaptop is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property IsDesktop is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property IsServer is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property IsUEFI is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property IsOnBattery is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property SupportsX86 is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property SupportsX64 is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property SupportsSLAT is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Finished getting asset info]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Getting OS SKU info]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Unable to determine Windows SKU while in Windows PE.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Determining the Disk and Partition Number from the Logical Drive X:\WINDOWS]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property OriginalArchitecture is now = ]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property OriginalArchitecture is now = ]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property OriginalArchitecture is now = ]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Getting virtualization info]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property IsHypervisorRunning is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property SupportsVT is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property SupportsNX is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property Supports64Bit is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property SupportsHyperVRole is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property IsVM is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property VMPlatform is now = VMware]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Finished getting virtualization info]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Connection succeeded to MicrosoftVolumeEncryption]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[There are no encrypted drives]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property IsBDE is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Processing the PREINSTALL phase.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Determining the INI file to use.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Finished determining the INI file to use.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Using from [Settings]: Rule Priority = DEFAULT]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[------ Processing the [DEFAULT] section ------]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Property DEPLOYROOT is now = \\mydeploymentserver\DeploymentShare$]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Using from [DEFAULT]: DEPLOYROOT = \\mydeploymentserver\DeploymentShare$]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[------ Done processing X:\Deploy\Scripts\Bootstrap.ini ------]LOG]!>

    Basics - Server 2008 R2 - SP1, WDS,  MDT 2013
    Well all, I've done this at least 20 times today and the deployment share info is still wrong...
    Someone else built and messed with this thing so i'm trying to fix it.  We have 2 MDT servers and 1 WDS that is on the Production MDT.  I've turned the test MDT off.
    It was working fine, until I updated the deployment share ... after adding some drivers for the surface pro 3 for the pxe boot
    Very Simple bootstrap.ini
    [Settings]
    Priority=Default
    [Default]
    DeployRoot=\\MMPDEPLOY02\DeploymentShare$
    UserID=xxx
    UserDomain=xxx
    UserPassword=xxx
    KeyboardLocale=en-US
    SkipBDDWelcome=YES
    It continues to show up on the client as ||mdt901w8|deploymentshare$  (test server) (pipes for \ since it makes it a link and i'm new)
    I've deleted all the .wim and associated files from all locations from the deployment share\boot folder and from the wds remote install\boot\x64\images folder where they are instead of the remote install\boot\images folder that everyone refers to.
    I really can't figure this one out... I know it's something simple I'm over looking but I can't see it..
    Any ideas..

  • Mdt 2013 refresh wizard canceled as soon as I authenticate

    I've been after this for a week or so now. I'm trying to run a POST OS Installation task, something I've done many times before, but always in MDT 2010. I"m now trying to kick off MDT 2013 from Windows 7 x64, and I get as far as being prompted for credentials.
    As soon as I enter my credentials, MDT quits and cleans up, immediately. Literally 1 second later according to the BDD.log. Nothing unusual seems to be recorded in the logs.
    If I try to run it again without deleting the MININT folder, it usually succeeds. If I then cancel out of the Task sequence menu without choosing anything and try it again, it fails again. Is this some type of bug? I've googled extensively, can't find anything.
    I've removed all software that has been updated recently from the PC, no AV is installed, nothing that should be stepping on anything.
    I'm running from an elevated prompt, like so:
    \\Server01\Deployment01$\scripts\LiteTouch.vbs
    Bdd.log returns this:

    just to loop back here... I replied to Joe offline via E-Mail. the case is very weird:
    I think it may have to do with the EVENTSHARE being defined in the bootstrap.ini file, somehow that is forcing MDT to setup a new connection to
    \\Server\Events$  and the dialog prompting for credentials is causing problems.
    *Still* that shouldn’t case this code to return true:
    ' Was the wizard   cancelled? 
    If so, exit
    If UCase(oEnvironment.Item("SkipBDDWelcome"))
    <> "YES"
    and oEnvironment.Item("WizardComplete")
    <> "Y"
    then
    Cleanup
    oLogging.ReportFailure "Welcome wizard failed or was   cancelled",
    5212
    End
    if
    The logs *SHOW* that SkipBDDWelcome and WizardComplete are set properly:
    Property SKIPBDDWELCOME is now = NO            
    ZTIGather           
    12/18/2014   8:45:14 AM  0 (0x0000)
    Property WizardComplete is now = Y     
    Wizard  12/18/2014   8:45:15 AM 
    0 (0x0000)
    Might be some kind of weird race condition in the Litetouch.wsf code. The progress bar UI fluff is pretty complex.
    My recommendations would be to place EVENTSHARE into the cs.ini file rather than the bootstrap.ini file to see if that fixes things.
    Otherwise just commenting out the code above, I’m not 100% sure why it’s there to begin with.
    -k
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • MDT 2013 won't capture 8.1 image, does not boot to PE to capture

    I am doing this with Server 2012 R2 and MDT 2013, and the reference machines are VMs
    I initially created a deployment share for creating windows 7 and windows 8.1 reference images and capturing and deployment worked ok. After getting into some more details i customized the deployment share customsettings  to make things easier and created
    a separate capture share for capturing new reference images. I updated permissions on the share so my service account has access to it. 
    In this share i imported the windows 8.1 os files and copied the sysprep and capture task sequence i used to capture my first reference image [from the original deployment share], but when running the task sequence it reboots and just goes back into windows,
    instead of windows PE to capture the image. 
    I copied a windows 7 capture sequence to the capture share, imported the windows 7 files and updated the task, and it rebooted into PE without a problem and copied an image. so I don't believe I have any permissions/customsettings problems with the new share.
    Im not seeing any errors jump out at me in the bdd.log but I'm new-ish to going over the logs and using MDT to start with so I may be missing the obvious. I am using SMS trace and dont see any red/yellow highlites either. 
    In windows 7 i did have the vm in audit mode when i mapped the share as an admin and started the task sequence. In windows 8.1 i am not in audit mode [after doing some research and learning more about using MDT it did not seem necessary]
    After comparing a run of the windows 7 task to windows 8 i see the boot.wim copied to the win 7 vm, but i dont see it on the win 8 vm. There is a partition created, i cant see data in it when i show hidden files. 
    rules for the capture share
    [Settings]
    Priority=Default
    Properties=MyCustomProperty
    [Default]
    OSInstall=Y
    SkipAppsOnUpgrade=YES
    SkipCapture=NO
    SkipAdminPassword=YES
    SkipProductKey=YES
    Heres the last part of bdd.log. New here so I can't post a link yet, didnt know if i should post the whole thing here or not to start with. 
    <![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="08:29:38.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property PHASE is now = CUSTOM]LOG]!><time="08:29:38.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
    <![LOG[--------- Script Start ---------]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
    <![LOG[LTICopyScripts processing completed successfully.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
    <![LOG[Creating startup folder item to run LiteTouch.wsf once the shell is loaded.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp\LiteTouch.lnk" created.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property BootPE is now = ]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="08:32:24.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDiskPartition : \\WIN81-REF\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\WIN81-REF\root\cimv2:Win32_LogicalDisk.DeviceID="E:"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDisk : \\WIN81-REF\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDiskPartition : \\WIN81-REF\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\WIN81-REF\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDisk : \\WIN81-REF\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ZTIUtility!GetAllFixedDrives = E: C:]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[No task sequence is in progress.]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Not running within WinPE.]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeploymentMethod = UNC]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Mapped Network UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeployRoot = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property DeployDrive is now = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeployDrive = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Phase = CUSTOM]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property DeployDrive is now = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeployDrive = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeploymentType = CUSTOM]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ResourceRoot = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property ResourceDrive is now = Z:]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ResourceDrive = Z:]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[SMS Task Sequencer already found on C:\MININT\Tools\X64]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

    Thanks for your reply. 
    The pc is not in the domain when i run litetouch. It was joined after install, then i run some local gpos/scripts against it, install all of the shared printers from servers, then i put it back in a workgroup, login as the local administrator, delete the
    domain profiles and guids in the registry, briefly connected back to a domain server [not with a mapped drive] to copy a couple of files, rebooted into the local admin account an ran litetouch. 
    After running litetouch.wsf the first time in the windows 8.1 pro vm [no changes, but manual connection] it rebooted without sysprepping or taking an image
    I deleted the task sequence and created another one with "sysprep and capture" as the sequence.  i made no changes to the task sequence. did all of the above, ran litetouch, and it just reboots. sysprep does not run and windows pe does not load. 
    if i run sysprep and boot into audit mode [as a test, since my windows 7 vm snapshot was in audit mode when it runs litetouch.wsf], then run litetouch, sysprep works, then it DID capture an image, but after that image was capture and the VM rebooted, i got
    this error when loading windows 8
    "windows could not complete the installation. To install windows on this computer, restart the installation" and if i hit ok it will reboot and error out again. 
    Haven't had any issues with that VM until now. 
    I reverted to my snapshot and just ran sysprep oobe w/ generalize to see how it would react
    it failed, setuperr.log shows SYSPRP failed to remove apps for the current user. some searching gives me information on that and makes me think its related to adding/deleting user profiles? i dont actually use or update the apps at all, i have a deploy task
    that removed most of them and customizes the start screen and those seem to work without issue. 
    found this as my reference: http://support.microsoft.com/kb/2769827/en-nz
    Sysprep has an additional provider that is added in Windows 8 to clean appx packages and generalize the image. The provider will only work if the Appx package is a per-user package or an all-user provisioned package.
    and
    Resolution
    The correct way of removing the package is to remove the package for the user running sysprep and also remove the provisioning. This can be done using the following Powershell cmdlets:
    Import-Module Appx
    Import-Module Dism
    Get-AppxPackage -AllUser | Where PublisherId -eq 8wekyb3d8bbwe | Format-List -Property PackageFullName,PackageUserInformation
    if i run that i get a lot of 
    [unknown user]: installed
    Do I just need to revise my process and start from scratch? or at least just never actually join the domain and user other profiles? thats a convenience thing so its not a big deal, really.
    I have an image made in a similar way that works, but doesnt have quite all the updates/changes i wanted. It captured [at the time] fine and installs without issue
    Heres an overview of what I do [i am open to some revisions on this]
    -deploy windows 8 base install from MDT
    -join domain, login with service account [just makes getting to some things easier]
    -install office 2010 pro plus w/ sp2 [i do understand that these can be set as an MDT app but the install takes a while and i dont like waiting on it if i dont have to]
    -install windows updates [no WSUs server currently, on my future to-do list, not my decision right now and i do understand the benefits of having one]
    -connect to servers and install all network printers [we have so many that i dont want to wait on the drivers when we do a big roll out soon]
    -install oracle software [i can get it to automate in windows 7, not 8, so i dont want to manually deal with it post-install]
    -install adobe reader/java [i do understand that these can be set as an MDT app]
    -leave domain, reboot, login as local admin
    -clean domain profiles/registry guids
    -make some local gpoedits [we dont have 8.1 enterprise and just want the start screen locked down]
    -install our AV network agent
    -lite touch. 
    any advice is appreciated

  • Unable to launch Litetouch.vbs (LiteTouch.wsf) from UNC path - A connection to the Deploayment Share Could not be made

    I am having a difficult time figuring out this issue. Here is the back story. The particular deployment share is not used in the traditional sense of deploying OS images. Instead, it is only used in deploying applications. I actually have three shares that
    do this catered to three different clientele groups; IT, teachers and students.
    I have these shares set up so that the Litetouch.vbs is used as a login script and tied to specific AD accounts. When launched, it goes through the normal MDT gathering process and eventually shows a list of applications to select to install.
    And this has and still is working perfectly for several years with both wired and wireless computers, until recently.
    My issue, I'm afraid, is with the new Intel Dual Band 7260 wireless cards/drivers (both N7260 and AC7260. The reason I suspect this is because any other desktop or laptop will launch the VBScript just fine and bring up the list of software like it has always
    done. However, if I UNC to the share and try to manually run LiteTouch.vbs, I get the "A connection to the deployment share cannot be made. Connection OK. Possible cause: Invalid credentials." That's right. I can UNC to the shares all day long, but
    when launching the LiteTouch.vbs or LiteTouch.wsf scripts, I always get the above error. So the wireless is working, in a way. Just not the way I need it to. I've tried different versions of drivers all with the same error. I've launched other VBScripts that
    I've wrote from UNC paths and they run fine.
    I am using a Domain Admin account to connect back to the deployment share through MDT. My account is a domain admin account. The share permissions are full control for Everyone and Domain Admins. The folder permissions are Read Only for Everyone and Full
    Control for Domain Admins. Like I stated, this works fine on any other system.
    When I look at the BDD.log file, sometimes I don't see anything, but most of the time I see the line "No physical adapters present. Cannot deploy over wireless." Which, in my case, is not true because I can use any other laptop with older
    Intel wireless cards, Broadcom, Atheros or whatever and it works perfectly. And, if I hardwire the offending laptops and use Ethernet instead of wireless, I can launch the VBScript and proceed just fine.
    I guess my question is, is there a way to force MDT to use any network connection, whether it's wired or wireless to deploy anything. In my case, it would be software.
    We use this option as a way for students in our high schools to be able to log in with a special account and install specific software they may need for a class. It is easier to have them do it this way than to try and install different software for
    different classes on a total of 4000 laptops.
    I am currently running Windows Server 2012 R2 with MDT 2013. The laptops are running Windows 7 SP1 x64 Enterprise and Windows 8.1.1 Enterprise.
    Any help or ideas anyone has to offer would be greatly appreciated.
    ~Mike

    I understand that you got MDT to work on other adapters, and I understand that some people dislike the AC series.
    However...
    I must strongly disagree with your conclusion:
    the Intel 7260 cards just will not work for this scenario. Any other wireless card works
    perfectly fine...
    As designed, MDT is coded to block Wireless deployment scenarios. However, the algorithm used to determine if a network adapter is wired vs wireless is highly flawed, it will check the description (caption) of the network adapter and search for the string:
    "Wireless". And if I recall, it is difficult to determine Wireless vs Wired within a VBSCript.
    Set colAdapters = objWMI.ExecQuery("select * from win32_NetworkAdapterconfiguration where IPEnabled = True")
    For Each oAdapter in colAdapters
    If Instr(UCase(oAdapter.Caption),"WIRELESS") = 0 Then
    If oAdapter.IPConnectionMetric < sIPConnectionMetric Or sIPConnectionMetric = "" Then
    sIPConnectionMetric = oAdapter.IPConnectionMetric
    End If
    End IF
    If Instr(UCase(oAdapter.Caption),"WIRELESS") Then
    sWirelessConnectionMetric = oAdapter.IPConnectionMetric
    End If
    Next
    If sIPConnectionMetric = "" Then
    oLogging.CreateEntry "No physical adapters present, cannot deploy over wireless", LogTypeError
    ValidatenetworkConnectivity = Failure
    Exit Function
    End IF
    On my Lenovo W530, for example, when I disable my Wired connection, my wireless adapter reports:
    PS C:\> gwmi -query "select * from win32_NetworkAdapterconfiguration where IPEnabled = true" | select-object Caption
    Caption
    [00000002] Intel(R) Centrino(R) Ultimate-N 6300 AGN
    AS you can see, no "Wireless" in the caption string.  A connection to the deployment share works just fine.
    Therefore...
    Yes, you *may* have gotten the installation to work on the machines that *just happen* to not have "wireless" in the caption, but I would not count on this to be true on all machines in a corporate environment.
    -k
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • MDT 2013 stalls during first boot into OS

    I just built a new MDT 2013 server (on 2012 R2) and am attempting to deploy Windows 7 from it via litetouch.  I've been working with MDT 2010 for several years so I am pretty familiar with how it works and just about everything is fine with 2013 except
    for one small issue.  When the sequence boots into Windows 7 for the first time, it just sits there at the desktop and nothing happens.  This happens every time and performs the same on virtual and physical machines.  All I have to do is reboot
    the machine and the task sequence will pick right up where it left of and finish everything correctly.
    I have found similar reports that seem to be resolved by adding pauses to either the ltibootstrap, litetouch, or ztiutility scripts to give the machine additional time to initialize, but none have worked for me.  The only seemingly relevant log entry
    comes from the BDD file.  The last entry is:
    <![LOG[RUN: regsvr32.exe /s "C:\Users\wdsbuild\AppData\Local\Temp\Tools\x64\Microsoft.BDD.Utility.dll"]LOG]!><time="17:47:46.000+000" date="03-25-2014" component="LiteTouch" context="" type="1"
    thread="" file="LiteTouch">
    <![LOG[FAILURE (Err): -2147024770  0x8007007E: CreateObject(Microsoft.BDD.Utility) -]LOG]!><time="17:47:46.000+000" date="03-25-2014" component="LiteTouch" context="" type="2" thread=""
    file="LiteTouch">
    I question the relevance of this entry because I don't actually have to manually register the dll to get it to work again.  Everything else in the BDD and SMSTS logs looks fine and don't appear to give any indication of what is going on.
    I have also attempted to add an additional restart to the task sequence immediately following the restart that is initiated after the OS has been laid down, but since the task sequence doesn't start after that first autologin, it doesn't execute.
    Thoughts?

    +1 on the drivers. I have rarely seen this, never able to reproduce in a consistent manner.
    Here is the process:
    * MDT places a hook within the unattend.xml file applied to the operating system. It calls the script LTIBootStrap.vbs. This happens in OOBE setup. If you did not sysprep or skiped OOBE setup this step may fail.
    * LTIBootStrap.vbs calls "Litetouch.wsf /Start" to install itself in the start/run after reboot into the full OS.
    IT *might* be possible that there is some other application hooked in to run at logon that is preventing MDT from running. Using autoruns.exe from sysinternals could help in debugging.
    Alternatively, you could set HIDESHELL=YES in your cs.ini file. When this is set, MDT will add it self in the registry as a "run" command rather than within the "startup" group in the shell.
    Keith Garner - keithga.wordpress.com

  • How to execute LiteTouch.vbs file remotely?

    Hi,
    I am developing a VB script which executes another VB script (LiteTouch.vbs) from MDT Deployment Share
    remotely. But I am not able to trigger it (triggering has no effect). On the other hand if I use the script to trigger some other script say for copy a file to some directory, it works perfectly. Could someone please help me in solving or atleast
    figuring out the issue?
    Client machine name: CLIENT4 and server machine name: SERVER
    The scripts are as follows:
    Script1 - Call.vbs
    strComputer = "CLIENT4"
    strCommand = "cscript.exe
    \\SERVER\Deployment$\Scripts\LiteTouch.vbs"
    Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
    Set objProcess = objWMIService.Get("Win32_Process")
    errReturn = objProcess.Create(strCommand, null, null, intProcessID)
    When I run Call.vbs, it has no effect. The runtime engine cscript is also not initialized in the taskmanager. But when I replace the second line as 'strCommand = "cscript.exe
    \\SERVER\C$\abc.vbs"' (abc.vbs say for example copies a file from one location to other) and run the Call.vbs it is executed successfully.
    I have also taken care that the Deployment$ folder is accesible from the client machine CLIENT4. Again, I have also tried to map the entire Deployment$ folder on the CLIENT4 machine and execute LiteTouch.vbs, it still has not effect.
    Any help on the same would be greatly appreciated.
    Many thanks.
    Regards, Sagar Palande

    When I developed a similar program a few years ago I used the information in this kb article:
    http://support.microsoft.com/default.aspx?scid=kb;en-us;827227
    Based on this article I decided to copy the executable from my computer to the root of C: on the remote computer (where the executable is to be run) using a mapped drive. Then I connected to the remote computer with WMI and used the Win32_Process
    class to execute program. If the program was Test.bat, then the command was "c:\\Test.bat". Finally, I deleted the executable from the remote computer.
    Your problem might be that "\" should be replaced by "\\" in the command you execute. Or, it might be necessary to copy the VBScript to the remote computer. The program I developed is linked here:
    http://www.rlmueller.net/PatchInstall.htm
    Richard Mueller
    MVP ADSI

  • MDT 2013 Windows 8.1 Task sequence Stops After first Reboot. login

    Hi There,
    The issue I am having is that After the OS gets laid down, and the Windows 8.1 computer reboots, The task sequence does not continue. It fails everytime. There are not any obvious errors that happen in the process that I can see in the logs. But I have
    customized this process quite a bit and I could use some help. We are deploying potentionally to over 30,000 computers.
    The test machine I have been using is the Surface pro 2.
    The interesting part is after a failure is if I start the process over again ,  boots into PE, then run diskpart manually from command prompt to Clean Disk 0, and then reboot and start the MDT task sequence, it will deploy fine.
    I also have a custom step that copies the TS media from the stick to a Recovery partition I create. The user can launch a -re-image or MDT refresh from an Icon/script, which will unhide this "recovery partition", and kick off a lite touch refresh.
    This works succesfully everytime. We have remote locations with very slow links, so MDT over the network or MDT integrated with SCCM is not an option at this time. So this is the solution.
    I am attempting to use MDT 2013 to deploy Windows 8.1 Offline, and using GPT partitions.
    I am using a custom Format and partiition Step, that call the CustomDiskpart.txt script from %deployroot%\Scripts.
    I am also using a Split image, as multi partitioned EFI/NTFS USB sticks are not a possibility for us , also, the USB sticks capable of this are seen by MDT as a "fixed drive" anyways. Which can cause issues in itself. So the LTIAPPLY.wsf has
    been edited to search and apply ther split .swm files.  This works well.
    After the Task sequence failure I have tried launching the Litetouch scripts from the C:\MINNINT folder manually to continue the sequence, but it doesnt  do anything.
    I don't want to always be running Diskpart manually before imaging a new OEM computer. I needa second pair of eyes on this.
    Thank You in advance!

    Hi,
    Thanks Again for taking a look.
    I checked the sysprep log in the image and they look fine. No errors.
    As requested here are some logs. Let me know if I can provide anything else.
    BDD.log
    litetouch.log
    SMSTS.log
    Im not actually attempting to provide a recovery image. What I am doing is leveraging MDT to refresh the computer remotely. We can update the MDT media on the hidden data partition,when required and kick it off remotely. Some of the computers are very
    remote, and without SCCM DP's, plus a combination of slow links and a lack of deskside techs made this a requirement. This works without incident.
    The only issue I have is on a new computer if I run the sequence (offline USB media) it will fail the first time, unless I run a diskpart clean in PE first.. Then it will succeed. Refreshing the computer is fine.

  • Since upgrade to MDT 2013, can't capture Windows 7 image.

    Hi fellas,
    I use Virtual Box to create a 32- and 64-bit reference Windows 7 VM, which I then capture using an MDT Sysprep & Capture TS.  This worked without a hitch using MDT 2012.
    I recently upgraded to MDT 2013.  Since then, after the VM syspreps and reboots, I get a boot manager error saying Windows failed to start.  Status: 0xc0000260.
    Not sure where to look for any logs.  What I've done so far:
    - Upgraded to latest version of Virtual Box (4.3.18)
    - Rebuilt both VMs from scratch.
    - Deleted and recreated the deployment share and Sysprep & Capture task sequences.
    Stumped for the time being, although I could always just boot to my Win PE disc and manually capture with imagex.  But c'mon.

    Thanks for your input, but this is indeed a configuration issue, and it makes sense.
    Vbox VMs are configured according to the guest OS installed on them.  For my Windows 7 x64 VM, it's configured of course to run as Windows 7 x64.  In the MDT 2012 environment, the Windows PE version
    was 3.0, which is based on Windows 7, and hence the VM could boot to it since it was configured for it.
    But MDT 2013 uses PE 5.0, based on 8.1.  The VM crashes or throws an error when trying to boot the PE 5.0 boot image.  I went into the VM's settings and changed the Guest OS to 8.1 x64, and it booted successfully to Windows PE and captured the
    image according to the Sysprep & Capture sequence.
    Sorry for the wild goose chase fellas.  This should've been the first thing I checked.

  • Server 2012 R2 + MDT 2013 + WINLOAD.EXE error

    Hi All,
    After watching some videos on MDT 2013 integration with SCCM 2012 I have been testing some builds of Windows Server 2012 R2. The MDT 2013 integration is working well with Database look-ups providing the required rules for customsettings.ini. To coincide
    with the tests I am using the MDT 2013 Server Task Sequence Template.
    Unfortunately I am hitting an error whereby, when using the MDT Task Sequence the full Operating System fails to start with a:
    \Windows\System32\Winload.exe, 0xC000000F, File is Missing or Corrupt
    Note: This is happening when the full OS is starting up. This is not a WinPE startup issue.
    When I use a non-MDT Task Sequence, i.e. a typical task sequence we use for OSD the build process works OK. We still have MDT database integration working in that Task Sequence however.
    Some background info:
    As per our normal process we are using a Windows Server 2012 R2 Capture image. The reference machine was build and capture using a partition scheme of (Partition 1 - 500MB + No Drive Letter + Hidden, Partition 2 - 100% of disk - Drive C:\)
    This is a new SCCM 2012 R2 implementation and as such we installed CU3 as part of our build process. CU4 is yet to be applied.
    Our WinPE Boot Images are WinPE 5 with a build number of 6.3.9600.16384
    As we have an existing SCCM 2007 environment I am currently using USB Boot media to kick off the Task Sequence
    We are only considering a "New Computer" build scenario. The MDT 2013 Task Sequence already detects that because the "_SMSTSinWinPE" = True.
    In both Task sequences the Format and Partition step is as follows:
    Disk 0
    Standard(MBR)
    BDEDrive (Primary) - 499MB, Marked Active with variable BDEDrive assigned
    OSDisk (Primary) - 90GB variable OSDisk assigned
    In both Task sequences the Apply Operating System step is as follows:
    Using Captured Image
    Apply operating system from a captured image (Image 2-2)
    Apply image to Logical Drive (OSDisk)
    In both Task sequences the Apply Data Image step is as follows:
    Using Captured Image
    Image 1-1 (from the same captured image as shown above)
    Apply image to Logical Drive (BDEDrive)
    What has been done so far:
    Already eliminated driver packs as the problem occurs with and without them
    Have monitored the build process (during WinPE that is) to determine what disks and partitions are in play at that stage. The 500MB BDE and 90GB OS Partitions are created as expected. The Apply OS and Apply Data Image steps are applying to the correct partitions.
    I have used the Windows Server 2012 R2 Installation CD and tried to run a bootrec /fixmbr + bootrec /fixboot
    I have used the Windows Server 2012 R2 Installation CD and tried to run a bootrec /rebuildbcd
    I have tried toggling the "OSDPreserveDriveLetter" variable from True to False and back again. Based on my interpretation of the SCCM 2012 R2 + Windows Server 2012 drive letter issue this should be set to True so the capture image drive letters
    are preserved.
    I have disabled an UEFI Partitioning steps just as a precaution.
    There is no Bitlocker steps involved yet.
    I have trawled through the SMSTS.LOG. So far it looks OK to me:
    !--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Expand a string: WinPEandFullOS TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Executing command line: tsenv.exe "OSDPreserveDriveLetter=True" TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Finished with error code 0 TSEnv 18/02/15 8:09:49 AM 728 (0x02D8)
    Process completed with exit code 0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    !--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Successfully completed the action (Set Variable for Drive Letter) with the exit win32 code 0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    MP server https://SOMETHING24.SOMETHING. Ports 80,443. CRL=false. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Setting authenticator TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set authenticator in transport TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Sending StatusMessage TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Setting message signatures. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Setting the authenticator. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    CLibSMSMessageWinHttpTransport::Send: URL: SOMETHING24.SOMETHING:443 CCM_POST /ccm_system_AltAuth/request TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    In SSL, but with no client cert TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Request was successful. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Expand a string: %_SMSTSMDataPath%\Logs TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Clear local default environment TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Updated security on object D:\_SMSTaskSequence. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a global environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a global environment variable _SMSTSInstructionStackString=0 33 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a TS execution environment variable _SMSTSInstructionStackString=0 33 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Save the current environment block TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Successfully save execution state and environment to local hard disk TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Start executing an instruction. Instruction name: Apply Operating System Image. Instruction pointer: 43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a global environment variable _SMSTSCurrentActionName=Apply Operating System Image TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a global environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a local default variable OSDImageIndex TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLog TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Expand a string: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Expand a string: TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Command line for extension .exe is "%1" %* TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Start executing the command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    !--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Expand a string: WinPE TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Executing command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Command line for extension .exe is "%1" %* ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Set command line: "OSDApplyOS.exe" /image:S0200034,2 /target:D: /runfromnet:False ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Found run from net option: 0 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Not a data image ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    ApplyOSRetry: ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    TSLaunchMode: UFD ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    OSDUseAlreadyDeployedImage: FALSE ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    'C:\' not a removable drive ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    The volume D:\ exists and is a local hard drive. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    The volume D:\ is using a valid file system. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Windows target partition is 0-2, driver letter is D:\ ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Verifying boot volume is NTFS. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    The machine does not have a local client cache. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    ResolveSource flags: 0x00000001 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    SMSTSPersistContent: . The content for package S0200034 will be persisted ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    DownloadOnDemand flag is true. Attempting to download content locally for Package S0200034. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Locations: Multicast = 0, HTTP = 2, SMB = 0. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Package Flags: 0x01000000 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Multicast is not enabled for the package. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Trying https://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    GetDirectoryListing() entered ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Initializing HTTP transport. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Setting Authenticator. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Set authenticator in transport ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Setting Media Certificate. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    WinHttp credentials set ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    CLibSMSMessageWinHttpTransport::Send: URL: SOMETHING24.SOMETHING:443 PROPFIND /NOCERT_SMS_DP_SMSPKG$/S0200034 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    In SSL, but with no client cert ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    401 - Unsuccessful with anonymous access. Retrying with context credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Using thread token for request ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    401 - Unsuccessful with context credentials. Retrying with supplied credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Request was successful. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    DAV response string is:
    <?xml version="1.0" encoding="utf-8" ?><D:multistatus xmlns:D="DAV:"><D:response><D:href>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/sccm?/S0200034/</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:supportedlock/><D:getetag/><D:creationdate/><D:iscollection>1</D:iscollection><D:resourcetype><D:collection/></D:resourcetype><D:ishidden>0</D:ishidden><D:displayname>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/sccm?/S0200034/</D:displayname><D:getlastmodified></D:getlastmodified><D:getcontentlanguage/><D:getcontentlength>0</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim</D:displayname><D:getlastmodified>Tue, 10 Feb 2015 04:56:27 GMT</D:getlastmodified><D:getcontentlength>6814100762</D:getcontentlength></D:prop></D:propstat></D:response></D:multistatus> ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    List of files to be downloaded ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    File: http://SOMETHING24.SOMETHING:443/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    GetDirectoryListing() successfully completed ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    401 - Unsuccessful with anonymous access. Retrying with context credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    401 - Unsuccessful with context credentials. Retrying with supplied credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 0-2147483646 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 2147483647-4294967293 ApplyOperatingSystem 18/02/15 8:10:40 AM 724 (0x02D4)
    Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 4294967294-6442450940 ApplyOperatingSystem 18/02/15 8:11:23 AM 724 (0x02D4)
    Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 6442450941-6814100761 ApplyOperatingSystem 18/02/15 8:12:14 AM 724 (0x02D4)
    Downloaded file from http://SOMETHING24.SOMETHING:443/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim to D:\_SMSTaskSequence\Packages\S0200034\dos-20150210.wim ApplyOperatingSystem 18/02/15 8:12:21 AM 724 (0x02D4)
    VerifyContentHash: Hash algorithm is 32780 ApplyOperatingSystem 18/02/15 8:12:21 AM 724 (0x02D4)
    Content successfully downloaded at D:\_SMSTaskSequence\Packages\S0200034. ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Opening image file D:\_SMSTaskSequence\Packages\S0200034\dos-20150210.wim ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Image file S0200034 version "2015-02-10" will be applied ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Starting to apply image 2 from dos-20150210.wim to D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Wiping D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Set "D:\_SMSTaskSequence" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Set "%OSDStateStorePath%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Set "%_SMSTSClientCache%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Set "%_SMSTSNewClientCachePathToCleanup%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Skipping D:\System Volume Information for wipe ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Skipping D:\_SMSTaskSequence for wipe ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Calculating expected free space. ApplyOperatingSystem 18/02/15 8:14:12 AM 1764 (0x06E4)
    Reporting deletion progress. ApplyOperatingSystem 18/02/15 8:14:12 AM 1764 (0x06E4)
    Successfully wiped D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Applying image to D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Applying image 2 to volume D: ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Executing command line: X:\windows\system32\cmd.exe /k TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
    The command completed successfully. TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
    Successfully launched command shell. TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
    Successfully applied image to D:\ ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
    OfflineRegistry::Init("D:\Windows") ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
    Loading offline registry hive "D:\Windows\system32\config\software" into HKLM\OfflineRegistry1 ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
    Loading offline registry hive "D:\Windows\system32\config\system" into HKLM\OfflineRegistry2 ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
    CurrentControlSet is mapped to ControlSet001 ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
    System root for target OS is D:\Windows, System drive is D: ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
    OS Version is 6.3 ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
    Successfully loaded a source BCD boot system ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
    SetupNewOS: Loaded source boot system from target volume "D:\" ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
    BootLoader::restore: D:\, C:\ ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
    Saving bcd store to D:\_SMSTaskSequence\ApplyBootSystem\boot\BCD ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
    Command line for extension .exe is "%1" %* ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
    Set command line: "bcdboot.exe" D:\Windows /s C:\ /l en-US ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
    Executing command line: "bcdboot.exe" D:\Windows /s C:\ /l en-US ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
    Process completed with exit code 0 ApplyOperatingSystem 18/02/15 8:21:11 AM 724 (0x02D4)
    Unloading offline SOFTWARE registry hive ApplyOperatingSystem 18/02/15 8:21:11 AM 724 (0x02D4)
    Unloading offline SYSTEM registry hive ApplyOperatingSystem 18/02/15 8:21:12 AM 724 (0x02D4)
    Updating MountedDevices key in target system registry ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    OfflineRegistry::Init("D:\Windows") ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Loading offline registry hive "D:\Windows\system32\config\software" into HKLM\OfflineRegistry1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Loading offline registry hive "D:\Windows\system32\config\system" into HKLM\OfflineRegistry2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    CurrentControlSet is mapped to ControlSet001 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    OS volume after boot is: '\DosDevices\C:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Reading '\DosDevices\D:' value under MountedDevices in WinPE registry ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 0 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 0 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb272081-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb272089-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb27208a-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 3 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 3 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb27208b-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 4 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 4 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb27208c-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 5 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 5 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\DosDevices\X:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 6 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 6 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb272095-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 7 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 7 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb272098-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 8 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 8 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\DosDevices\G:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 9 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 9 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\DosDevices\H:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 10 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 10 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\DosDevices\I:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 11 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 11 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb27209b-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 12 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 12 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\DosDevices\J:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 13 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 13 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '#{cb2720cf-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 14 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 14 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '#{cb2720d2-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 15 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 15 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '#{cb2720d5-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 16 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 16 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '#{cb2720e2-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 17 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 17 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb2720f3-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 18 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 18 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '#{cb272126-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 19 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 19 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb272139-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Enumerating index: 20 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Enumerated index: 20 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Found value: '\DosDevices\C:' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Enumerating index: 21 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Enumerated index: 21 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Found value: '\??\Volume{cb27213d-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Data for value '\DosDevices\D:' matches data for value '\??\Volume{cb27213d-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Done enumerating. Closing mounted devices key. ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Closed mounted devices key. ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Deleting MountedDevices key on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Creating new MountedDevices key on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Writing new values to MountedDevices on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Successfully updated MountedDevices on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Unloading offline SOFTWARE registry hive ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Unloading offline SYSTEM registry hive ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Finished updating MountedDevices in target system registry (0x00000000) ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing up known name surrogate reparse points... ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing junction point path [D:\Documents and Settings] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing junction point path [D:\users\Administrator\AppData\Local\Application Data] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing junction point path [D:\users\Administrator\AppData\Local\History] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing junction point path [D:\users\Administrator\AppData\Local\Microsoft\Windows\Temporary Internet Files] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing junction point path [D:\users\Administrator\AppData\Local\Temporary Internet Files] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing junction point path [D:\users\Administrator\Application Data] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing junction point path [D:\users\Administrator\Cookies] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing junction point path [D:\use
    The fact that our normal Task Sequence works OK eliminates the Capture image and the WinPE boot images. It must be something I have not configured or configured incorrectly in the MDT task sequence.
    Any suggestions would be great.
    NSutton

    Hi,
    If I were you, I would Streamline the MDT Task Sequence to find the root cause.
    Moreover, please refer to the link below:
    How to fix Windows System32 Winload.exe Missing Or Corrupt 0xc000000f Error?
    http://winwiki.org/windows-system32-winload-exe-missing-or-corrupt-0xc000000f/
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • MDT 2010 Deleted task still running

    Hi Guys, I have been using MDT 2010 with Litetouch for deploying Windows 7 x64 clents for the last month. I have a main task sequence which does the deployment and a test task sequence for me to try new things out.
    On the test task sequence I created custom task which deletes a desktop icon, the problem now is that even after I have deleted this task it still runs even though its not in the task sequence any longer.
    Even when I create a new task sequence the deleted custom task still runs! This is very strange any ideas?

    Hi,
    it sounds impossible :)
    I think the same action might have been configured in another step, or it might be added as a dependency on some application.
    To verify, you could take a look at the xml files that descrive your applications and taks sequences in .\control.
    MCP/MCSA/MCTS/MCITP

Maybe you are looking for

  • DVI to video adaptor question

    I am new the Apple world but am thinking of buying a Mac mini as a music and photo server. I will use it mainly via a TV with the remote control and Front Row. I am in the UK and have a CRT Panasonic (28" wide) with SCART connections. I also have a S

  • How do I save my pages documents from icloud onto my iMac?

    I just purchased my first mac.  I have an iphone and ipad however, so I have lots of pages documents.  When I open pages i have two tabs, iCloud and On My Mac.  How do i get all of my folders and files from the one to the other? thanks for your help!

  • Multi-Person iChat Video Quality

    Hi, I am using iChat with 2 other person (so a total of 3 people in the video conferencing). What we noticed is that the audio quality remains great. But as soon as the third person joins the video chat, the video quality decrease dramatically. Any o

  • Deprecated

    What does it mean when it says Warning [deprication] show() in java.awt.Dialog() has been deprecated?

  • HP 7280 All-in=one - can you automatically print the fax log?

    On my old HP, you could set a regular day for it to automatically print fax logs. I can't find that setting on the HP 7280 (Win 7 computer), and I often forget to print out a log. (and nothing appears in the fax log box from the HP Solutions Center).