Hi,

I'm trying to set  up custom computer naming dependent on user locale that is chosen during deployment.

I know there is userexit script to be used but I'm not sure whether it can cope with what I want it to do.

My cs.ini looks like that:

SkipLocaleSelection=NO
UserExit=NewHostname.vbs
OSDComputerName=#NewHostname("%KeyboardLocale%","%IsLaptop%","%IsDesktop%","%SerialNumber%")#

newHostname.vbs:

Function UserExit(sType, sWhen, sDetail, bSkip)
  UserExit = Success
End Function
Function NewHostname(sKBLang,sLaptop,sDesktop,sSerialNo)
  Dim strLastTwo, strLastSix, strChassis
  strLastTwo = Right(sKBlang, 2)
  strLastSix - Right(sSerialNo, 6)
 
  If sLaptop = "TRUE" then
  strChassis = "LT"
  else if sDesktop = "TRUE" then
  strChassis = "DT"
  end if
 
  NewHostname = strLastTwo & "-" & strChassis & "-" & strLastSix
End Function

I know it doesn't have a failsafe for a situation when sytsem is deployed on server but that won't happen ever.

Can you tell me if that script has chance of working or what needs to be changed? Thanks.

Hi colleagues,

I found strange issue with MDT 2013

I'm trying to deploy previosly captured image (KB2998527 has been installed in captured system)

When I'm select any time zone except Russia Time Zones (RTZ) in dropdown list, after deploying all works fine and I see correct TimeZone.

In case if I select any RTZ, after install Time Zone setup as -8.

I debug process and found, that in TIMEZONENAME variable exists "Russia TZ9 Standard time" (for example). and in tzutil I don't see such TZ Name.

As a workaround I txt file in image with links between correct TZ names and Russia TZX Standard Time and by tzutil I setup needed timezone after installation

But, could you please fix it next update for MDT 2013?

Thanks in advance

Hi 

Iam trying to integrate web service with MDT, which helps in opening the webpage, keyin the computer name and type of installation and service tag.

How do i setup web server that integrates with MDT on windows 2008 R2 server?  

Thanks

Venky

Hi,

I am using the LIT OEM task sequence.  By default there is a Format and Partition Disk step.  It currently sets up MBR with 100pct of disk.  I wanted to use the other Format and Partition which detects UEFI/BIOS.   I select the OEM task and all appears to work, it shuts down.   When I power up, I get a "Dirty Environment" message.  I've tried diskpart/clean and then restart the processes.  Still get that message.  If I click, "Continue", it will but the fails with "ZTI ERROR-unhandled error returned by ZTIDRIVERS:  Path not found 76.

If i use the default "Format and Partition", the image process finishes fine.

Any ideas?

thx
Paul

I'm using a VirtualBox VM to pilot some changes and I've run into an unusual problem that only seems to affect VirtualBox VM's.  Other machines (VMware VM's, Hyper-V VM's and physical) work fine no matter which setting for the Install OS step.

I discovered that the Install OS step in the TS was set to 'Specific disk and partition Disk 0 Partition 1', for whatever reason, and didn't change it because things were working.  (This is a new organization)  When its setup like this, the VirtualBox VM fails with "Failure ( 5456 ): Unable to determine Destination Disk, Partition and/or Drive. See BDD.LOG for more information."  In the BDD, right above that line it says "DestinationDisk and Partition did not yield a target Partition."

Curious, when I check `diskpart > lis dis` it says "There are no fixed disks to show."  I double checked the VM config & tried again.  As soon as I was in PE I checked diskpart and it shows disk 0 with 45GB free.  Good. Select the TS, it begins then fails again with the same error.  I go back into diskpart and the disk is missing. ??

I change the Install Os step to 'Logical drive letter stored in a variable', set the variable to 'OSDisk'.  I then checked the properties of the Partition under 'Format and Partition' and manually entered 'OSDisk' as the variable since the field was empty.  The rest of the properties look normal: Primary partition, 100%, make this a boot partition, NTFS file system, quick format.


One more try: Boot the VM, check the disks (OK), select the TS stalls on 'Format and Partition Disk Preparing Disk 0 Partitions ...'.  I open BDD and I see several lines that read "Waiting for Drive to Exist: X%"  Finally it fails with "ZTI ERROR - Unhandled error returned by ZTIDiskpart: Object Required (424)".  I check the disks again and its missing.  What the heck?

I created a brand new standard client TS, made zero customizations to it, & tried both the WIM we're deploying and a stock Win7 WIM but they both fail with the Object required error. 

