There are a lot of scripts, vb and PS.

I am trying to use Ps with .NET so I don't have to import AD module.

But getting an error when I am trying to move the object.

Cant figure this out:

Thank you

I'm keeping Win7, 1803 and now adding 1809 to MDT. My MDT version is 6.3.8450.1000 and ADK is 10.1.17134.1 (I'm not sure how to determine the build # of my ADK).

Do I need to upgrade MDT/ADK to handle 1809 and also Win7/1803? If so, what versions do I need?
Thanks

I believe MDT should go from 8450 to 8456 but for ADK I'm not sure.

I have a new Dell Precision 3530 I'm trying to Boot to a LiteTouch.wim for rolling out Laptops and I seem to be having some issues. Every time I boot to UEFI NIC IPV4 it will connect and load the .wim but when Windows Development Toolkit runs all I get is a command prompt. But I want it to come up with an admin login so I can deploy the image. Boot mode is set to UEFI and secure boot is turned off, I've tested the .wim on other machines to see if its the .wim but it seems to be only happening on this Dell.

Update: Went to Dells site and downloaded the new WINPE drives and updated the .wim. Same problem still occurring.

Update Most Recent: deployed the LiteTouch.wim on 2 Dell Precision 3530 Laptops, One gives a "Dirty Boot" Popup before allowing me to enter in Admin credentials and Deploy. The other is giving a command prompt and nothing else. The only thing different between the two is the one that will deploy has a Bios of 1.5.1 and the other a Bios of 1.5.0.

Hey guys,

I've been searching for this and haven't found an answer yet.

I started using a total-control method deploying my drivers and for the most part it's been great - But when trying to import my driver package to another deployment share, it reports tat it cannot copy files because there are duplicates.

I thought it might have just been complaining about the files itself (because MDT seems to manage the back end files on its own, as not to create duplicates, etc.) and still be copying all the links in my organized folders... but it isn't doing them either.

Has anybody found a solution for this?

Thanks,

I am trying to upgrade all the computers in my company from Win 7 to Win 10 1809/1803 with MDT solution. What's the hardware requirement for the Win 7 client (Especially for hard disk). I did some research on internet but I didn't find any official answer and I deploy the upgrade in my test lab and I still don't know the limitation.

Sit back and relax. This post will be lengthy. I have been racking my brain on this for over a week, and I desperately need a hero. Let me start with the scenario. We use a combination of MDT\WDS to deploy our images (we also have an SCCM environment that is not integrated with MDT). We are in the middle of using MDT's refresh capability to replace our Windows 7 bitlockered OS' with Windows 10. The refresh process goes like this:

1. Litetouch.vbs is executed from within a running Windows 7 OS that has Bitlocker enabled.
2. Task sequence is executed, and performs the following key steps: (a) backs up user profiles via USMT, (b) disables BDE protectors, (c) applies Windows PE, (d) reboots to MDT to continue the task sequence
3. Once the PC has booted into the MDT environment, the task sequence continues on like this (key elements only): (a) applies the WIM, (b) converts the bios to UEFI via Dell CCTK, (c) converts the MBR to GPT via the Microsoft MBR2GPT utility, (d) reboots to load Windows 10 for the first time.

This last reboot is where the issue lies. As soon as the task sequence hits that 'Restart' task, it blue screens with an 'fvevol.sys' error, and a 'DRIVER IRQL NOT LESS OR EQUAL' error, and it just sits there until the power is cycled. Now once you cycle the power, the task sequence continues without error, but we kick these off remotely. So our only option right now is to either have the end user cycle the power, or be physically present at the workstation.

Now...with the previous iteration of WinPE, we were still getting this blue, but it would at least reboot automatically, and continue on with the task sequence. I have scoured the internet, and cannot find anything related to this. I find it hard to believe that no one is encountering this, as it happens on EVERY machine of ours (not a random thing). Here is what I have tried so far:

1. Removed the built-in 'Disable BDE protectors' task in MDT, and replaced it with a script of my own (no change).
2. Mounted the 'LiteTouchPE_x64.wim' and edited the registry entry "AutoReboot" value from 0 to 1. This change causes the PC to shutdown after the bluescreen instead of rebooting.
3. Mounted the 'LiteTouchPE_x64.wim' and edited the registry so that it does not load fvevol.sys (a bitlocker driver). This causes the PC to boot straight to the MDT menu (task sequence does not continue), as it can no longer read the scripts from the drive due to encryption. I thought this was rather strange since the bde protectors get disabled before it reboots to WinPE. This tells me that WinPE is possibly re-enabling bitlocker.

