MDT  wizard not  showing up or completing the task  after deployment, for this reason folders SMS,minint LTIbootstap are not deleting nor restoring user data

Hello, I'm setting up a new task sequence for deployment of a thin image of Windows 10 1803 on MDT Build 8450. I've ran the obstacle course of setting up silent installations of all of the applications and things and the future was looking bright. The final"new" step in my thin image task sequence was overwriting a pair of ini files in one of the application directories - trivial, I thought. That's when it's all went wrong. 

I've tried overwriting them through Powershell - "permission denied."

I've tried overwriting them via VBS - "permission denied." 

I've tried batch scripting - "permission denied"

I've attempted to take ownership of the files, delete them and then copy in the new ini files. "Permission denied!"

At that point I started trying all manner of existing scripted solutions made available by kind admins with as many variations as I could imagine. "Permission denied!"

I've even built a custom windows update CAB do perform the overwrite and attempted to import it into MDT - "not a valid windows update package."

I'm willing to read, I'm willing to eat humble pie. I'm willing to light candles around Deployment Fundamentals - Vol 6 and beg for a miracle. Does anyone have any suggestions as to how content in Program Files (x86) ought to be overwritten during deployment?

I rely need help here. I am trying to deploy windows 10 LTSC 2019 1807 with MDT on