I have read articles that talk about how you can use ZTIWindowsUpdate.wsf outside of using SCCM/MDT.

We would like to use it to Automate Windows Updates on some of our servers.

The issue we are running into is how do you pass the variables to it if your not use a TS? 
We need to pass the variable of the WSUSServer to it.

I have ZTIUtility.vbs and ZTIWindowsUpdate.wsf in the same folder.
What i have tried:
- placing a CustomSettings.ini in the same folder
- Batch file with variables

Any help would be appreciated.

Justin Cochran

I am doing a build and capture of Windows 10 using MDT 2013u2.

Windows 10 clients both during the build process and after being deployed are asking "Do you want to allow your PC to be discoverable?"  I thought this question was controlled by the NetworkLocation setting in OOBE Unattend.xml.  That value is set to "Work" - but I am still being asked the question about discoverability.  When I deploy the OS using a Task Sequence, I also get this question.  This is not the kind of question my users know how to answer. 

Is there a way to set this value in unattend.xml?  Has networklocation been depreciated?

I'm currently running MDT 2013 Update 1 on a Windows 2012 R2 with WDS. I imported the OS files, drivers for Surface and created Task Sequence. I boot Surface Pro 3 into PXE and select my task and all works fine, it even loads the OS but when it tries to capture the image as the second phase it always fails with "Expected image state is Image_State_Generalize_Reseal_to_OOBE, actual image state is Image_State_Complete, sysprep did not succeed. Failure 6192, Litetouch deployment failed, return code = -2147467259 0x80004005"

I try capturing the image using a Sysprep and capture, connected to Deployment share and ran LiteTouch.vbs and wizard comes up and it starts to run thru the task but it fails in the same error. Driving me nuts and not sure why it's happening. I need to complete this image ASAP and I'm wondering if I'm hitting a MDT 2013 bug.

thanks in advance. 

Hi,

I have ported a deployment share from MDT 2013 Update 1 to Update 2.  The same installation works fine with MDT 2013 Update 1 USB Media.  With MDT 2013 Update 2 the installation from hang at

Running Action: Install Operating System

100%

From the BDD.log or LTIApply.log

Copy File: C:\MININT\unattend.xml to V:\Windows\Panther\Unattend.xml
LTIApply2016-08-17 16:33:28
0 (0x0000)
Copied unattend.xml to V:\Windows\Panther for image apply.
LTIApply2016-08-17 16:33:28
0 (0x0000)
About to run command: dism.exe /Image:V:\ /Apply-Unattend:V:\Windows\Panther\Unattend.xml /ScratchDir:C:\MININT\Scratch
LTIApply2016-08-17 16:33:28
0 (0x0000)
Command has been started (process ID 340)LTIApply
2016-08-17 16:33:280 (0x0000)
  Console > Deployment Image Servicing and Management tool
LTIApply2016-08-17 16:33:29
0 (0x0000)
  Console > Version: 10.0.10586.0LTIApply
2016-08-17 16:33:290 (0x0000)
  Console > Image Version: 6.1.7601.17514 LTIApply2016-08-17 16:33:37
0 (0x0000)
  Console > 
[                           0.1%                           ]LTIApply 2016-08-17 16:34:120 (0x0000)
ZTI Heartbeat: command has been running for 1 minutes (process ID 340)
LTIApply2016-08-17 16:34:12
0 (0x0000)
  Console > 
[                           1.1%                           ]LTIApply 2016-08-17 16:34:120 (0x0000)
  Console > 
[=                          2.0%                           ]LTIApply 2016-08-17 16:34:120 (0x0000)
  Console > 
[=                          3.0%                           ]LTIApply 2016-08-17 16:34:120 (0x0000)
  Console > 
[==                         4.0%                           ]LTIApply 2016-08-17 16:34:120 (0x0000)
  Console > 
[==                         4.9%                           ]LTIApply 2016-08-17 16:34:120 (0x0000)
  Console > 
[===                        5.9%                           ]LTIApply 2016-08-17 16:34:120 (0x0000)
  Console > 
[===                        6.8%                           ]LTIApply 2016-08-17 16:34:120 (0x0000)
  Console > 
[====                       7.8%                           ]LTIApply 2016-08-17 16:34:120 (0x0000)
  Console > 
[=====                      8.7%                           ]LTIApply 2016-08-17 16:34:120 (0x0000)
  Console > 
[=====                      9.7%                           ]LTIApply 2016-08-17 16:34:120 (0x0000)
  Console > 