The only thing I have not tried is fully decrypting the drive. I suspect this would work, but I shouldn't have to do this. Also, this issue does not occur if we boot straight to MDT using a 'New Computer' deployment type scenario.

I would greatly appreciate any feedback on this! Thanks to all in advance!

Good Morning, 

 Yesterday I was working in MDT to add a App package. It wasn't working so I deleted it and updated the Deployment Share. When I try to PXE boot now, I am getting this error:

Nothing else changed except for me deleting the app package I was trying to install. Everything was working fine until I updated the deployment share. Any ideas on what went wrong here?

---

SC

Hello all.

I'm currently using MDT 8456 and I've created a Windows 10 v1809 image inside Virtualbox (as I usually do, up to v1803) and I've browsed to my \\DeploymentShare$\Scripts folder and I'm trying to run LiteTouch.wsf in order to select my Sysprep & Capture Task Sequence but nothing happens when I run it. It shows the loading animation (spinning circle) and I can see wscript.exe in Task Manager but the shell for the TS doesn't show up. I thought my MDT was broken somehow but I went back to my v1803 VM and that worked fine. 

I included some Logs here, hopefully that'll help. I'm hoping I don't have to rebuild this image and that someone can point me in the right direction.

If I bring in the USB 3.0 drivers into Out-of-box drivers then there are no issues but if I install this as an application MDT throws return code: 14. Why?

ZTIApp.log

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

################ZTIApplications1/31/2013 5:56:14 PM0 (0x0000)
Entry: {e39639af-2231-4151-a230-2e6ef3e52f56} ZTIApplications1/31/2013 5:56:14 PM0 (0x0000)
Name:  Intel USB 3.0ZTIApplications1/31/2013 5:56:14 PM0 (0x0000)
################ZTIApplications1/31/2013 5:56:14 PM0 (0x0000)
Validating connection to \\myserver\MDTProductionShare$\Applications\Intel USB 3.0ZTIApplications1/31/2013 5:56:14 PM0 (0x0000)
Already connected to server myserver as that is where this script is running from.ZTIApplications1/31/2013 5:56:14 PM0 (0x0000)
Change directory: \\myserver\MDTProductionShare$\Applications\Intel USB 3.0ZTIApplications1/31/2013 5:56:14 PM0 (0x0000)
Run Command: \\myserver\MDTProductionShare$\Tools\X64\bddrun.exe Setup.exe -sZTIApplications1/31/2013 5:56:14 PM0 (0x0000)
ZTI installing application ZTIApplications1/31/2013 5:56:14 PM0 (0x0000)
Event 41031 sent: ZTI installing application ZTIApplications1/31/2013 5:56:14 PM0 (0x0000)
About to run command: \\myserver\MDTProductionShare$\Tools\X64\bddrun.exe Setup.exe -sZTIApplications1/31/2013 5:56:14 PM0 (0x0000)
Command has been started (process ID 2820)ZTIApplications1/31/2013 5:56:14 PM0 (0x0000)
ZTI Heartbeat: command has been running for 0 minutes (process ID 2820)ZTIApplications1/31/2013 5:56:14 PM0 (0x0000)
Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 2820)ZTIApplications1/31/2013 5:56:14 PM0 (0x0000)
Return code from command = 14ZTIApplications1/31/2013 5:56:25 PM0 (0x0000)
Application Intel USB 3.0 returned an unexpected return code: 14ZTIApplications1/31/2013 5:56:25 PM0 (0x0000)
Event 41034 sent: Application Intel USB 3.0 returned an unexpected return code: 14ZTIApplications1/31/2013 5:56:25 PM0 (0x0000)
Property InstalledApplications001 is now = {cd89f564-0e36-4bb9-96de-0c5e44fe8168}ZTIApplications1/31/2013 5:56:25 PM0 (0x0000)
Property InstalledApplications002 is now = {ac202d91-77e0-4957-8f42-d561ff7332c6}ZTIApplications1/31/2013 5:56:25 PM0 (0x0000)
Property InstalledApplications003 is now = {e39639af-2231-4151-a230-2e6ef3e52f56}ZTIApplications1/31/2013 5:56:25 PM0 (0x0000)
Run Command is missing. ZTIApplications1/31/2013 5:56:26 PM0 (0x0000)
Property InstalledApplications001 is now = {cd89f564-0e36-4bb9-96de-0c5e44fe8168}ZTIApplications1/31/2013 5:56:26 PM0 (0x0000)
Property InstalledApplications002 is now = {ac202d91-77e0-4957-8f42-d561ff7332c6}ZTIApplications1/31/2013 5:56:26 PM0 (0x0000)
Property InstalledApplications003 is now = {e39639af-2231-4151-a230-2e6ef3e52f56}ZTIApplications1/31/2013 5:56:26 PM0 (0x0000)
Property InstalledApplications004 is now = {77cbcd50-ef90-46d8-9fc9-0c988e613c79}ZTIApplications1/31/2013 5:56:26 PM0 (0x0000)
ZTIApplications processing completed successfully. ZTIApplications1/31/2013 5:56:26 PM0 (0x0000)
Event 41001 sent: ZTIApplications processing completed successfully.ZTIApplications1/31/2013 5:56:26 PM0 (0x0000)
Microsoft Deployment Toolkit version: 6.1.2373.0 ZTIApplications1/31/2013 5:56:26 PM0 (0x0000)
The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.ZTIApplications1/31/2013 5:56:26 PM0 (0x0000)
Language/Locale Identified (in order of precedence): 1033,0409,0x0409,9,0009,0x0009ZTIApplications1/31/2013 5:56:26 PM0 (0x0000)
Mandatory Single Application install indicated. Guid: {056d0e83-2b28-47c2-a132-839a238c6bd4}ZTIApplications1/31/2013 5:56:26 PM0 (0x0000)