HP Compaq Dc5750 Small Form Factor but i get a network error :( After that i manual install win 10 ltsc 2019 on the computer and update the driver and all, and it run perfekt. i backup all drivers and import it in MDT but again t get the same network error :( it start to install from network but ran in to error:

Is it missing winpe driver? and if yes where can i get it for dc5750?

HMM CANT POST PIC :)
Error massage:

A Connection to the deployment share //......
could not be made.
The following networking device did not have a driver installed.
pci ven_14e4&dev_167b&subsys_280a103c&rev_02

Retry: Try again to connect to the deployment share.....

Hope there is a fix on this?

Cheers

     Jimmy

If I embed WSUS in my TS, client pc's will get updates from the WSUS.

However, I recall reading somewhere that in the TS, you must add a registry change to prevent those clients from attempting to get updates from MDT once out in the field.

No computers around the state are able to contact WSUS or MDT except in our IT lab, so what changes need to be made during the end of the TS to stop clients from trying to hit MDT/WSUS and let them go back to MS Updates again?

We have an environment of about 35-40 Dell desktop and laptops, typically no more than 5 of any given model.  I have always manually set up and configured the operating system, using group policies to control some settings, but have never deployed using images. 

We are currently running Windows 7 and I need to update device drivers on most of our machines and was trying to determine if I could use MDT to update the drivers.  I am planning on using it to deploy Windows 10 later this year and will include drivers at that time, but would also need to keep those drivers updated after the initial deployment.  

Everything I am seeing references updating the image with new drivers for OS deployment, not necessarily updating drivers months after the OS has been deployed.  Is this a viable use for MDT and if so, can you point me to some documentation on how to accomplish the driver update without the OS deployment.

Any help is appreciated. 

Hi,

I've been seeing an error that I think is interrupting my in-place upgrade task sequence at the very end:

TsManager.exe - Entry Point Not Found

The procedure entry point GetWindowsDOClientSettings could not be located in the dynamic link library C:\Windows\CCM\lsutilities.dll

If I click OK, it lets the deployment finish. However, I think it may be at the root of why some of these deployments are stalling out at the end. There's a lot to parse out in the error and I couldn't find much related material when I google'd it. If anyone has any ideas of what I should check, please let me know. Thanks! -G

**EDIT #2** More troubleshooting...

Being that the error was referencing lsutilities.dll, which is located in C:\Windows\CCM, I went down that trail for a while. I found that the version of lsutilities.dll in that folder was older than MDT 8450/ADK 1803, and that my SCCM site was running 1802 without any of the 3 hotfixes that had been released. I installed those hotfixes in order and let ConfigMgr update the clients from version 5.00.8634.1010 to 5.00.8634.1814. That client update also updated lsutilities.dll, but the problem remains.

I have MDT integrated into SCCM, but at this point we're only using MDT for OSD. There are a few OSD items added, but no task sequences and the DP isn't enabled for PXE. I noticed that the boot image in SCCM has a client version associated with it. Though I'm not deploying OSD via SCCM, is there something I should be doing with MDT (reminder, this is only a concern for in-place upgrades) to make sure clients can find a lsutilities.dll file that they agree with when they finish upgrading to 1803?

EDIT: A little bit closer on this now. Still following leads from smsts.log. Here's the block that interests me at the end of smsts.log. Red errors are in bold, yellow warnings in italics:

****************************************************************************
Execution engine result code: Success (0)
Cleaning Up.
Removing Authenticator
Cleaning up task sequence folder

Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.
Failed to delete directory 'C:\_SMSTaskSequence'
SetNamedSecurityInfo() failed.
SetObjectOwner() failed. 0x80070005.
RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.
RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence

Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...
Successfully unregistered Task Sequencing Environment COM Interface.
Executing command line: "C:\MININT\Tools\X64\TsProgressUI.exe" /Unregister
==========[ TsProgressUI started in process 7100 ]==========
Unregistering COM classes
Shutdown complete.
Process completed with exit code 0
Successfully unregistered TS Progress UI.
Sending success status message
In non SMS staqndalone mode.Ignoring SendStatusMessage request

RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram
GetTsRegValue() is unsuccessful. 0x80070002.

End program:
LOGGING: Setting log directory to "C:\Windows\CCM\Logs".
Process completed with exit code 0
Exiting with return code 0x00000000
==========[ TsProgressUI started in process 7044 ]==========
Unregistering COM classes
Shutdown complete.

With the update for MDT 8456 released, I can no longer find a download link for build 8450.  I am using an orchestration product that has not yet been updated to support build 8456, and need 8450.  Is there a direct download link available for build 8450 somewhere?

I much appreciate any help.

Hey there,

the title descibes it all.

After every Deploy, the system logs on in the built in Administrator Account automatically.

Even I placed a command Line as the last step in Post Install Task Sequence with:

cmd /c net user Administrator /active:no

That does not work either.

The reason: I prepare notebooks for schools. No Domain just Workgroup. There should be no built in admin visible at logon screen just the Teachers Admin and the childrens User.

Thank you for your help!

MY MAIN DESKTOP HAS AN ISSUE. THIS IS EVER SINCE I PUT 1809 ON IT. AT AUTO LOGON IT WIL STOP AT PRE-OS WITH A SCREEN THAT STATES "SOME MANY ATONOMUS LOGIN"" SOLAH, BALH, BLA MANY UNSUCESSFUL AUTO LOGIN, BLGH?AGH, BLAGH AND BLAGH. THE PURPOSE OF THE AUTO LOGINS IS TO HAVE THIS MACHINE UP AND RUNNING AND THIS SCREEN STOPS THE PROCCESS! hUH? cAN YOU HELP?      

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,

Problem: MDT doesn't inject the drivers automatically during the build process.

Setup: I have a dedicated build network (server and building devices only), so there is minimum traffic and it. Server is running Windows 2012R2 (WDS+MDT). I have a few task sequences, that work fine, but I'm having issues creating a task sequence for Dell Venue 11 Pro 5130 (Windows 8.1 x64).

Interesting bit: If I try to install devices manually and select deployment share as a source, all drivers are found and installed. Which makes me think injected drivers are correct.

What was tested:

1. I thought it could be affected by other task sequences, so I have created a new deployment share which contains only Windows 8.1 x64 and drivers from Dell site for 5130 (.cab package). No changes.

2. I have disabled original (ZTI script) Inject driver step in post-install stage and replaced it with same step as in pre-install stage (select profile one). No changes.

3. I have tried creating selection of drivers and trying to install that profile, then I tried to install "All drivers" profile. Next step was to install all drivers (not only compatible). Still no luck.

The only idea I have left is to use pnputil, but I would like to avoid it.

Any advises, suggestions are welcome.

Hi,

I use MDT 6.3.8450.1000 the latest version I can find. Just for testing I added Server 2019 1809. I was testing to capture a image. I kicked of an TS after boot, and the OS was installed, but I was end up with the MDT "Task Sequence" again inside the deployed Server 2019.

So I have not find anything about a new MDT for Server 2019 1809 support? 

/SaiTech

When trying to create a Task Sequence in MDT to Install a Windows 2019 feature, Windows 2019 server is not listed in drop down menu.  Has anyone encountered this problem?

I have installed the latest ADK v10.1.17763.1

Does MDT 6.3.8450.1000 support Windows 2019 roles and features deployments?

Thanks

Hi all.

I have updated my ADK on my MDT to 1809 (along with the new Windows PE Addon).  When I go to update my deployment share, I receive an error that access to the path is denied.  I have verified the permissions to the path and I can access it.  I also tried opening Deployment Workbench as administrator but I get the same error.  This should be a simple fix... Any ideas?  Here is the log:

=== Making sure the deployment share has the latest x86 tools ===

=== Processing LiteTouchPE (x86) boot image ===

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x86 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim will be used.
WIM file mounted.
Set Windows PE system root.
Set Windows PE scratch space.
Added component winpe-hta
Added component winpe-scripting
Added component winpe-wmi
Added component winpe-securestartup
Added component winpe-fmapi
Added component winpe-dismcmdlets
Added component winpe-mdac
Added component winpe-netfx
Added component winpe-powershell
Added component dart8
Injected driver Microsoft Corporation System wstorflt.inf 6.1.7601.17514 (1)
Injected driver Microsoft Display wvmbusvideo.inf 6.1.7601.17514 (1)
Injected driver Microsoft HIDClass wvmbushid.inf 6.1.7601.17514 (1)
Injected driver Microsoft Net wnetvsc.inf 6.1.7601.17514 (1)
Injected driver Microsoft System wdmvsc.inf 6.1.7601.17514 (1)
Injected driver Microsoft System ws3cap.inf 6.1.7601.17514 (1)
Injected driver Microsoft System wvmbus.inf 6.1.7601.17514 (1)
Injected driver Microsoft System wvmic.inf 6.1.7601.17514 (1)
Injected driver Microsoft. SCSIAdapter wstorvsc.inf 6.1.7601.17514 (1)
Injected driver VMware, Inc. Display vm3d.inf 8.15.01.0033
Injected driver VMware, Inc. Display vmx_svga.inf 12.01.08.0000
Injected driver VMware, Inc. Net vmxnet3ndis5.inf 1.5.2.0
Injected driver VMware, Inc. Net vmxnet3ndis6.inf 1.6.7.0
Copy: \\SRV-DTMG-01\mdtbuild$\Control\Bootstrap.ini to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Bootstrap.ini
Copy: C:\Program Files\Microsoft Deployment Toolkit\Templates\Unattend_PE_x86.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Unattend.xml
Copy: C:\Program Files\Microsoft Deployment Toolkit\Templates\winpeshl.ini to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Windows\system32\winpeshl.ini
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\LiteTouch.wsf to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\LiteTouch.wsf
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTIUtility.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTIUtility.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTIBCDUtility.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTIBCDUtility.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTIDiskUtility.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTIDiskUtility.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTIDataAccess.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTIDataAccess.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTIConfigFile.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTIConfigFile.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTIGather.wsf to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTIGather.wsf
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTIGather.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTIGather.xml
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\Wizard.hta to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Wizard.hta
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\Credentials_ENU.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Credentials_ENU.xml
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\Credentials_scripts.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Credentials_scripts.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WizUtility.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WizUtility.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\Wizard.css to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Wizard.css
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\Wizard.ico to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Wizard.ico
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\BackButton.jpg to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\BackButton.jpg
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\plusicon.gif to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\plusicon.gif
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\minusico.gif to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\minusico.gif
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\Summary_Definition_ENU.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Summary_Definition_ENU.xml
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\Summary_scripts.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Summary_scripts.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\LTICleanup.wsf to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\LTICleanup.wsf
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\BDD_Welcome_ENU.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\BDD_Welcome_ENU.xml
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WelcomeWiz_Choice.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WelcomeWiz_Choice.xml
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WelcomeWiz_Choice.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WelcomeWiz_Choice.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WelcomeWiz_DeployRoot.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WelcomeWiz_DeployRoot.xml
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WelcomeWiz_DeployRoot.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WelcomeWiz_DeployRoot.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WelcomeWiz_Initialize.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WelcomeWiz_Initialize.xml
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WelcomeWiz_Initialize.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WelcomeWiz_Initialize.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\SelectItem.jpg to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\SelectItem.jpg
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WelcomeBanner.jpg to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WelcomeBanner.jpg
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\btnout.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\btnout.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\btnover.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\btnover.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\btnsel.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\btnsel.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\LTIGetFolder.wsf to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\LTIGetFolder.wsf
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\NICSettings_Definition_ENU.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\NICSettings_Definition_ENU.xml
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTINicUtility.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTINicUtility.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTINicConfig.wsf to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTINicConfig.wsf
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\BackButton.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\BackButton.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\FolderIcon.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\FolderIcon.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ItemIcon1.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ItemIcon1.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\MinusIcon1.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\MinusIcon1.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\PlusIcon1.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\PlusIcon1.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\SelectItem.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\SelectItem.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\header-image.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\header-image.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\NavBar.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\NavBar.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\Computer.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Computer.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WelcomeWiz_Background.jpg to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WelcomeWiz_Background.jpg
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\DeployWiz_Administrator.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\DeployWiz_Administrator.png
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\BDDRUN.exe to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Windows\system32\BDDRUN.exe
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\WinRERUN.exe to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\WinRERUN.exe
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\CcmCore.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\CcmCore.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\CcmUtilLib.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\CcmUtilLib.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\Smsboot.exe to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\Smsboot.exe
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\SmsCore.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\SmsCore.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\TsCore.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\TsCore.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\TSEnv.exe to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\TSEnv.exe
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\TsManager.exe to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\TsManager.exe
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\TsmBootstrap.exe to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\TsmBootstrap.exe
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\TsMessaging.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\TsMessaging.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\TsmBootstrap.exe to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\TsmBootstrap.exe
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\TsProgressUI.exe to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\TsProgressUI.exe
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\TSResNlc.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\TSResNlc.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\CommonUtils.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\CommonUtils.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\ccmgencert.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\ccmgencert.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\msvcp120.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\msvcp120.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\msvcr120.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\msvcr120.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\00000409\tsres.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\00000409\tsres.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\Microsoft.BDD.Utility.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\Microsoft.BDD.Utility.dll
Copying WIM to the deployment share.
Creating an ISO.
Copying ISO to the deployment share.

System.Management.Automation.CmdletInvocationException: Access to the path '\\SRV-DTMG-01\mdtbuild$\Boot\ImageBuildLiteTouchPE_x86.iso' is denied. ---> System.UnauthorizedAccessException: Access to the path '\\SRV-DTMG-01\mdtbuild$\Boot\ImageBuildLiteTouchPE_x86.iso' is denied.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.Delete(String path)
   at Microsoft.BDD.Core.DirectoryUtility.CopyFile(DEInfo sourceFile, DEInfo destFile, String destFullName)
   at Microsoft.BDD.Core.DirectoryUtility.BeginCopyFile(String theSourceFile, String theDestFile)
   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName)
   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