[======                     10.6%                          ]LTIApply 2016-08-17 16:34:120 (0x0000)
  Console > 
[======                     11.6%                          ]LTIApply 2016-08-17 16:34:120 (0x0000)
  Console > 
[=======                    12.6%                          ]LTIApply 2016-08-17 16:34:120 (0x0000)
  Console > 
[=======                    13.5%                          ]LTIApply 2016-08-17 16:34:120 (0x0000)

  Console > 
[===========================92.8%=====================     ] LTIApply2016-08-17 16:34:400 (0x0000)
  Console > 
[===========================93.7%======================    ] LTIApply2016-08-17 16:34:410 (0x0000)
  Console > 
[===========================94.7%======================    ] LTIApply2016-08-17 16:34:410 (0x0000)
  Console > 
[===========================95.6%=======================   ] LTIApply2016-08-17 16:34:410 (0x0000)
  Console > 
[===========================96.6%========================  ] LTIApply2016-08-17 16:34:410 (0x0000)
  Console > 
[===========================97.5%========================  ] LTIApply2016-08-17 16:34:410 (0x0000)
  Console > 
[===========================98.5%========================= ] LTIApply2016-08-17 16:34:410 (0x0000)
  Console > 
[===========================99.5%========================= ] LTIApply2016-08-17 16:34:410 (0x0000)
  Console > 
[===========================99.9%========================= ] LTIApply2016-08-17 16:34:410 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:410 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:410 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:410 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:410 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:410 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:410 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:410 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:410 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:420 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:420 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:420 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:420 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:420 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:420 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:420 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:420 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:420 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:420 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:420 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:420 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:420 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply2016-08-17 16:34:420 (0x0000)

The Windows 7 image is x64 and the WinPE is x86.

Thank You

Hi,

I'm actually creating and unattended xml file for Sysprep, that help me to set computer name when sysprep is loading and then join the machine to the domain.

    According with documentation and posts about the subject, In WSIM I deleted the line <ComputerName></ComputerName> and left it blank too. I did the two steps separately but unfortunately it doesn't works always the computername is set dynamically and the machine isn't join to domain stills in the default WORKGROUP.
    Static IP Address and Primary DNS Server Configuration works (ping to domain works).

Unattend XML File:

<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"><settings pass="windowsPE"><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>en-US</InputLocale><SystemLocale>en-US</SystemLocale><UILanguage>en-US</UILanguage><UserLocale>en-US</UserLocale></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" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><OOBE><HideEULAPage>true</HideEULAPage></OOBE><UserAccounts><AdministratorPassword><Value>QwBvAGwAbwBtAGIAaQBhADIAMAAxADYAKgBBAGQAbQBpAG4AaQBzAHQAcgBhAHQAbwByAFAAYQBzAHMAdwBvAHIAZAA=</Value><PlainText>false</PlainText></AdministratorPassword></UserAccounts></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" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><Identification><Credentials><Domain>mydomain.local</Domain><Password>Administrator</Password><Username>Password#</Username></Credentials><JoinDomain>mydomain.local</JoinDomain></Identification></component><component name="Microsoft-Windows-TCPIP" 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"><Interfaces><Interface wcm:action="add"><Ipv4Settings><DhcpEnabled>false</DhcpEnabled><Metric>10</Metric><RouterDiscoveryEnabled>false</RouterDiscoveryEnabled></Ipv4Settings><UnicastIpAddresses><IpAddress wcm:action="add" wcm:keyValue="1">192.168.10.253/24</IpAddress></UnicastIpAddresses><Identifier>Ethernet</Identifier></Interface></Interfaces></component><component name="Microsoft-Windows-DNS-Client" 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"><Interfaces><Interface wcm:action="add"><DNSServerSearchOrder><IpAddress wcm:action="add" wcm:keyValue="1">192.168.10.1</IpAddress></DNSServerSearchOrder><DNSDomain>mydomain.local</DNSDomain><EnableAdapterDomainNameRegistration>true</EnableAdapterDomainNameRegistration><DisableDynamicUpdate>false</DisableDynamicUpdate><Identifier>Ethernet</Identifier></Interface></Interfaces></component><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"><RegisteredOwner>Admin</RegisteredOwner></component></settings><cpi:offlineImage cpi:source="wim:e:/install.wim#Windows Server 2012 R2 SERVERSTANDARD" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>

I have created a brand new MDT server with the new MDT 2013 Update 1 and Windows 10 ADK and I tried making the most simple possible deployment standard client task and importing a Windows 7 Enterprise evaluation ISO.