But IntelUSB3.log shows exit code: 0

Log:

--------

>> 1/31/2013 17:56:14:547
[Install Configuration]
  Installer Version: 1.4.38.0
  Compile date = Thu Apr 19 15:38:46 2012
  OS command line = Setup.exe -s
  Effective command line = -s
  Windows Version = Windows 7 SP1
  Platform = 64 bit
  Core Version = 3.0.1 (IIF2++)
  System up time = 41 sec
  Source: \\myserver\MDTProductionShare$\Applications\Intel USB 3.0
[Languages]
  0401 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\ar-SA\setup.exe.mui
  0405 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\cs-CZ\setup.exe.mui
  0406 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\da-DK\setup.exe.mui
  0407 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\de-DE\setup.exe.mui
  0408 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\el-GR\setup.exe.mui
  0409 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\en-US\setup.exe.mui
  0C0A - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\es-ES\setup.exe.mui
  040B - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\fi-FI\setup.exe.mui
  040C - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\fr-FR\setup.exe.mui
  040D - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\he-IL\setup.exe.mui
  040E - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\hu-HU\setup.exe.mui
  0410 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\it-IT\setup.exe.mui
  0411 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\ja-JP\setup.exe.mui
  0412 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\ko-KR\setup.exe.mui
  0414 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\nb-NO\setup.exe.mui
  0413 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\nl-NL\setup.exe.mui
  0415 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\pl-PL\setup.exe.mui
  0416 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\pt-BR\setup.exe.mui
  0816 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\pt-PT\setup.exe.mui
  0419 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\ru-RU\setup.exe.mui
  041B - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\sk-SK\setup.exe.mui
  0424 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\sl-SI\setup.exe.mui
  041D - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\sv-SE\setup.exe.mui
  041E - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\th-TH\setup.exe.mui
  041F - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\tr-TR\setup.exe.mui
  0804 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\zh-CN\setup.exe.mui
  0404 - \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Lang\zh-TW\setup.exe.mui
  User default LangID: 0x409
  User default UI language: 0x409
  Loaded language 0409
[Checking requirements]
  Checking for admin rights
  Admin rights OK
  Checking OS
  OS check OK
[Scanning drivers]
  Scanning drivers
  Found INF = \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\HCSwitch\x64\iusb3hcs.inf
  Found INF = \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\HCSwitch\x86\iusb3hcs.inf
  Found INF = \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\Win7\x64\iusb3hub.inf
  Found INF = \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\Win7\x64\iusb3xhc.inf
  Found INF = \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\Win7\x86\iusb3hub.inf
  Found INF = \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\Win7\x86\iusb3xhc.inf
  [INF Info]
    INF = \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\HCSwitch\x64\iusb3hcs.inf
