So I have the MDT task sequence set to enable Bitlocker and put the recovery key into Active Directory for easy access by the Domain Admins.  When I tested it, everything seemed fine.  When I went to image a production machine, I found that the machine kept prompting the user for the recovery key.  I then went about trying to add a GPUpdate /force command into the task sequence thinking that it might just be a policy issue.  When I went to test this on one of our spare machines, I ended up getting a failure message at the end stating the task sequence had failed.  I have added a link to all of the log files from this attempt in order to allow you all to see what is going on.  I am not sure if I should just add in a reboot command to the system in order for it to make sure it gets all of the right GPO's applied to the system.  Any help on this issue would be appreciated.

https://1drv.ms/f/s!AnkJZ7azSrQpbwX5A61XdYP6aXs

Running MDT 8456, ADK 1903, and Windows PE Add-on 1903

Deploying Windows 10 LTSC 2019

After deploying the image all Junction Points still exist, however, they are begin with D:\

What cause this and how do I fix it?

Hello

The topic title might seem a bit head scratching but hear me out. I'm attempting to create an offline MDT deployment solution for my branch offices that have less than stellar bandwidth. I've created the offline media, booted to it, and the image installs without issue. However, even though I use the option to "Configure with Static IP Address" prior to pushing the image, the IP Address I specify doesn't seem to stick.

Clicking this option when doing an online install, however, does yield the results I'm out for.

Basically, I'm trying to cut out the need to connect back to my MDT server for some of my branch offices to decrease the time it would take to push the image to these offices. I figure instead of connecting back to my server, just have it pull all of the information it needs from a USB stick and do everything else the same. Am I making sense and can this be a realistic option?

Other than this small blip, my offline install works without issue. Except for when it attempts to join the computer back to the domain and install patches for obvious reasons. Any thoughts?

Is it possible to image a computer with a wim file on a different file share than the deployment share?  I'm low on space.

Hi, I got 'Unable to find LiteTouch.wsf needed to continue the deployment' error after deployment - the deployment itself ended with 0 error/warning in summary window. I deployed with USB HD, after deployment the system shut down (set that in .ini), and I unplugged the USB - if I leave the USB connected, when I power on the machine, it will re-deploy from the USB.