The MDT Server is a Server 2012 R2 VM running on Server 2012 R2 Hyper-V.

I created the deployment share, imported the operating system, created a basic deployment task and then tried to update the deployment share so it can create boot images.

This failed from the beginning.

These are the errors  I see:

=== 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-mdac
Copy: C:\Deployment1\Control\Bootstrap.ini to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Bootstrap.ini
Copy: C:\Program Files\Microsoft Deployment Toolkit\Templates\Unattend_PE_x86.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Unattend.xml
Copy: C:\Program Files\Microsoft Deployment Toolkit\Templates\winpeshl.ini to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Windows\system32\winpeshl.ini
Copy: C:\Deployment1\Scripts\LiteTouch.wsf to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\LiteTouch.wsf
Copy: C:\Deployment1\Scripts\ZTIUtility.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTIUtility.vbs
Copy: C:\Deployment1\Scripts\ZTIBCDUtility.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTIBCDUtility.vbs
Copy: C:\Deployment1\Scripts\ZTIDiskUtility.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTIDiskUtility.vbs
Copy: C:\Deployment1\Scripts\ZTIDataAccess.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTIDataAccess.vbs
Copy: C:\Deployment1\Scripts\ZTIConfigFile.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTIConfigFile.vbs
Copy: C:\Deployment1\Scripts\ZTIGather.wsf to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTIGather.wsf
Copy: C:\Deployment1\Scripts\ZTIGather.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTIGather.xml
Copy: C:\Deployment1\Scripts\Wizard.hta to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Wizard.hta
Copy: C:\Deployment1\Scripts\Credentials_ENU.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Credentials_ENU.xml
Copy: C:\Deployment1\Scripts\Credentials_scripts.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Credentials_scripts.vbs
Copy: C:\Deployment1\Scripts\WizUtility.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WizUtility.vbs
Copy: C:\Deployment1\Scripts\Wizard.css to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Wizard.css
Copy: C:\Deployment1\Scripts\Wizard.ico to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Wizard.ico
Copy: C:\Deployment1\Scripts\BackButton.jpg to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\BackButton.jpg
Copy: C:\Deployment1\Scripts\plusicon.gif to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\plusicon.gif
Copy: C:\Deployment1\Scripts\minusico.gif to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\minusico.gif
Copy: C:\Deployment1\Scripts\Summary_Definition_ENU.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Summary_Definition_ENU.xml
Copy: C:\Deployment1\Scripts\Summary_scripts.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Summary_scripts.vbs
Copy: C:\Deployment1\Scripts\LTICleanup.wsf to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\LTICleanup.wsf
Copy: C:\Deployment1\Scripts\BDD_Welcome_ENU.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\BDD_Welcome_ENU.xml
Copy: C:\Deployment1\Scripts\WelcomeWiz_Choice.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WelcomeWiz_Choice.xml
Copy: C:\Deployment1\Scripts\WelcomeWiz_Choice.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WelcomeWiz_Choice.vbs
Copy: C:\Deployment1\Scripts\WelcomeWiz_DeployRoot.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WelcomeWiz_DeployRoot.xml
Copy: C:\Deployment1\Scripts\WelcomeWiz_DeployRoot.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WelcomeWiz_DeployRoot.vbs
Copy: C:\Deployment1\Scripts\WelcomeWiz_Initialize.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WelcomeWiz_Initialize.xml
Copy: C:\Deployment1\Scripts\WelcomeWiz_Initialize.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WelcomeWiz_Initialize.vbs
Copy: C:\Deployment1\Scripts\SelectItem.jpg to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\SelectItem.jpg
Copy: C:\Deployment1\Scripts\WelcomeBanner.jpg to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WelcomeBanner.jpg
Copy: C:\Deployment1\Scripts\btnout.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\btnout.png
Copy: C:\Deployment1\Scripts\btnover.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\btnover.png
Copy: C:\Deployment1\Scripts\btnsel.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\btnsel.png
Copy: C:\Deployment1\Scripts\LTIGetFolder.wsf to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\LTIGetFolder.wsf
Copy: C:\Deployment1\Scripts\NICSettings_Definition_ENU.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\NICSettings_Definition_ENU.xml
Copy: C:\Deployment1\Scripts\ZTINicUtility.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTINicUtility.vbs
Copy: C:\Deployment1\Scripts\ZTINicConfig.wsf to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTINicConfig.wsf
Copy: C:\Deployment1\Scripts\BackButton.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\BackButton.png
Copy: C:\Deployment1\Scripts\FolderIcon.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\FolderIcon.png
Copy: C:\Deployment1\Scripts\ItemIcon1.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ItemIcon1.png
Copy: C:\Deployment1\Scripts\MinusIcon1.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\MinusIcon1.png
Copy: C:\Deployment1\Scripts\PlusIcon1.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\PlusIcon1.png
Copy: C:\Deployment1\Scripts\SelectItem.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\SelectItem.png
Copy: C:\Deployment1\Scripts\header-image.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\header-image.png
Copy: C:\Deployment1\Scripts\NavBar.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\NavBar.png
Copy: C:\Deployment1\Scripts\Computer.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Computer.png
Copy: C:\Deployment1\Scripts\WelcomeWiz_Background.jpg to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WelcomeWiz_Background.jpg
Copy: C:\Deployment1\Scripts\DeployWiz_Administrator.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\DeployWiz_Administrator.png
Copy: C:\Deployment1\Tools\x86\BDDRUN.exe to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Windows\system32\BDDRUN.exe
Copy: C:\Deployment1\Tools\x86\WinRERUN.exe to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\WinRERUN.exe
Copy: C:\Deployment1\Tools\x86\CcmCore.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\CcmCore.dll
Copy: C:\Deployment1\Tools\x86\CcmUtilLib.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\CcmUtilLib.dll
Copy: C:\Deployment1\Tools\x86\Smsboot.exe to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\Smsboot.exe
Copy: C:\Deployment1\Tools\x86\SmsCore.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\SmsCore.dll
Copy: C:\Deployment1\Tools\x86\TsCore.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\TsCore.dll
Copy: C:\Deployment1\Tools\x86\TSEnv.exe to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\TSEnv.exe
Copy: C:\Deployment1\Tools\x86\TsManager.exe to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\TsManager.exe
Copy: C:\Deployment1\Tools\x86\TsmBootstrap.exe to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\TsmBootstrap.exe
Copy: C:\Deployment1\Tools\x86\TsMessaging.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\TsMessaging.dll
Copy: C:\Deployment1\Tools\x86\TsmBootstrap.exe to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\TsmBootstrap.exe
Copy: C:\Deployment1\Tools\x86\TsProgressUI.exe to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\TsProgressUI.exe
Copy: C:\Deployment1\Tools\x86\TSResNlc.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\TSResNlc.dll
Copy: C:\Deployment1\Tools\x86\CommonUtils.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\CommonUtils.dll
Copy: C:\Deployment1\Tools\x86\ccmgencert.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\ccmgencert.dll
Copy: C:\Deployment1\Tools\x86\msvcp120.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\msvcp120.dll
Copy: C:\Deployment1\Tools\x86\msvcr120.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\msvcr120.dll
Copy: C:\Deployment1\Tools\x86\00000409\tsres.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\00000409\tsres.dll
Copy: C:\Deployment1\Tools\x86\Microsoft.BDD.Utility.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x86\Microsoft.BDD.Utility.dll
Copy: C:\Program Files\Microsoft Deployment Toolkit\Samples\Background.bmp to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Windows\system32\winpe.bmp
Copying WIM to the deployment share.
Creating an ISO.
Copying ISO to the deployment share.