*   Section <PackageInfo> Key <Sequence> not found in INF
    Date = 10/16/2012
    Version = 1.0.6.245
    ClassGUID = {4D36E97D-E325-11CE-BFC1-08002BE10318}
    PackageInfo.Name = iusb3hcs
    PackageInfo.Sequence = 0
    Manufacturer = HCSwitch_PCIF,NTAMD64.6.1,NTAMD64.6.2
    Resolved Manufacturer = HCSwitch_PCIF.NTAMD64.6.1
    Inf supports 64 bit.
    Description: PCI bus
    HardwareID = HCSwitch,*PNP0A08
    Matched HardwareID = *PNP0A08
    Installed Driver = {4d36e97d-e325-11ce-bfc1-08002be10318}\0014
*   Section <PackageInfo> Key <Name> not found in INF
  [INF Info]
    INF = \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\HCSwitch\x86\iusb3hcs.inf
*   Section <PackageInfo> Key <Sequence> not found in INF
    Date = 10/16/2012
    Version = 1.0.6.245
    ClassGUID = {4D36E97D-E325-11CE-BFC1-08002BE10318}
    PackageInfo.Name = iusb3hcs
    PackageInfo.Sequence = 0
    Manufacturer = HCSwitch_PCIF,NTx86.6.1,NTx86.6.2
    Resolved Manufacturer = HCSwitch_PCIF
!   Error locating a device section. Skipping inf
  [INF Info]
    INF = \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\Win7\x64\iusb3hub.inf
*   Section <PackageInfo> Key <Sequence> not found in INF
    Date = 10/16/2012
    Version = 1.0.6.245
    ClassGUID = {36FC9E60-C465-11CF-8056-444553540000}
    PackageInfo.Name = iusb3hub
    PackageInfo.Sequence = 0
    Manufacturer = Intel,NTAMD64.6.1,NTAMD64.6.2
    Resolved Manufacturer = Intel.NTAMD64.6.1
    Inf supports 64 bit.
    Description: Intel(R) USB 3.0 Root Hub
    HardwareID = IUsb3HubModel,IUSB3\ROOT_HUB30
    Description: USB 2.0 Hub
    HardwareID = IUsb3HubModel,IUSB3\CLASS_09&SUBCLASS_00&PROT_01
    Description: USB 2.0 MTT Hub
    HardwareID = IUsb3HubModel,IUSB3\CLASS_09&SUBCLASS_00&PROT_02
    Description: USB 3.0 Hub
    HardwareID = IUsb3HubModel,IUSB3\CLASS_09&SUBCLASS_00&PROT_03
    Description: USB Hub
    HardwareID = IUsb3HubModel,IUSB3\CLASS_09
  [INF Info]
    INF = \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\Win7\x64\iusb3xhc.inf
*   Section <PackageInfo> Key <Sequence> not found in INF
    Date = 10/16/2012
    Version = 1.0.6.245
    ClassGUID = {36FC9E60-C465-11CF-8056-444553540000}
    PackageInfo.Name = iusb3xhc
    PackageInfo.Sequence = 0
    Manufacturer = Intel,NTAMD64.6.1,NTAMD64.6.2
    Resolved Manufacturer = Intel.NTAMD64.6.1
    Inf supports 64 bit.
    Description: Intel(R) USB 3.0 eXtensible Host Controller
    HardwareID = IUsb3XhcModel,PCI\VEN_8086&DEV_1E31&REV_00
    Description: Intel(R) USB 3.0 eXtensible Host Controller
    HardwareID = IUsb3XhcModel,PCI\VEN_8086&DEV_1E31&REV_01
    Description: Intel(R) USB 3.0 eXtensible Host Controller
    HardwareID = IUsb3XhcModel,PCI\VEN_8086&DEV_1E31&REV_02
    Description: Intel(R) USB 3.0 eXtensible Host Controller
    HardwareID = IUsb3XhcModel,PCI\VEN_8086&DEV_1E31&REV_03
    Description: Intel(R) USB 3.0 eXtensible Host Controller
    HardwareID = IUsb3XhcModel,PCI\VEN_8086&DEV_1E31&REV_04
    Matched HardwareID = PCI\VEN_8086&DEV_1E31&REV_04
  [INF Info]
    INF = \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\Win7\x86\iusb3hub.inf