I searched the error and saw so many different cases and suggestions, I also tried one recommended solution from this forum (https://social.technet.microsoft.com/Forums/en-US/1d31aeac-3f62-4a40-8c7c-b8a1efed6fd9/unable-to-find-litetouchwsf-after-imaging?forum=mdt), but it messed up my deployment and it took me couple hours to resume. BTW, I tried it in build TS (not dep TS, maybe I did incorrectly?).

Can anybody shine light on the issue? A little more info - MDT ver: 6.3.8443.1000; image OS: win10 x64

The BDD.log (with some replacement of company sensitive words) is pasted below, as well as the disk manager screenshot of the deployed system.

Event 41001 sent: ZTISetVariable processing completed successfully. ZTISetVariable 1/11/2018 12:38:42 AM 0 (0x0000)
Microsoft Deployment Toolkit version: 6.3.8443.1000 ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
------------------------- Object Initialization ------------------------- ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
------------------------- Initialization ------------------------- ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Synchronizing the environments. ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Property DeployRoot is now = H:\Deploy ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Property DeployDrive is now = H: ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Property ResourceRoot is now = H:\Deploy ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Property ResourceDrive is now = H: ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Property OSDTargetDriveCache is now = D: ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Finished synchronizing the environments. ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Getting OS info ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Property OSCurrentVersion is now = 10.0.16299 ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Property OSCurrentBuild is now = 16299 ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Property OSVersion is now = WinPE ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Property IsServerOS is now = False ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Property IsServerCoreOS is now = False ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Finished getting OS info ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Getting HAL information ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Property HALName is now = acpiapic ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Finished getting HAL information ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Getting network info ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Finished getting network info ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Getting DP info ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Unable to determine ConfigMgr distribution point ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Finished getting DP info ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Getting WDS server info ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Unable to determine WDS server name, probably not booted from WDS. ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Finished getting WDS server info ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Property HostName is now = MININT-R24HTJ7 ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Getting asset info ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Unable to determine asset tag via WMI. ZTIGather 1/11/2018 12:38:42 AM 0 (0x0000)
Property AssetTag is now =  ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property SerialNumber is now = FNWCSS1 ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property Make is now = Dell Inc. ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property Model is now = Latitude E6420 ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property Product is now = 0PH12P ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property UUID is now = 4C4C4544-004E-5710-8043-C6C04F535331 ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property Memory is now = 3977 ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property Architecture is now = X64 ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property ProcessorSpeed is now = 2801 ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property CapableArchitecture is now = AMD64 X64 X86 ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property IsLaptop is now = True ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property IsDesktop is now = False ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property IsServer is now = False ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property IsUEFI is now = False ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property IsOnBattery is now = False ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property SupportsX86 is now = True ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property SupportsX64 is now = True ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property SupportsSLAT is now = True ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Finished getting asset info ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Getting OS SKU info ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Unable to determine Windows SKU while in Windows PE. ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Determining the Disk and Partition Number from the Logical Drive X:\windows ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Getting virtualization info ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property IsHypervisorRunning is now = False ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property SupportsVT is now = True ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property SupportsNX is now = True ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property Supports64Bit is now = True ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property SupportsHyperVRole is now = True ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
This computer does not appear to be a virtual machine (BIOS is 'DELL   - 6222004'). ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Property IsVM is now = False ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Finished getting virtualization info ZTIGather 1/11/2018 12:38:43 AM 0 (0x0000)
Connection succeeded to MicrosoftVolumeEncryption ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
There are no encrypted drives ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
Property IsBDE is now = False ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
Processing the STATERESTORE phase. ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
Event 41000 sent: Processing the STATERESTORE phase. ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
Only gathering local settings (no rules processing). ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
Determining the INI file to use. ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
Using DEFAULT VALUE: Ini file = H:\Deploy\Control\CustomSettings.ini ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
Finished determining the INI file to use. ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
Skipping rules processing. ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
Remapping variables. ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
Property TaskSequenceID is now = Rep03-10N-DEP ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
Property DeploymentType is now = NEWCOMPUTER ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
Property OSDNetworkJoinType is now = 1 ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
Property OSDWorkGroupName is now = WORKGROUP ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
Finished remapping variables. ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
ZTIGather processing completed successfully. ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
Event 41001 sent: ZTIGather processing completed successfully. ZTIGather 1/11/2018 12:38:44 AM 0 (0x0000)
Property post is now =  LTIApply 1/11/2018 12:38:44 AM 0 (0x0000)
Microsoft Deployment Toolkit version: 6.3.8443.1000 LTIApply 1/11/2018 12:38:44 AM 0 (0x0000)
The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. LTIApply 1/11/2018 12:38:44 AM 0 (0x0000)
Will boot into Windows PE architecture x64 to match OS being deployed. LTIApply 1/11/2018 12:38:44 AM 0 (0x0000)
OSDTargetDriveCache was determined earlier : D: LTIApply 1/11/2018 12:38:44 AM 0 (0x0000)
Property OSDTargetDriveCache is now = D: LTIApply 1/11/2018 12:38:44 AM 0 (0x0000)
Property OSDisk is now = D: LTIApply 1/11/2018 12:38:44 AM 0 (0x0000)
LTIApply processing completed successfully. LTIApply 1/11/2018 12:38:44 AM 0 (0x0000)
Event 41001 sent: LTIApply processing completed successfully. LTIApply 1/11/2018 12:38:44 AM 0 (0x0000)
Microsoft Deployment Toolkit version: 6.3.8443.1000 ZTIDomainJoin 1/11/2018 12:38:44 AM 0 (0x0000)
The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. ZTIDomainJoin 1/11/2018 12:38:44 AM 0 (0x0000)
Property DomainJoinAttempts is now = 1 ZTIDomainJoin 1/11/2018 12:38:44 AM 0 (0x0000)
Not attempting to join a domain because JoinWorkgroup = WORKGROUP. ZTIDomainJoin 1/11/2018 12:38:44 AM 0 (0x0000)
ZTIDomainJoin processing completed successfully. ZTIDomainJoin 1/11/2018 12:38:44 AM 0 (0x0000)
Event 41001 sent: ZTIDomainJoin processing completed successfully. ZTIDomainJoin 1/11/2018 12:38:44 AM 0 (0x0000)
Microsoft Deployment Toolkit version: 6.3.8443.1000 ZTIPowerShell 1/11/2018 12:38:44 AM 0 (0x0000)
The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. ZTIPowerShell 1/11/2018 12:38:44 AM 0 (0x0000)
PowerShell version detected: 5.1.16299.15 ZTIPowerShell 1/11/2018 12:38:44 AM 0 (0x0000)
About to run: "H:\Deploy\Tools\Modules\Microsoft.BDD.TaskSequenceModule\Microsoft.BDD.TaskSequencePSHost40.exe" "H:\Deploy\Scripts\UtilityScripts\US_Move-Files\US_Move-Files.ps1" "D:\MININT\SMSOSD\OSDLOGS" -BuildScriptPath X:\windows\Logs\MDTLogs -SourcePath H:\Deploy\Scripts\DeployScripts -myLogPath X:\windows\Logs\MDTLogs -myLogName "MDT-PSLog.log" -myModulePath "H:\Deploy\Scripts\UtilityScripts\PSModules" ZTIPowerShell 1/11/2018 12:38:44 AM 0 (0x0000)
TSHOST: Script completed with return code 0 TaskSequencePSHost 1/11/2018 12:38:49 AM 0 (0x0000)
ZTIPowerShell processing completed successfully. ZTIPowerShell 1/11/2018 12:38:49 AM 0 (0x0000)
Event 41001 sent: ZTIPowerShell processing completed successfully. ZTIPowerShell 1/11/2018 12:38:49 AM 0 (0x0000)
Microsoft Deployment Toolkit version: 6.3.8443.1000 ZTIPowerShell 1/11/2018 12:38:49 AM 0 (0x0000)
The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. ZTIPowerShell 1/11/2018 12:38:49 AM 0 (0x0000)
PowerShell version detected: 5.1.16299.15 ZTIPowerShell 1/11/2018 12:38:49 AM 0 (0x0000)
<Message containing password has been suppressed> ZTIPowerShell 1/11/2018 12:38:49 AM 0 (0x0000)
X:\windows\Logs\MDTLogs\PostInstallScripts\WinXAddUser.vbs not found.  Account %WinXAdminName% created. TaskSequencePSHost 1/11/2018 12:38:52 AM 0 (0x0000)
TSHOST: Script completed with return code 0 TaskSequencePSHost 1/11/2018 12:38:52 AM 0 (0x0000)
ZTIPowerShell processing completed successfully. ZTIPowerShell 1/11/2018 12:38:52 AM 0 (0x0000)
Event 41001 sent: ZTIPowerShell processing completed successfully. ZTIPowerShell 1/11/2018 12:38:52 AM 0 (0x0000)
Microsoft Deployment Toolkit version: 6.3.8443.1000 ZTIPowerShell 1/11/2018 12:38:52 AM 0 (0x0000)
The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. ZTIPowerShell 1/11/2018 12:38:52 AM 0 (0x0000)
PowerShell version detected: 5.1.16299.15 ZTIPowerShell 1/11/2018 12:38:52 AM 0 (0x0000)
About to run: "H:\Deploy\Tools\Modules\Microsoft.BDD.TaskSequenceModule\Microsoft.BDD.TaskSequencePSHost40.exe" "H:\Deploy\Scripts\UtilityScripts\US_Install-Updates\US_Install-Updates.ps1" "D:\MININT\SMSOSD\OSDLOGS" -myLogPath X:\windows\Logs\MDTLogs -myLogName "\MDT-PSLog.log" -myModulePath "H:\Deploy\Scripts\UtilityScripts\PSModules" -myMSUPath "X:\windows\Logs\MDTLogs\MDTScripts\DS_AdditionalMSUFiles" ZTIPowerShell 1/11/2018 12:38:52 AM 0 (0x0000)
TSHOST: Script completed with return code 0 TaskSequencePSHost 1/11/2018 12:38:56 AM 0 (0x0000)
ZTIPowerShell processing completed successfully. ZTIPowerShell 1/11/2018 12:38:56 AM 0 (0x0000)
Event 41001 sent: ZTIPowerShell processing completed successfully. ZTIPowerShell 1/11/2018 12:38:56 AM 0 (0x0000)
Property restore is now =  ZTIUserState 1/11/2018 12:38:56 AM 0 (0x0000)
Microsoft Deployment Toolkit version: 6.3.8443.1000 ZTIUserState 1/11/2018 12:38:56 AM 0 (0x0000)
The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. ZTIUserState 1/11/2018 12:38:56 AM 0 (0x0000)
OSDTargetDriveCache was determined earlier : D: ZTIUserState 1/11/2018 12:38:56 AM 0 (0x0000)
Property OSDTargetDriveCache is now = D: ZTIUserState 1/11/2018 12:38:56 AM 0 (0x0000)
Property OSDisk is now = D: ZTIUserState 1/11/2018 12:38:56 AM 0 (0x0000)
User state restore bypassed. ZTIUserState 1/11/2018 12:38:56 AM 0 (0x0000)
ZTIUserState processing completed successfully. ZTIUserState 1/11/2018 12:38:56 AM 0 (0x0000)
Event 41001 sent: ZTIUserState processing completed successfully. ZTIUserState 1/11/2018 12:38:56 AM 0 (0x0000)
Microsoft Deployment Toolkit version: 6.3.8443.1000 ZTIPowerShell 1/11/2018 12:38:56 AM 0 (0x0000)
The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. ZTIPowerShell 1/11/2018 12:38:56 AM 0 (0x0000)
PowerShell version detected: 5.1.16299.15 ZTIPowerShell 1/11/2018 12:38:56 AM 0 (0x0000)
About to run: "H:\Deploy\Tools\Modules\Microsoft.BDD.TaskSequenceModule\Microsoft.BDD.TaskSequencePSHost40.exe" "H:\Deploy\Scripts\UtilityScripts\US_Move-Files\US_Move-Files.ps1" "D:\MININT\SMSOSD\OSDLOGS" -BuildScriptPath X:\windows\Logs\MDTLogs -clean -purge -myLogPath X:\windows\Logs\MDTLogs -myLogName "MDT-PSLog.log" -myModulePath "H:\Deploy\Scripts\UtilityScripts\PSModules" ZTIPowerShell 1/11/2018 12:38:56 AM 0 (0x0000)
X:\windows\Logs\MDTLogs\PostInstallScripts location not found TaskSequencePSHost 1/11/2018 12:39:00 AM 0 (0x0000)
TSHOST: Script completed with return code 0 TaskSequencePSHost 1/11/2018 12:39:00 AM 0 (0x0000)
ZTIPowerShell processing completed successfully. ZTIPowerShell 1/11/2018 12:39:00 AM 0 (0x0000)
Event 41001 sent: ZTIPowerShell processing completed successfully. ZTIPowerShell 1/11/2018 12:39:00 AM 0 (0x0000)
Command completed, return code = 0 LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
LTI deployment completed successfully LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Event 41015 sent: LTI deployment completed successfully LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Property RetVal is now = 0 LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Using a local or mapped drive, no connection is required. LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
OSDTargetDriveCache was determined earlier : D: LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Property OSDTargetDriveCache is now = D: LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Property OSDisk is now = D: LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\DS_WinXAddUser.log to X:\windows\Logs\MDTLogs\WIN10RS3-REF\DS_WinXAddUser.log LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\LiteTouch.log to X:\windows\Logs\MDTLogs\WIN10RS3-REF\LiteTouch.log LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\LTIApply.log to X:\windows\Logs\MDTLogs\WIN10RS3-REF\LTIApply.log LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\LTICopyScripts.log to X:\windows\Logs\MDTLogs\WIN10RS3-REF\LTICopyScripts.log LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\US_Install-Updates.log to X:\windows\Logs\MDTLogs\WIN10RS3-REF\US_Install-Updates.log LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\US_Move-Files.log to X:\windows\Logs\MDTLogs\WIN10RS3-REF\US_Move-Files.log LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\Wizard.log to X:\windows\Logs\MDTLogs\WIN10RS3-REF\Wizard.log LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\ZTIConfigure.log to X:\windows\Logs\MDTLogs\WIN10RS3-REF\ZTIConfigure.log LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\ZTIDiskpart.log to X:\windows\Logs\MDTLogs\WIN10RS3-REF\ZTIDiskpart.log LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\ZTIDomainJoin.log to X:\windows\Logs\MDTLogs\WIN10RS3-REF\ZTIDomainJoin.log LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\ZTIdrivers.log to X:\windows\Logs\MDTLogs\WIN10RS3-REF\ZTIdrivers.log LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\ZTIGather.log to X:\windows\Logs\MDTLogs\WIN10RS3-REF\ZTIGather.log LiteTouch 1/11/2018 12:39:00 AM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\ZTINextPhase.log to X:\windows\Logs\MDTLogs\WIN10RS3-REF\ZTINextPhase.log LiteT .......

Hello all,

I am trying to deploy Windows 10 1903 using MDT 8456 and am running into a problem. I am testing this out on a Dell Latitude E5530 that had Windows 7 installed and secure boot off in legacy BIOS mode.

I changed the BIOS to UEFI, secure boot on and managed to deploy Windows 10 successfully through MDT. I have now made some changes to my task sequence and am attempting to deploy to this same machine again, however, now after MDT applies the image and the computer reboots, I get an error that there are no bootable devices.

If I use the boot menu, I see under the UEFI entries that there is an entry for Windows Boot Manager. If I select that, the computer boots normally into Windows and the task sequence resumes and completes normally.

Does anyone know what is going on here and how can I fix it so that I don't have to manually choose Windows from the boot menu to start the computer? Thanks!

I'm having a weird issue that I cannot seem to resolve and would appreciate any assistance.

I have a deployment cd that will no longer work. I get the invalid credentials message. Nothing was changed in the deployment and I have recreated the boot image numerous times since this issue popped up.

Now this image last worked correctly on 3/12. The following week some things were changed as we have been trying to get PXE booting working correctly in our tech area which is being handled by others who only have access to the WDS server and the boot image. They managed to get this working but was receiving the same invalid credential message. Turns out the reason for this was an old boot image from a deleted deployment share was being used. This has been resolved and the correct boot image allows us to run deployments successfully.

This same image on CD however does not. Canceling out of the Invalid credential screen shows that it is trying to connect to a deployment share that is no longer there. It was valid at one time but has since been deleted and the share that replaced was created from scratch so nothing should be pointing to that location.

So I'm at a loss as to why it is doing this and have no idea where to look. So far I've only found that the bootstrap.ini has the deployment share listed and this is correct on the CD. Where else would it be pulling this information from? What can I do short of recreating a new share or rebuilding the current one? 

Hello!

We have a 20 identical PCs (Windows 7 only) connected to a local workgroup. I used VM to prepare a thick image with all the apps needed. Now i am confused with the the deployment: Can MDT work from a Windows 7 PC to deploy the image over the LAN to other PCs?

I noticed antivirus is interfering with the deployment workbench and maybe other MDT-related processes.  For instance, I am unable to open the unattended.xml file without errors when A/V is running.

What are the recommended files and folders that should be excluded from antivirus scanning on a machine running ADK and MDT 2013?

I'm trying to capture a new image from a reference desktop computer, but I always get a failure.
Here are the details : 

ZTI ERROR - unhandled error returned by LTlApply: Argument ou appel de procédure incorrect (5)

Litetouch deployment failed, Return Code -2147467259 0x80004005

Execution engine result code: Reboot (2)

Execution engine result code: Reboot (2)

Execution engine result code: Reboot (2)

Execution engine result code: Reboot (2)

Execution engine result code: Reboot (2)

RegQueryValueExW is unsuccessful for SoftwareXMicrosoftXSMSXTask Sequence, SMSTSEndProgram

GetTsRegValue0 is unsuccessful. 0x80070002.

Failed to run the action: Apply Windows PE.

Access is denied. (Error: 00000005,' Source: Windows)

The execution of the group (Capture Image) has failed and the execution has been aborted. An action failed.

Operation aborted (Error: 80004004,' Source: Windows)

Failed to run the last action: Apply Windows PE. Execution of task sequence failed.

Access is denied. (Error: 00000005,' Source: Windows)

Task Sequence Engine failed! Code: enExecutionFail

Task sequence execution failed With error code 80004005

RegQueryValueExW is unsuccessful for SoftwareXMicrosoftXSMSXTask Sequence, SMSTSEndProgram

GetTsRegValue0 is unsuccessful. 0x80070002.

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

Failed to run the action: Apply Windows PE.

Access is denied. (Error: 00000005,' Source: Windows)

The execution of the group (Capture Image) has failed and the execution has been aborted. An action failed.

Operation aborted (Error: 80004004,' Source: Windows)

Failed to run the last action: Apply Windows PE. Execution of task sequence failed.

Access is denied. (Error: 00000005,' Source: Windows)

Task Sequence Engine failed! Code: enExecutionFail

Task sequence execution failed With error code 80004005

RegQueryValueExW is unsuccessful for SoftwareXMicrosoftXSMSXTask Sequence, SMSTSEndProgram

GetTsRegValue0 is unsuccessful. 0x80070002.

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

What can I check to troubleshoot this ?

Hi All,

I have an issue trying to deploy a (already customised) WIN10 1903 wim image via MDT.

recently upgraded MDT v8456 (from 829?), replaced the boot images in WDS and restarted the server. ADK has also been updated for 1909

I have added the WIM to the Operating Systems (selected does not need system files).

Created a standard client TS and deployed to the client and got the following errors. (couldn't upload the entire content due to 4-60000 limit)

I have NOT edited the customsettings.ini since the upgrade.

Now I am getting prompted for the administrator password also. Have I missed something.

Could someone please confirm which Task Sequences need to be disabled if I just want to deploy the drivers and OS?

I have Windows ADK with the PE addition installed. The PE version is 10.x But I'm interested if I could choose to use WinPE 3.0 when creating the boot image in MDT. I'm concerned because some PC's have janky hardware and don't work with Windows 10. So if I'm using WinPE 10.x, the machine might not even boot to install Windows 7 from MDT.

Hi Everyone,

I am a script kiddie (I know literally next to nothing) when it comes to scripting.  I dont really understand cscript and I barely know enough to write simple power shell scripts.

I am trying to have a task sequence option similar to modifying the computer description during deployment.

However this time I need to modify the ManagedBy in AD.  This would add an AD group member to the "ManagedBy" field in Active Directory during the lite touch install for the current computer being imaged.

Can anyone help me getting this figured out.  I'm sure it's simple but I am struggling with it.

Deploying Win10 1809.  How can I hide the following folders for ALL user profiles, even if they log into someone else's system ?

I want to hide 3D Objects, Contacts, Music, Videos, Links and Saved Games.  Even when a new user logs into the system.

Deploying with MDT, image create in VMware.

Hi,

I'm using MDT 6.3.8456 and I am unable to process the TaskSequenceID from CustomSettings.ini as well as this, if I set the computer name during deployment it doesn't update during the installation wizard.

I've removed the gateway addresses, and other sensitive information. All works but my TaskSequenceID DEPLOY_SRV settings are ignored, and also my computer name doesn't update when manually changed in the deployment wizard, although MDT recognises the correct name when it's joined to the domain etc.

I've tried various steps including editing the DeployWiz_SelectTS.vbs, DeployWiz_Validation.vbs, adding extra "Gathers" in the MDT Task Sequence, and a 2nd ini with specific TaskSequenceID and settings. Below are my settings. Ive worked with MDT in the past, and I've this working on another deployment by updating the DeployWiz_Validation.vbs. This version MDT 6.3.8456 seems to have issues. My settings are below, all other settings are processed. If i remove the settings under Default, and place them under DEPLOY_SRV the are ignored, but if placed under Default they are processed.

Hi,

I have created a upgrade task sequence, which is working well and will successfully update a device to 1903. 

However I have a strange issue where I get the OOBE prompts when logging in to an upgraded machine post upgrade but only on the local admin account.

Is this normal, and if so any way to stop this from happening?

You can exit the OOBE by running task manager, it then seemingly doesn't ask again.

But if you try to complete the OOBE I just get the 'Something went wrong' message with OOBESETTINGSMULTIPAGE every time.

After having resolved most of my problems concerning system building / OS preinstallation using MDT, I still have issues when it comes to the sysprep part.

As mentioned above, can anyone explain me the difference between running "LTISysprep.wsf" vs. running a command line "sysprep.exe /generalize /oobe /quiet /quit /shutdown" in detail?

Though it has taken quite some time to figure out, I have realised that I need a second answer file (unattend.xml) for a correct OOBE experience. That second unattend.xml is specifically designed for the Sysprep process in order to deactivate the local Administrator as well as the AutoLogon behaviour (both needed by MDT during build process).

For this reason, I have to guide sysprep to that 2nd answer file. If I could incorporate the standard sysprep command, there wouldn't be any problem, as I would just add "/unattend:<Path-to-Unattend002.xml>" to the command.

When I run this sysprep command in MDT task sequence (regardless of specifying unattend-path or not), however, I always get an error and MDT deployment does not complete successfully; whereas the MDT default way of using "LTISysprep.wsf" will not result in any errors.

Does LTISysprep.wsf tell MDT when to finish deployment while command-line sysprep does not; thus leaving the MDT deployment wizard in an uncertain state?

If so, how would I be able to change LTISysprep.wsf to use a different, second unattend.xml for the Sysprep process? So far, LTISysprep.wsf uses the installation unattend.xml (generated by MDT & stored in the task sequence folder), even though I have copied the Sysprep-unattend.xml (file name: "unattend.xml" as it should be) to the directory "%SYSTEMROOT%\System32\Sysprep\" before.

I would greatly appreciate any thoughts on this!

Regards,

Keith

Hello there...

Quick question. For the convenience of my deployment folks, I would like to do the following:

_SMSTSOrgName=Acme IT - Deployment on %OSDComputerName%

I have a default OSDComputerName=PC-#Left("%SERIALNUMBER%",12)# but is usually changed by the deployment people to match the username.

Everything works fine except that _SMSTSOrgName=Acme IT - Deployment on %OSDComputerName% shows PC-#Left("%SERIALNUMBER%",12)# instead of the new name input in the wizard. Should I use another variable? I already tried %HostName% but it shows MININT-% which is worse.

Any ideas?

Thanks