=== Completed processing platform x86 ===

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

=== Processing LiteTouchPE (x64) 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 x64 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\amd64\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

Deployment Image Servicing and Management tool
Version: 10.0.10240.16384

Image Version: 10.0.10240.16384

Processing 1 of 1 - Adding package WinPE-MDAC-Package~31bf3856ad364e35~amd64~~10.0.10240.16384

Error: 1726

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

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

Exit code = 1726

DISM /Add-Package failed for component C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\winpe-mdac.cab, rc = 1726.
Added component winpe-mdac
Copy: C:\Deployment1\Control\Bootstrap.ini to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Bootstrap.ini
Copy: C:\Program Files\Microsoft Deployment Toolkit\Templates\Unattend_PE_x64.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Unattend.xml
Copy: C:\Program Files\Microsoft Deployment Toolkit\Templates\winpeshl.ini to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Windows\system32\winpeshl.ini
Copy: C:\Deployment1\Scripts\LiteTouch.wsf to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\LiteTouch.wsf
Copy: C:\Deployment1\Scripts\ZTIUtility.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTIUtility.vbs
Copy: C:\Deployment1\Scripts\ZTIBCDUtility.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTIBCDUtility.vbs
Copy: C:\Deployment1\Scripts\ZTIDiskUtility.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTIDiskUtility.vbs
Copy: C:\Deployment1\Scripts\ZTIDataAccess.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTIDataAccess.vbs
Copy: C:\Deployment1\Scripts\ZTIConfigFile.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTIConfigFile.vbs
Copy: C:\Deployment1\Scripts\ZTIGather.wsf to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTIGather.wsf
Copy: C:\Deployment1\Scripts\ZTIGather.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTIGather.xml
Copy: C:\Deployment1\Scripts\Wizard.hta to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Wizard.hta
Copy: C:\Deployment1\Scripts\Credentials_ENU.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Credentials_ENU.xml
Copy: C:\Deployment1\Scripts\Credentials_scripts.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Credentials_scripts.vbs
Copy: C:\Deployment1\Scripts\WizUtility.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WizUtility.vbs
Copy: C:\Deployment1\Scripts\Wizard.css to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Wizard.css
Copy: C:\Deployment1\Scripts\Wizard.ico to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Wizard.ico
Copy: C:\Deployment1\Scripts\BackButton.jpg to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\BackButton.jpg
Copy: C:\Deployment1\Scripts\plusicon.gif to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\plusicon.gif
Copy: C:\Deployment1\Scripts\minusico.gif to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\minusico.gif
Copy: C:\Deployment1\Scripts\Summary_Definition_ENU.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Summary_Definition_ENU.xml
Copy: C:\Deployment1\Scripts\Summary_scripts.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Summary_scripts.vbs
Copy: C:\Deployment1\Scripts\LTICleanup.wsf to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\LTICleanup.wsf
Copy: C:\Deployment1\Scripts\BDD_Welcome_ENU.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\BDD_Welcome_ENU.xml
Copy: C:\Deployment1\Scripts\WelcomeWiz_Choice.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WelcomeWiz_Choice.xml
Copy: C:\Deployment1\Scripts\WelcomeWiz_Choice.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WelcomeWiz_Choice.vbs
Copy: C:\Deployment1\Scripts\WelcomeWiz_DeployRoot.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WelcomeWiz_DeployRoot.xml
Copy: C:\Deployment1\Scripts\WelcomeWiz_DeployRoot.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WelcomeWiz_DeployRoot.vbs
Copy: C:\Deployment1\Scripts\WelcomeWiz_Initialize.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WelcomeWiz_Initialize.xml
Copy: C:\Deployment1\Scripts\WelcomeWiz_Initialize.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WelcomeWiz_Initialize.vbs
Copy: C:\Deployment1\Scripts\SelectItem.jpg to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\SelectItem.jpg
Copy: C:\Deployment1\Scripts\WelcomeBanner.jpg to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WelcomeBanner.jpg
Copy: C:\Deployment1\Scripts\btnout.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\btnout.png
Copy: C:\Deployment1\Scripts\btnover.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\btnover.png
Copy: C:\Deployment1\Scripts\btnsel.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\btnsel.png
Copy: C:\Deployment1\Scripts\LTIGetFolder.wsf to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\LTIGetFolder.wsf
Copy: C:\Deployment1\Scripts\NICSettings_Definition_ENU.xml to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\NICSettings_Definition_ENU.xml
Copy: C:\Deployment1\Scripts\ZTINicUtility.vbs to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTINicUtility.vbs
Copy: C:\Deployment1\Scripts\ZTINicConfig.wsf to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ZTINicConfig.wsf
Copy: C:\Deployment1\Scripts\BackButton.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\BackButton.png
Copy: C:\Deployment1\Scripts\FolderIcon.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\FolderIcon.png
Copy: C:\Deployment1\Scripts\ItemIcon1.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\ItemIcon1.png
Copy: C:\Deployment1\Scripts\MinusIcon1.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\MinusIcon1.png
Copy: C:\Deployment1\Scripts\PlusIcon1.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\PlusIcon1.png
Copy: C:\Deployment1\Scripts\SelectItem.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\SelectItem.png
Copy: C:\Deployment1\Scripts\header-image.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\header-image.png
Copy: C:\Deployment1\Scripts\NavBar.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\NavBar.png
Copy: C:\Deployment1\Scripts\Computer.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\Computer.png
Copy: C:\Deployment1\Scripts\WelcomeWiz_Background.jpg to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\WelcomeWiz_Background.jpg
Copy: C:\Deployment1\Scripts\DeployWiz_Administrator.png to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Scripts\DeployWiz_Administrator.png
Copy: C:\Deployment1\Tools\x64\BDDRUN.exe to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Windows\system32\BDDRUN.exe
Copy: C:\Deployment1\Tools\x64\WinRERUN.exe to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\WinRERUN.exe
Copy: C:\Deployment1\Tools\x64\CcmCore.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\CcmCore.dll
Copy: C:\Deployment1\Tools\x64\CcmUtilLib.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\CcmUtilLib.dll
Copy: C:\Deployment1\Tools\x64\Smsboot.exe to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\Smsboot.exe
Copy: C:\Deployment1\Tools\x64\SmsCore.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\SmsCore.dll
Copy: C:\Deployment1\Tools\x64\TsCore.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\TsCore.dll
Copy: C:\Deployment1\Tools\x64\TSEnv.exe to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\TSEnv.exe
Copy: C:\Deployment1\Tools\x64\TsManager.exe to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\TsManager.exe
Copy: C:\Deployment1\Tools\x64\TsmBootstrap.exe to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\TsmBootstrap.exe
Copy: C:\Deployment1\Tools\x64\TsMessaging.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\TsMessaging.dll
Copy: C:\Deployment1\Tools\x64\TsmBootstrap.exe to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\TsmBootstrap.exe
Copy: C:\Deployment1\Tools\x64\TsProgressUI.exe to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\TsProgressUI.exe
Copy: C:\Deployment1\Tools\x64\TSResNlc.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\TSResNlc.dll
Copy: C:\Deployment1\Tools\x64\CommonUtils.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\CommonUtils.dll
Copy: C:\Deployment1\Tools\x64\ccmgencert.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\ccmgencert.dll
Copy: C:\Deployment1\Tools\x64\msvcp120.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\msvcp120.dll
Copy: C:\Deployment1\Tools\x64\msvcr120.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\msvcr120.dll
Copy: C:\Deployment1\Tools\x64\00000409\tsres.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\00000409\tsres.dll
Copy: C:\Deployment1\Tools\x64\Microsoft.BDD.Utility.dll to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Deploy\Tools\x64\Microsoft.BDD.Utility.dll
Copy: C:\Program Files\Microsoft Deployment Toolkit\Samples\Background.bmp to C:\Users\ADMINI~1.INT\AppData\Local\Temp\2\MDTUpdate.2492\Mount\Windows\system32\winpe.bmp
ERROR: The process cannot access the file because it is being used by another process. 
Exit code = 1