*   Section <PackageInfo> Key <Sequence> not found in INF
    Date = 10/16/2012
    Version = 1.0.6.245
    ClassGUID = {36FC9E60-C465-11CF-8056-444553540000}
    PackageInfo.Name = iusb3hub
    PackageInfo.Sequence = 0
    Manufacturer = Intel,NTx86.6.1,NTx86.6.2
    Resolved Manufacturer = Intel
!   Error locating a device section. Skipping inf
  [INF Info]
    INF = \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\Win7\x86\iusb3xhc.inf
*   Section <PackageInfo> Key <Sequence> not found in INF
    Date = 10/16/2012
    Version = 1.0.6.245
    ClassGUID = {36FC9E60-C465-11CF-8056-444553540000}
    PackageInfo.Name = iusb3xhc
    PackageInfo.Sequence = 0
    Manufacturer = Intel,NTx86.6.1,NTx86.6.2
    Resolved Manufacturer = Intel
!   Error locating a device section. Skipping inf
  Removed INF = \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\HCSwitch\x86\iusb3hcs.inf
  Removed INF = \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\Win7\x86\iusb3hub.inf
  Removed INF = \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\Win7\x86\iusb3xhc.inf
  Checking platform size
  Checking for downgrading
  [Checking INF versions]
    \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\HCSwitch\x64\iusb3hcs.inf
      PCI bus
        Installed version: 6.1.7601.17514
        Version in package: 1.0.6.245
        Installed INF info: Name=, Provider=Microsoft, Section=PCI_DRV_ROOT
        Existing installed INF is Inbox/Chipset INF/NULL driver OR marked as ignore. Skipping version check
    \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Drivers\Win7\x64\iusb3xhc.inf
      No previous version found
[Install]
* action file parsed
Reading action file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\setup.if2
Groups: DRIVER=1, HCSDRIVER=1, TOOLS=1
[Finding prior INFs]
  Prior INF files not found.
[Filter scan]
  Found filter
  No lower filters found.
[Filtering components per group]
[Filter conditions]
Sorting action list for installation
[Service - 0]
  Name = iusb3hcs
[Process - 0]
  Marking iusb3mon.exe to terminate when uninstalled
[Process - 0]
  Marking C:\windows\system32\wevtutil.exe to run when uninstalled
[Process - 0]
  Marking C:\windows\system32\wevtutil.exe to run when uninstalled
[Registry - 0]
  Marking registry value HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\USB3MON=, for deletion during uninstallation
[Folder - 0]
  Marking folder C:\Program Files (x86)\Intel\Intel(R) USB 3.0 eXtensible Host Controller Driver\uninstall\x64 for delete on uninstall
[Folder - 0]
  Marking folder C:\Program Files (x86)\Intel\Intel(R) USB 3.0 eXtensible Host Controller Driver\Drivers for delete on uninstall
[Folder - 0]
  Marking folder C:\Program Files (x86)\Intel\Intel(R) USB 3.0 eXtensible Host Controller Driver for delete on uninstall
[File - 100]
  Operation = copy
  Destination = C:\windows\system32\drivers\USB3Ver.dll
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\USB3Ver.dll
[File - 100]
  Operation = copy
  Destination = C:\Program Files (x86)\Intel\Intel(R) USB 3.0 eXtensible Host Controller Driver\uninstall\Setup.exe
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\Setup.exe
[Folder - 150]
  Source = \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang
  Destination = C:\Program Files (x86)\Intel\Intel(R) USB 3.0 eXtensible Host Controller Driver\uninstall
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\ar-SA\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\ar-SA\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\cs-CZ\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\cs-CZ\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\da-DK\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\da-DK\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\de-DE\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\de-DE\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\el-GR\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\el-GR\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\en-US\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\en-US\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\es-ES\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\es-ES\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\fi-FI\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\fi-FI\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\fr-FR\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\fr-FR\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\he-IL\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\he-IL\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\hu-HU\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\hu-HU\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\it-IT\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\it-IT\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\ja-JP\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\ja-JP\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\ko-KR\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\ko-KR\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\nb-NO\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\nb-NO\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\nl-NL\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\nl-NL\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\pl-PL\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\pl-PL\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\pt-BR\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\pt-BR\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\pt-PT\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\pt-PT\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\ru-RU\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\ru-RU\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\sk-SK\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\sk-SK\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\sl-SI\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\sl-SI\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\sv-SE\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\sv-SE\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\th-TH\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\th-TH\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\tr-TR\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\tr-TR\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\zh-CN\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\zh-CN\setup.exe.mui
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\zh-TW\license.txt
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\lang\zh-TW\setup.exe.mui
[File - 200]
  Operation = copy
  Destination = C:\Program Files (x86)\Intel\Intel(R) USB 3.0 eXtensible Host Controller Driver\uninstall\x64\Drv64.exe
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\x64\Drv64.exe
[File - 250]
  Operation = copyonly
  Destination = C:\windows\SysWOW64\difxapi.dll
    Copying file \\myserver\MDTProductionShare$\Applications\Intel USB 3.0\difxapi.dll