Hi all,

i have issues with the post application windows update task sequence.

While os deployment instantly after searching for updates the deployment failed.

I created a new custom task sequence for testing and copied the post application windows updates in there.

I´m using a shared wsus, with https and target groups

I remember in my old company where i worked, i set up mdt with wsus and there it worked just fine. Wsus was there http not https don’t know if that might be the problem.

I followed this:

https://www.peppercrew.nl/index.php/2015/10/add-wsus-target-group-option-to-mdt-deployments-2/ 

used Method 2

When i look in regedit HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate wsus and the right target group are in there, still the task sequence didnt work.

When i do the windows updates normal over settings everything is working.

Does someone had experienced same issues or does anybody have a tip for me?

Any help much appreciated.

I uploaded the logs 

https://uploadfiles.io/oi7hv 

I would like to set the value of a property when I either update the deployment share or create the media.  It doesn't really matter which time.  I understand I can define the property in the CustomSettings.ini or bootstrap.ini file and that it should be accessible as a global property.  And I've seen many examples of updating the values of properties during deployment.  But this is not what I want.

I want to keep track of an actual build run and increment it every time I update the deployment share.  I'm not sure if there is already a property that has this info but so far I have not found anything.

1) Is there a build property that already exists?

2) How can I automate updating a property at build time, not deployment time?