REG LOAD failed, rc = 1.

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

==============================================================

What causes this?

Litetouch deployment runs task sequence, installs image, almost completes and then logs in as administrator and just sits there, does not run any state restore tasks listed in task sequence. It will stay like this until logged off. However, once PC is rebooted it logs straight into administrator again and just sits.

Tested current Image/Task sequence we use and that still deploys fine and performs all tasks listed in the task sequence, so it is not an issue with the server.

In the new image the only changes are Windows updates, installed programme update & some programmes and folders have been removed.

Any help would be greatly appreciated.

Note -

MDT 2010 (64 bit) / WDS

Windows 7 (32 bit) image)

Hi Guys,

I am getting an error when importing an operating system into my deployment share.

Performing the operation “import” on target “Operating system”.
Creating new item named REFW81X64CDrive in Windows 8.1×64 REFW81X64.wim at DS002:\Operating Systems.
Creating new item named REFW81X64CDrive in Windows 8.1×64 REFW81X64.wim at DS002:\Operating Systems.
Item already exists: ‘E:\MDT\DEPLOYMENT\Operating Systems\REFW81X64CDrive in Windows 8.1×64.wim’ specified.
Import processing finished.

It says item already exists ” specified. Can you please tell me what is happening??

I have done abit of research and some people are saying to remove the tag of the operating system from the Operatingsystems.xml in the control folder in your deployment share. I have tried this buyt it still is failing.