Hi there!

I am trying to edit unattended xml file (custom image) with my MDT ande ADK 10.1.18362.1 version. For some reson I get the error Non-zero return code from catalog utility, rc = 2002 at the end.

It does not matter if I try to open the xml file from WSIM, I see down belo the message "Can't find Windows Image information in answer file. I´ve also tried with a clean installation and some other WIM files which worked on MDT previous versions... Same error..

Any support is much appreciatted,

Leonardo D.

I've just updated my MDT version to 8465 and my ADK for 1809. Just created a brand new OS image from the DVD.

Now, trying to capture the image fails with INAGE_STATE_COMPLETE, sysprep did not complete. 2147467259.

Any ideas?

When installing applications as part of a task sequence I'm seeing entries in the logs saying "Command has been started (Process ID XX)" followed by "ZTI Heartbeat: command has been running for X minutes (process ID XX)" from component Install_Application.

Install_Application is 3rd party application wrapper I'm using, the previous version of it(8.5.1) required the EventShare property to be set in CustomSettings.ini, but the version I'm using now (12.1) does not have this requirement so I've commented out the EventShare property in CustomSettings.ini, yet the log entries above are still being written. 

The author of this app wrapper is hard to get hold of so my question to everyone here is, are these entries related to the EventShare property?  I mean, without knowing the code inside Install_Application.wsf can anyone tell me where these log entries are coming from?  The text  "ZTI Heartbeat:..." does not appear inInstall_Application.wsf or ZTIApplications.wsf, so how is it getting in the logs?

The reason I'm asking is I suspected the EventShare requirement of version 8.5.1 was causing intermittent issues with app installs, that's the main reason I updated to 12.1, but even after updating and removing the EventShare property from CustomSettings.ini it looks to like it's still working like it did in previously.

Here's what I've done so far, created a standard application SQL Server installer with quiet install command (tested when run manually):

setup.exe /action=INSTALL /IACCEPTSQLSERVERLICENSETERMS /qs /features=SQLEngine /INSTALLSQLDATADIR=E:\MSSQL\SYSTEM /SQLBACKUPDIR=D:\Backup\Database /SQLTEMPDBDIR=E:\MSSQL\TEMP /SQLTEMPDBLOGDIR=F:\MSSQL\TRANSLOG /SQLUSERDBDIR=E:\MSSQL\DATA /SQLUSERDBLOGDIR=F:\MSSQL\TRANSLOG /SECURITYMODE=SQL /SQLSYSADMINACCOUNTS="BUILTIN\Administrators" "myadmin" /AGTSVCSTARTUPTYPE=Automatic /INSTANCENAME=MSSQLSERVER /SAPWD=Password1

if you will notice, folders are located in different drives.

on my task sequence, I've formatted the disks first, set it online then assigning drive letters before creating a task "Install Application" which will install the SQL server.