Hello,

i am using the latest version of MDT.

I have in my task-sequence overview folders and task-sequences.

Now i want a specific task-sequence on TOP of the list above all other folders and Task-sequences.

I have tried this in tasksequences.xml and tasksequencgroups.xml without result.

Anybody know how to achieve this?

Thx

The media deployment point WIM splitting functionality does not seem to be working in MDT 2013 Update 2. Although I have been unable to find official documentation or guidance on the functionality, I have gathered from various posts here and elsewhere that these are the requirements:

1. SkipWIMSplit should be set to "False" in Settings.xml
2. The operating system (WIM) and corresponding deployment task sequence should be included in the selection profile used for the media deployment point
3. The operating system (WIM) should be 4GB+ in size

All of these requirements have been met in my environment but when I update media, the 10GB WIM is not recognized as 4GB+ and is not split. I have prepared a "vanilla" environment (Server 2012 R2, WAIK 1511, MDT 2013 Update 2, zero customizations or changes to defaults) to work on this issue but still no success.

Anyone out there have this working? If so, what have you implemented in addition to the three items above.

Finally, where is the documentation for this?

Thanks in advance for any help or guidance. 

Hello guys,

I need to install RSAT Tools ( Remote Server Administration Tools ) with MDT Via Rols.

Just the Admin PC-s sholud have the tool...

And in the Deployment Workbranche under Database - Roles i created Admin Folder for admin pc-s.

The RSAT is in the Deployment Share Applications.

( The RSAT toos are a .cab file "update" KB2693643 and they are installed with a command " DISM.exe /Online /Add-Package /PackagePath: C:\Temp\WindowsTH-KB2693643-x64.cab /quiet"

Just this app cant be installed on the PC, all other admin tools and apps added via roles are there ...
Can someone help me please ?