Some please help!

Hello,

i need help for create a boot image. where is a bcdedit error by creating the boot image.

here is the log

Hi all,

I have 2 problems with MDT 2013 that I need some help with. I'm deploying Windows 7 (OEM until the VL license is in place very soon, so no comments on that pls.!)

Let's start with the customsettings.ini:

[Settings]
Priority=DefaultGateway,Manufacturer,Default

[DefaultGateway]
192.168.31.1=SiteA
192.168.32.1=SiteB
192.168.33.1=SiteC
192.168.34.1=SiteD

[SiteA]
OSDComputerName=PC-A-
MachineObjectOU=OU=SiteA,OU=Workstations,OU=Computers,OU=Managed,DC=domain,DC=local

[SiteB]
OSDComputerName=PC-B-
MachineObjectOU=OU=SiteB,OU=Workstations,OU=Computers,OU=Managed,DC=domain,DC=local

[SiteC]
OSDComputerName=PC-C-
MachineObjectOU=OU=SiteC,OU=Workstations,OU=Computers,OU=Managed,DC=domain,DC=local

[SiteD]
OSDComputerName=PC-D-
MachineObjectOU=OU=SiteD,OU=Workstations,OU=Computers,OU=Managed,DC=domain,DC=local

[Manufacturer]
Dell Inc.=Dell
Hewlett Packard=HP
LENOVO=Lenovo
Microsoft Corporation=Microsoft