also, already tried using setup.exe /ConfigurationFile=ConfigurationFile.ini (https://docs.microsoft.com/en-us/sql/database-engine/install-windows/install-sql-server-using-a-configuration-file?view=sql-server-2017) instead of the above command, but same results. here's the screenshot https://cdn1.imggmi.com/uploads/2019/5/9/13dacc4c8f71ffa45aa33c116d79624e-full.jpg

can't seem to get it work as it failed on the last task "Install Application". any ideas?

Thanks!

I recently upgraded to MDT 8456. There was an old issue with the correct steps not showing up in the sysprep and capture sequence. The fix was to edit the ZTIUtility.vbs with the line below

Look for this line:

If (oTS.SelectSingleNode("//step[@type='BDD_InstallOS']") is nothing) and (oTS.SelectSingleNode("//step[@type='BDD_UpgradeOS']") is nothing) then

And change it to:

If (oTS.SelectSingleNode("//step[@type='BDD_InstallOS' and @disable='false']") is nothing) and (oTS.SelectSingleNode("//step[@type='BDD_UpgradeOS' and @disable='false']") is nothing) then

I had done this edit in the past and it was still there after the upgrade, but I dont get correct screens when I try to sysprep and capture.

Has anyone else had this issue with 8456?

Here are my Custom settings in the same order:

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=YES
SkipCapture=NO
DoCapture=YES

DomainMembership=YES
SkipAdminPassword=YES
AdminPassword=Test1
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitlocker=YES

JoinDomain=mycompany.local
DomainAdmin=joindomain
DomainAdminDomain=MyCompany.local
DomainAdminPassword=MyCompany
MachineObjectOU=OU=mycompany Computers,DC=mycompany,DC=local

SkipTimeZone=YES
TimeZoneName=Eastern Standard Time
SkipLocaleSelection=YES
KeyboardLocale=en-US
UserLocale=en-US
UILanguage=en-US

SkipUserData=YES

When Domain join Credentials (bolded text above) are removed from customize.ini, Capture image pane shows in task sequence.

HOWEVER, when the Domain join credentials are added back in the Customize settings, The capture image pane  no longer shows. After selecting the Capture Windows 10 task sequence, it just tells me ready to begin. 

Can someone please tell me whats going on?

I'm new to MDT, so this could be something I'm missing, though I've searched all over the nets and find similar issues.  1809 ADK and 8456.1000 MDT installed on a 2016 Server, and it's an 1809 image we're trying to build.  I just cannot get the image to skip Windows Welcome - it starts at the Select Region page no matter what settings I put in the unattend.xml file.

The weird part is that if I turn on the VM that was used to create this reference image, it *does* skip the OOBE and goes to the login window.  So it appears there is something that happens during the capture phase, but I have no idea what it is.

But then, if I just choose Sysprep only vs. Capture when making the image, I get an error message stating "Could not find C:\LTIBootstrap.vbs" during the startup, which is a script that is specified in the OOBE section of the unattend.xml.

Can anyone give me any ideas of what is going on here?

We got a new batch of Dell latitude 5591 laptops and I set up WDS (server 2019) and MDT (6.3.8456) Created my own capture task sequence. First I had to inject updated drivers into the litetouchpe_x64.wim and add that to the boot images in WDS before the laptop would even PXE boot. Finally got it to PXE into WDS and ran the litetouchPE_x64.wim, but it kept failing with the above error as soon as it went to sysprep.

Booted into win10 and manually ran the litetouch.vbs, worked fine.

How to get this to work over PXE?

I have my WDS/MDT server set up with PXE booting right now.  It works great, I can set a PC to PXE boot and it will deploy the image like a champ.  I now need to create  a USB boot-only media.  I have some computers that can't do PXE boot, but they still need to imaged.  I would prefer not to do a whole offline USB stick as I want to keep the latest version available on the server.  I have created a USB boot media with the LiteTouch.iso image.  I boot from the usb media and it starts and stops at a command prompt.  I have checked and I do have IP and the Y: and Z: drives are mapped and I can see the data on the server.  If I close the command prompt, the computer reboots.  I've tried on several computers, but it always stops at the command prompt when booting from USB.  Any ideas?

Hi,

Has anyone seen any issues with MDT and deploying to Surface devices?

I created a reference image that installs the C++ packages and put the latest windows updates on. Also, I injected the EN-GB language pack into the reference WIM file.

Ive created a very basic task sequence that injects the drivers, performs a further windows update and activates Windows. When deployed all works OK except the biometrics and Windows Hello does not work. 

As a test, I manually rebuilt the laptop with the Windows 10 VL ISO I am using and it picks up the Biometrics with no issues, so hardware issues can be ruled out.

Im an Exchange guy by trade so this is not really my area of expertise. Anyone come across such an issue or can assist with troubleshooting? I'm testing on a Surface Book 2

Thanks in advance

I have my Start Menu tiles working perfectly on 1803. They are exactly where I want them and all is well.

Making a brand new image for 1809, I repeated the process but I don't get any tiles at all after deployment.

Does each individual OS require its own XML be created within that OS? (Are the XML files useable within different OS's)?

I tried making a new XML and kept getting an error about invalid XML file. Then I remembered all the little tweaks that had to be done in 1803 to get it to work, so I did those as well but I while I don't get an error, I don't get one tile on the Start Menu, just everything listed on the left.

Is anyone aware of any issues in 1809 assigning and setting up Tiles?

-Thanks