[Dell]
SkipProductKey=YESProductKey=32KD2-K9CTF-M3DJT-4J3WC-733WD

[HP]
SkipProductKey=YESProductKey=74T2M-DKDBC-788W3-H689G-6P6GT

[Lenovo]
SkipProductKey=YESProductKey=237XB-GDJ7B-MV8MH-98QJM-24367

[Microsoft]
'For test deployment to a VMSkipProductKey=NOProductKey=AAAAA-BBBBB-CCCCC-DDDDD-EEEEE

[Default]
_SMSTSOrgName=Running %TaskSequenceID% on %OSDComputername%
KeyboardLocale=0406:00000406
OSInstall=Y

SkipComputerName=NO

Question 1:

According to the Gateway we pre-set the OSDComputerName with a name according to the naming convention. Later in the task sequence a number manually added (e.g. PC-A-321) 

Notice _SMSTSOrgName=Running %TaskSequenceID% on %OSDComputername%

When the TS are running I only see "Running .... on PC-A-" and not "Running ... on PC-A-321".

I have tried to update _SMSTSOrgName in a task sequence, but it is not reflected in the UI.

So how do it make the UI reflect the update of the %OSDComputername% with the value manually entered?

Question 2:

I try to detect the Manufacturer and set the OEM license key (they are public SLP license keys). It does not seem to work. It is possible at all to detect Manufactorer at all in the [Settings] section?

If I manually create a task sequence for each OEM vendor and add the license key during the TS setup it works.

What am I doing wrong?

Thank you for any input!

Hello Community,

I meet a problem while creating a Media from the DeploymentShare - Advanced Configuration - Media - Media001 - Update Media Content.

I use this method to create a USB MDT media for the Branch Office where there is no server.
It worked in the past but from the upgrade to WAIK 10 / WinPE 10, I'm unable to create a new Media...

Find below the message when I try to Update the media contents :

How could I solve this problem? An idea?

Thanks by advance ! :)

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,

I am using MDT to deploy a Windows 10 image to a test device. After the imaging process the machine logs into the Administrator account where usually the Deployment Wizard should launch and complete the MDT deployment, following a successful message or errors. However, after the device auto logs into the Administrator account to complete MDT, I am presented with a blank Wizard.hta screen. I followed the path to where the Wizard.hta is launching from and the folder is empty.

Folder = C:\Users\ADMINI~1\AppData\Local\Temp\DeploymentScripts\Wizard.hta

I also located the log file and found this: (Wizard.log)

<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Microsoft Deployment Toolkit version: 6.3.8330.1000]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Property Debug is now = FALSE]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Not Wizard = False]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[FAILURE ( 20001 ): Definition file not defined. Please call with /Defintion:<file>   CommandLine:"\\myimages\mymdt\Scripts\Wizard.hta"]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="3" thread="" file="Wizard"><![LOG[Microsoft Deployment Toolkit version: 6.3.8330.1000]LOG]!><time="15:40:01.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Not Wizard = False]LOG]!><time="15:40:01.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[FAILURE ( 20001 ): Definition file not defined. Please call with /Defintion:<file>   CommandLine:"\\myimages\mymdt\Scripts\Wizard.hta"]LOG]!><time="15:40:01.000+000" date="03-14-2016" component="Wizard" context="" type="3" thread="" file="Wizard">

Would anyone know why the Wizard.hta is not properly launching and why MDT is not completing on Windows 10? 

Thank-you,

AP

I am having issues with MDT 2013 image deployment. It is failing after the Operating Systems installation. 10 errors and 3 warnings. It seems it did not following thru the Task Sequences. The log says it did not have enough disk space. I checked the space used after the deployment. it showed 70GB free space out of the 80GB. I am not sure were to start this. search on the google regarding the error codes. It did not help.

JC