At this moment i am creating a new task sequence in MDT to deploy Windows 10 Enterprise x64 (build 1607).

I created a task where i deploy a custom Windows start menu. This is what i already did.

1) I created internet shortcuts (.url files) and copied them into the startmenu/programms folder.
2) I right clicked these shortcuts which appear in the startmenu and selected "Pin to start". Now they appear as tiles.
3) I exported the menu with Powershell using Export-Startlayout –path C:\Startmenu.xml
4) I copied the startmenu.xml and the shortcuts to my MDT script folder.
5) In MDT i created a task to copy the layout file to the local machine during deployment usingcmd.exe /c copy %SCRIPTROOT%\startmenu\LayoutStartMenu.xml c:\Windows\Temp
6) In MDT i created a task to copy the URL file to the local machine during the deployment using:cmd.exe /c copy %SCRIPTROOT%\startmenu\theurlfile.url "C:\ProgramData\Microsoft\Windows\Start Menu\Programs"
7) In MDT i created a "Run Powershell Script" task where i run a powershell script that imports the menu in Windows 10 during the deployment using:%SCRIPTROOT%\startmenu-win10\ApplyCustomMenu.ps1
 - (The script: Import-StartLayout –LayoutPath C:\Windows\Temp\LayoutStartMenu.xml -MountPath $env:SystemDrive\)

The problem:

When i restart the computer and I login as a user i can see that the custom menu appears. All the groups and select program tiles are there but not the URL tiles. The spaces are empty but no tiles are shown. The .URL are copied over and can be found in the startmenu/programs folder. I just have to click them again and select pin to start.

Does someone has an idea what i do or goes wrong?

Hello,

I'm in the process of building a reference image containing things like the Visual C++ packages as well as the Office365 suite. I seem to be stuck on the Office365 part. From my understanding, I need to use the Office 2016 Deployment Tool to customize/manage these deployments. This is where I get stuck:

1. Upon downloading this from Microsoft (1) I run it and it puts a 'setup' application where I specify. From my reading it seems as if running this 'setup' should extract the Office Deployment Tool (setup.exe) and a sample configuration file (configuration.xml). However, nothing happens when I run this setup. A cmd-like screen very briefly flashes then nothing. What am I doing wrong?
2. Assuming I'm missing something in the first step... will the tool create an appropriate .msi image to put into MDT going by way of Applications --> New Application --> Application with source file (the .msi?)??? Obviously I'll have to modify the task sequence as well but it should work the same way as the Visual C++ installs I guess. What's the point in this if MDT has a built in 'Microsoft Office Customization' tool? Can't I just throw in an install.msi and customize it with that? Where would I get an appropriate .msi? (2)

From reading I think that I might be missing something with the command line. Thank you in advance!

(1) https://www.microsoft.com/en-us/download/details.aspx?id=49117

(2) https://technet.microsoft.com/en-us/itpro/windows/deploy/create-a-windows-10-reference-image

We're struggling with trying to deploy a Windows 7 image created with MDT 2012 via Windows 2008 WDS to an HP notebook. We boot through WDS and then when we choose the OS to deploy we get a Windows Boot Manager message

Status: 0xc0000017

Info: There isn't enough memory available to create a ramdisk device.

Anyone seen this before?

Orange County District Attorney

I've been Google'ing, searching TechNet and perusing the MDT Documentation Library for a complete guide to "customsettings.ini". While I've managed to find bits and pieces here and there, I've yet to find something that lists all the possible commands and variables. Does anyone know where I can find this?  Or even a giant example customsettings file with all the commands they know of with a line by line explanation of what each does. (It's OK to leave out the database parts.)

Thanks!!!

Hello,

I've encountered an error today that I've not seen before.

We've been running our environment on a Virtual server hosted at a remote location for a few months now -- we previously had a physical server hosted on location by us. We run MDT 2013 Update 2 on the virtual Server 2012 R2 with ADK version 10.1.14393.0.

Everything has been working fine until today. I updated  a couple of applications to newer versions, and am now receiving an error when attempting to completely regenerate the boot image.

The error I am receiving inside of MDT is: Access to the path 'C:\Users\administrator.AMERIFIRST\AppData\Local\Temp\2\MDTUpdate.4124\LiteTouchPE_x64.wim' is denied. ---> System.UnauthorizedAccessException: Access to the path 'C:\Users\administrator.AMERIFIRST\AppData\Local\Temp\2\MDTUpdate.4124\LiteTouchPE_x64.wim' is denied.

Here is the log file directly from MDT.

=== Making sure the deployment share has the latest x86 tools ===
=== 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 D:\DeploymentShare\Operating Systems\Windows 10 Pro x64 Anniversary\Sources\boot.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
Injected driver ASIX Net NETAX88772.inf 3.16.8.0
Injected driver Atheros Communications Inc. Net netathrx.inf 10.0.0.298
Injected driver Broadcom Net b57nd60a.inf 12.4.1.0
Injected driver Broadcom Net b57nd60a.inf 14.0.0.7
Injected driver Broadcom Net b57nd60a.inf 14.4.2.2
Injected driver Broadcom Net b57nd60a.inf 14.4.2.4
Injected driver Broadcom Net b57nd60a.inf 15.0.0.17
Injected driver Broadcom Net k57nd60a.inf 12.4.0.3
Injected driver Broadcom Net k57nd60a.inf 14.0.0.7
Injected driver Broadcom Net k57nd60a.inf 14.4.2.2
Injected driver Broadcom Net k57nd60a.inf 14.4.2.2 (1)
Injected driver Broadcom Net k57nd60a.inf 15.0.0.6
Injected driver Intel Corporation hdc iaAHCIC (15).inf 12.9.0.1001
Injected driver Intel Corporation hdc iaAHCIC (17).inf 12.8.2.1000
Injected driver Intel Corporation hdc iaAHCIC (19).inf 14.5.2.1088
Injected driver Intel Corporation hdc iaAHCIC.inf 12.8.0.1016
Injected driver Intel Corporation hdc iaAHCIC.inf 14.5.2.1088 (1)
Injected driver Intel Corporation SCSIAdapter iaAHCI.inf 4.3.0.1198
Injected driver Intel Corporation SCSIAdapter iaAHCIB.inf 4.3.0.1198
Injected driver Intel Corporation SCSIAdapter iaStorA.inf 4.3.0.1198
Injected driver Intel Corporation SCSIAdapter iaStorAC (41).inf 12.9.0.1001
Injected driver Intel Corporation SCSIAdapter iaStorAC (43).inf 12.8.2.1000
Injected driver Intel Corporation SCSIAdapter iaStorAC (46).inf 14.5.2.1088
Injected driver Intel Corporation SCSIAdapter iaStorAC.inf 12.8.0.1016
Injected driver Intel Corporation SCSIAdapter iaStorAC.inf 14.5.2.1088 (1)
Injected driver Intel Corporation SCSIAdapter iaStorB.inf 4.3.0.1198
Injected driver Intel Corporation SCSIAdapter iaStorS.inf 4.3.0.1198
Injected driver Intel hdc iaAHCI.inf 10.1.0.1008
Injected driver Intel hdc iaAHCI.inf 11.0.0.1032
Injected driver Intel Net E1c62x64.INF 11.15.12.0
Injected driver Intel Net E1c62x64.INF 11.8.81.0
Injected driver Intel Net E1C62x64.inf 11.8.81.0 (1)
Injected driver Intel Net E1C62x64.inf 12.10.29.0
Injected driver Intel Net E1C62x64.INF 12.10.29.0 (1)
Injected driver Intel Net E1C62x64.inf 12.10.29.0 (2)
Injected driver Intel Net E1C63x64.inf 12.10.29.0
Injected driver Intel Net E1C63x64.inf 12.10.29.0 (1)
Injected driver Intel Net E1C64x64.INF 12.10.29.0
Injected driver Intel Net E1C64x64.inf 12.10.29.0 (1)
Injected driver Intel Net E1C65x64.inf 12.12.140.22
Injected driver Intel Net E1C65x64.inf 12.12.140.22 (1)
Injected driver Intel Net E1d62x64.INF 12.12.50.4
Injected driver Intel Net E1D62x64.inf 12.12.50.7205
Injected driver Intel Net E1D62x64.inf 12.13.17.4
Injected driver Intel Net E1d63x64.inf 12.12.50.4
Injected driver Intel Net E1D63x64.inf 12.13.17.4
Injected driver Intel Net E1D64x64.INF 12.12.50.4
Injected driver Intel Net E1D64x64.inf 12.13.17.4
Injected driver Intel Net E1D65x64.inf 12.13.17.4
Injected driver Intel Net E1D65x64.inf 12.13.17.4 (1)
Injected driver Intel Net E1K62x64.INF 11.5.10.0
Injected driver Intel Net E1Q63x64.inf 12.7.27.0
Injected driver Intel Net E1R62x64.inf 12.11.97.0
Injected driver Intel Net E1R62x64.INF 12.11.97.0 (1)
Injected driver Intel Net E1R62x64.inf 12.13.27.0
Injected driver Intel Net E1R63x64.INF 12.11.97.0
Injected driver Intel Net E1R63x64.inf 12.14.7.0
Injected driver Intel Net E1R64x64.INF 12.11.97.0
Injected driver Intel Net E1R64x64.inf 12.14.7.0
Injected driver Intel Net E1R65x64.inf 12.12.226.0
Injected driver Intel Net E1R65x64.inf 12.12.226.0 (1)
Injected driver Intel Net E1Y62x64.inf 10.0.6.0
Injected driver Intel Net Netwsw00.INF 15.13.0.2
Injected driver Intel Net Netwsw02.INF 17.13.0.9
Injected driver Intel SCSIAdapter iaStor.inf 10.1.0.1008
Injected driver Intel SCSIAdapter iaStor.inf 11.0.0.1032
Injected driver LSI Corp. SCSIAdapter megasas2 (75).inf 6.703.04.00
Injected driver LSI Corp. SCSIAdapter megasas2.inf 6.703.03.00
Injected driver LSI Corporation SCSIAdapter lsi_sas2.inf 2.00.66.02
Injected driver LSI Corporation SCSIAdapter lsi_sas3.inf 2.50.75.01
Injected driver Realtek Net rt640x64.inf 10.001.0505.2015
Injected driver Realtek Net rt64win7.inf 7.038.0113.2011
Injected driver Realtek Net rt64win7.inf 7.046.0610.2011
Injected driver Realtek Net rtu30x64w7.INF 7.14.1114.2014
Injected driver Realtek Net rtux64w10.INF 10.1.0506.2015
Injected driver Sierra Wireless Incorporated Net swg3knet05.inf 14.11.1050.69
Injected driver SMSC Net net7500-x64-n620f.inf 1.01.0009.0000
Injected driver SMSC Net net7500-x64-n630f.inf 2.3.0.1
Injected driver VMware, Inc. Net vmxnet3ndis6.inf 1.5.1.0
Injected driver VMware, Inc. SCSIAdapter pvscsi.inf 1.2.3.0
Copy: D:\DeploymentShare\Control\Bootstrap.ini to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\Bootstrap.ini
Copy: C:\Program Files\Microsoft Deployment Toolkit\Templates\Unattend_PE_x64.xml to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Unattend.xml
Copy: C:\Program Files\Microsoft Deployment Toolkit\Templates\winpeshl.ini to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Windows\system32\winpeshl.ini
Copy: D:\DeploymentShare\Scripts\LiteTouch.wsf to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\LiteTouch.wsf
Copy: D:\DeploymentShare\Scripts\ZTIUtility.vbs to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\ZTIUtility.vbs
Copy: D:\DeploymentShare\Scripts\ZTIBCDUtility.vbs to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\ZTIBCDUtility.vbs
Copy: D:\DeploymentShare\Scripts\ZTIDiskUtility.vbs to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\ZTIDiskUtility.vbs
Copy: D:\DeploymentShare\Scripts\ZTIDataAccess.vbs to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\ZTIDataAccess.vbs
Copy: D:\DeploymentShare\Scripts\ZTIConfigFile.vbs to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\ZTIConfigFile.vbs
Copy: D:\DeploymentShare\Scripts\ZTIGather.wsf to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\ZTIGather.wsf
Copy: D:\DeploymentShare\Scripts\ZTIGather.xml to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\ZTIGather.xml
Copy: D:\DeploymentShare\Scripts\Wizard.hta to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\Wizard.hta
Copy: D:\DeploymentShare\Scripts\Credentials_ENU.xml to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\Credentials_ENU.xml
Copy: D:\DeploymentShare\Scripts\Credentials_scripts.vbs to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\Credentials_scripts.vbs
Copy: D:\DeploymentShare\Scripts\WizUtility.vbs to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\WizUtility.vbs
Copy: D:\DeploymentShare\Scripts\Wizard.css to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\Wizard.css
Copy: D:\DeploymentShare\Scripts\Wizard.ico to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\Wizard.ico
Copy: D:\DeploymentShare\Scripts\BackButton.jpg to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\BackButton.jpg
Copy: D:\DeploymentShare\Scripts\plusicon.gif to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\plusicon.gif
Copy: D:\DeploymentShare\Scripts\minusico.gif to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\minusico.gif
Copy: D:\DeploymentShare\Scripts\Summary_Definition_ENU.xml to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\Summary_Definition_ENU.xml
Copy: D:\DeploymentShare\Scripts\Summary_scripts.vbs to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\Summary_scripts.vbs
Copy: D:\DeploymentShare\Scripts\LTICleanup.wsf to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\LTICleanup.wsf
Copy: D:\DeploymentShare\Scripts\BDD_Welcome_ENU.xml to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\BDD_Welcome_ENU.xml
Copy: D:\DeploymentShare\Scripts\WelcomeWiz_Choice.xml to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\WelcomeWiz_Choice.xml
Copy: D:\DeploymentShare\Scripts\WelcomeWiz_Choice.vbs to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\WelcomeWiz_Choice.vbs
Copy: D:\DeploymentShare\Scripts\WelcomeWiz_DeployRoot.xml to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\WelcomeWiz_DeployRoot.xml
Copy: D:\DeploymentShare\Scripts\WelcomeWiz_DeployRoot.vbs to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\WelcomeWiz_DeployRoot.vbs
Copy: D:\DeploymentShare\Scripts\WelcomeWiz_Initialize.xml to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\WelcomeWiz_Initialize.xml
Copy: D:\DeploymentShare\Scripts\WelcomeWiz_Initialize.vbs to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\WelcomeWiz_Initialize.vbs
Copy: D:\DeploymentShare\Scripts\SelectItem.jpg to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\SelectItem.jpg
Copy: D:\DeploymentShare\Scripts\WelcomeBanner.jpg to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\WelcomeBanner.jpg
Copy: D:\DeploymentShare\Scripts\btnout.png to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\btnout.png
Copy: D:\DeploymentShare\Scripts\btnover.png to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\btnover.png
Copy: D:\DeploymentShare\Scripts\btnsel.png to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\btnsel.png
Copy: D:\DeploymentShare\Scripts\LTIGetFolder.wsf to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\LTIGetFolder.wsf
Copy: D:\DeploymentShare\Scripts\NICSettings_Definition_ENU.xml to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\NICSettings_Definition_ENU.xml
Copy: D:\DeploymentShare\Scripts\ZTINicUtility.vbs to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\ZTINicUtility.vbs
Copy: D:\DeploymentShare\Scripts\ZTINicConfig.wsf to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\ZTINicConfig.wsf
Copy: D:\DeploymentShare\Scripts\BackButton.png to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\BackButton.png
Copy: D:\DeploymentShare\Scripts\FolderIcon.png to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\FolderIcon.png
Copy: D:\DeploymentShare\Scripts\ItemIcon1.png to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\ItemIcon1.png
Copy: D:\DeploymentShare\Scripts\MinusIcon1.png to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\MinusIcon1.png
Copy: D:\DeploymentShare\Scripts\PlusIcon1.png to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\PlusIcon1.png
Copy: D:\DeploymentShare\Scripts\SelectItem.png to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\SelectItem.png
Copy: D:\DeploymentShare\Scripts\header-image.png to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\header-image.png
Copy: D:\DeploymentShare\Scripts\NavBar.png to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\NavBar.png
Copy: D:\DeploymentShare\Scripts\Computer.png to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\Computer.png
Copy: D:\DeploymentShare\Scripts\WelcomeWiz_Background.jpg to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\WelcomeWiz_Background.jpg
Copy: D:\DeploymentShare\Scripts\DeployWiz_Administrator.png to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Scripts\DeployWiz_Administrator.png
Copy: D:\DeploymentShare\Tools\x64\BDDRUN.exe to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Windows\system32\BDDRUN.exe
Copy: D:\DeploymentShare\Tools\x64\WinRERUN.exe to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\WinRERUN.exe
Copy: D:\DeploymentShare\Tools\x64\CcmCore.dll to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\CcmCore.dll
Copy: D:\DeploymentShare\Tools\x64\CcmUtilLib.dll to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\CcmUtilLib.dll
Copy: D:\DeploymentShare\Tools\x64\Smsboot.exe to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\Smsboot.exe
Copy: D:\DeploymentShare\Tools\x64\SmsCore.dll to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\SmsCore.dll
Copy: D:\DeploymentShare\Tools\x64\TsCore.dll to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\TsCore.dll
Copy: D:\DeploymentShare\Tools\x64\TSEnv.exe to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\TSEnv.exe
Copy: D:\DeploymentShare\Tools\x64\TsManager.exe to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\TsManager.exe
Copy: D:\DeploymentShare\Tools\x64\TsmBootstrap.exe to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\TsmBootstrap.exe
Copy: D:\DeploymentShare\Tools\x64\TsMessaging.dll to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\TsMessaging.dll
Copy: D:\DeploymentShare\Tools\x64\TsmBootstrap.exe to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\TsmBootstrap.exe
Copy: D:\DeploymentShare\Tools\x64\TsProgressUI.exe to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\TsProgressUI.exe
Copy: D:\DeploymentShare\Tools\x64\TSResNlc.dll to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\TSResNlc.dll
Copy: D:\DeploymentShare\Tools\x64\CommonUtils.dll to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\CommonUtils.dll
Copy: D:\DeploymentShare\Tools\x64\ccmgencert.dll to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\ccmgencert.dll
Copy: D:\DeploymentShare\Tools\x64\msvcp120.dll to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\msvcp120.dll
Copy: D:\DeploymentShare\Tools\x64\msvcr120.dll to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\msvcr120.dll
Copy: D:\DeploymentShare\Tools\x64\00000409\tsres.dll to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\00000409\tsres.dll
Copy: D:\DeploymentShare\Tools\x64\Microsoft.BDD.Utility.dll to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Deploy\Tools\x64\Microsoft.BDD.Utility.dll
Copy: C:\Program Files\Microsoft Deployment Toolkit\Samples\Background.bmp to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\Windows\system32\winpe.bmp
Copy: D:\DeploymentShare\CCTK\x64 to C:\Users\ADMINI~1.AME\AppData\Local\Temp\2\MDTUpdate.4124\Mount\
Compressing the WIM to reclaim unused space.

System.Management.Automation.CmdletInvocationException: Access to the path 'C:\Users\administrator.AMERIFIRST\AppData\Local\Temp\2\MDTUpdate.4124\LiteTouchPE_x64.wim' is denied. ---> System.UnauthorizedAccessException: Access to the path 'C:\Users\administrator.AMERIFIRST\AppData\Local\Temp\2\MDTUpdate.4124\LiteTouchPE_x64.wim' is denied.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.InternalDelete(String path, Boolean checkHost)
   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()

Has anyone seen this error before? This is severely stressing me out, and I cannot seem to fix it.

I've checked permissions, and even resorted to giving Everyone full access to the folder, which had no effect.

Any help will be greatly appreciated.

Thanks,

Bob

Guys,

I am trying to capture a Windows 7 x86 image. The image I am trying to capture is on a virtual machine (VMware Workstation). I am using MDT 2013. I have tried to capture the image by manually running Litetouch.wsf manually from the virtual machine and by PXE booting and selecting the capture task sequence.

Do you guys have any knowledge of the following error I get (see screenshot):

Hi All

My sincere apologies if this is in the wrong forum, please feel free to move it if so.

I have a question regarding a deployment task that I have for a Dell Latitude E5470. I have managed to get these devices to deploy after playing around with device drivers, device apps etc etc.

I can deploy to the device successfully using the Dell driver cab supplemented with individual driver applications added as an 'Application Bundle'. However, a recent change to the task whereby I modified the 'CustomSettings.ini' file to auto join our domain has resulted in one particular application (Intel Dynamic Platform and Thermal Framework) partially installing. One element of the application fails to install and leaves me with an unknown device within device manager. Deploying from another deployment share which doesn't utilise the auto join domain function installs all device drivers.....?

The previous task before the auto join had a pause within the task to allow our engineers to manually join the domain and required a restart after this and the engineer to log back into the device and resume the task. Is it this reboot or the pause in the task that successfully copied all of the required files and now auto join is failing to copy all required drivers....?

We are using MDT 2013, deploying to Dell Latitude E5470 with Windows 7 Pro 64 bit.

I hope this all makes sense to you and if not my apologies as I was given the task of taking over deployment after the previous person changed jobs so most of what I know has been through research and trial and error.

Thanks

Hello,

We have a Dell T5810 Precision i am trying to deploy with MDT 2013 U2 using Total Control
I am getting a BSOD Megasas2.sys error 359 on reboot, up until that point the drive is detected, formatted, drivers deployed and OS installed (Win7 SP1).  When i check the dynamic logs, no errors are appearing there. There is no NVME drive, its just a normal Samsung SM871 and the BIOS has been set to AHCI no RAID. we have the same SSD in many other Dell products and no problems with deployment.

I have tried booting with just 32 bit drivers, just 64 bit drivers, removing the Megasas2.sys 64bit drivers from LSICorp that get thrown in the boot.wim on updating the DeploymentShare. I have also tried the latest WinPE 3.0, 5.0 and 10 Cab packs from the Dell website which has made no difference to the error being recieved.

I can build the box manual and install drivers, but that doesn't fix the issue that is presented and defeats the purpose of having MDT in the first place.

Can anyone offer any suggestions??

I previously had MDT 2013 Update 2 installed, and upgraded to MDT 8443. I'm using ADK Win10 1607 with Windows 10 as the file server. This has been working for over a year now.

I upgraded the MDT software and updated my deployment share and litetouch WIM. I deployed my litetouch WIM to our WDS and booted off it.

Now, no matter what Task Sequence I select, after the "Ready to begin" screen, I get the following error:

Deployment Error
"Invalid DeploymentType value "" specified. The deployment will not proceed."
[OK]

I've tried every Task Sequence, I even built a new Task Sequence, I get thesame issue. I've tried manually specifying the "DeploymentType" various in both my bootstrap and in the Task Sequence itself, with no improvement.

I am currently completely down and unable to image systems.

==RULES==

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
SkipBDDWelcome=YES
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
SkipDomainMembership=NO
JoinDomain=domain.com
EventService=http://computer:9800

==BOOTSTRAP.INI==

Hello,

I have been testing a  number of scenarios with MDT using this video from Michael Beaver as a reference:

Deploy MDT 2013 and Windows 10 from scratch

https://www.youtube.com/watch?v=QOgvECpIsAI

In it - Mike sets up an MDT build lab from the ground up. One thing that is interesting to me in the vid - is where he inserts a Suspend command into the Deploy and Capture segment when first deploying Windows 10 to a new VM. This places a "Resume task sequence" icon on the desktop - but also allows the user to make mods to the Win 10 deployment as well.

While Mike does at least one thing in his video (Sets Remote Desktop to be on) - in my tests - I tried to do a few more things like add two group policy changes (Lose Consumer Experiences and Turn Off Cortana and I cleaned up the start menu etc - and then continue on with the Task Sequence by double clicking the icon.

But when I finally get around to capturing that image and then redeploying it to test it on a new VM - all of my tweaks are gone. No GP edits came across and the start menu is back to it's shoddy state.

Clearly something else is happening when I hit "Resume Task Sequence". Anyone have any ideas on why something like turning on Remote Desktop will stick in the captured images but my stuff will not?

Cheers,

B

Hey,

We are just in the process of putting MDT into our environment and have run into a couple of oddities with the HTA wizard I wanted to ask about out here.

1. On Surface Books the font is teeny tiny. Is there any way to fix the wizard for high DPI devices? The release notes say that it was fixed in the 8443 release so maybe I am doing something wrong.

2. On occasion the wizard will come up white or blank. I am thinking this might be due to a hiccup in the network maybe? I've seen a few posts about it on the internet but haven't been able to pin anything down for it.

Hi Guys

So I've just been given a selection of HP Spectre x360s and I'm looking to create a standard image on one and then replicate it to the other machines. I've set-up one as I'd like it already.

I believe I've set up the Capture and Sysprep task properly in MDT 2012 but I'm unable to get the LiteTouch script to run properly when I'm on the Laptop in question; I'm not given the option of Capturing an image, only Backing one up.
When I try and boot MDT from my USB I'm prompted to Capture the image, but it fails with error '[FAILURE ( 5456 ): Unable to determine Destination Disk, Partition, and/or Drive'

Please assist

Thanks
Mark

Hello community,

I have a huge problem with MDT2012 since yesterday: I cleaned my driver repository a little and now I cannot import driver CAB´s anymore, every time it ends with this error:

System.Management.Automation.CmdletInvocationException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index ---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.ThrowHelper.ThrowArgumentOutOfRangeException()
   at System.Collections.Generic.List`1.get_Item(Int32 index)
   at Microsoft.BDD.PSSnapIn.Verifier.AddDriver(String theInfFile)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.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()

Funny: For testing I have created a second (new) "deployment share" and the same CABs gets imported without problems there. So the problem must be somewhere in my old share, but I have no clue how to fix this.

I crawled tho hole web and can not find anything! I don´t wont to move my whole share to the new one :(

Any advise?

Hello all,

I am currently trying to set up a windows server 2012 r2 with MDT 2013 update 2 and ADK on it. My boss has given me the task to get this up and running before the spring semester starts in January because he wants to stop using Semantic Ghost. I have no idea what I am doing wrong or if I have missed a step. I have no one helping me work on this project and my boss knows nothing about the MDT system. Now with all that in mind here is my problem:

I have the server 2012 r2 set up on VMware vSphere and the MDT 2013 update 2 and ADK are on this virtual machine and all ready to go. I am needing to push a Windows 10 Pro image with multiple programs (Tableau 9.2, Python, Visual Studios, etc.) out to 40 desktop machines. I know how to create the image and get all of that stuff working, but when I go to push the image to a machine in the lab using PXE Boot nothing happens. PXE Boot comes back with "No boot filename recieved" or something like that. We have a server rack in our lab and the old ghost server is off and has been off for a while now. I have made sure that the virtual machine and the desktop machines are on the same subnet. I am able to ping the virtual machine from the desktops, but I can only ping the desktops from the virtual machine if the firewall is down on the desktops. The DHCP is not set up on the virtual machine server because it is set up on our server rack.  

I need help figuring out how to deploy the image from the virtual machine to the desktops using the PXE Boot. 

Hi,

So I'm having some issues doing very, very basic application installs. Basically I'm loading Flash, Java, and Adobe Reader in an image. I'll try to keep this simply and I'll cut it into a few parts. Screenshots of errors below. This should be very straightforward, what am I doing wrong?

FLASH PLAYER INSTALL

I have downloaded the IE-ActiveX.msi installer from Adobe distribution center. I subsequently added it as an application in MDT with quiet install command: msiexec.exe /i install_flash_player_23_active_x.msi /qn /norestart

I then added a task sequence for this and put that install after the Visual C++ packages.Issue: after deployment I receive a return code: 1603. I've Google'd this code and none of the problems apply to me. It's a new install, no duplicates, system permission is all give. See error screencaps below.

ACROBAT READER DC INSTALL

I downloaded this from the Adobe distrubution center as well. As before, I've added it as an application with a quiet install command: msiexec.exe /i Adobe_Reader_DC_MSI.msi /qn

I then added a task sequence for this install. Issue: after deployment it causes a problem because it tried to install it twice at the same time(?). See screenshot below for reference. It should be a quiet install with no user input, why is it prompting?

Java Install

I downloaded this from the manual download at Java. Specifically the 'Windows Offline' version calledjre-8u111-windows-i586.exe. I added this as an application with command line: jre-8u111-windows-i586.exe /s IEXPLORER=1

I then added a task sequence for this install. Issue: after deploy I get an error code -80. No luck Googl'ing this return code.

Error screen 1

Error screen 2

I have just upgraded MDT 2013 to Update 2 (skipped Update 1) and tested one of many self contained Media deployment ISO images we have. These use a specific Task Sequence ID which is hidden from the Wizard using "SkipTaskSequence=YES" and"TaskSequenceID=..." in CustomSettings.ini.

Unlike the previous MDT2013 (non-updated) version, the install now fails to proceed past the "Wizard Ready" stage with the error 'Invalid DeploymentType of "" '.

The Deployment Type (NEWCOMPUTER) is not set in CustomSettings.ini (never has been), but the logs clearly show it is discovered correctly set (to NEWCOMPUTER) by ZTIGather and LiteTouch; but the Wizard log then reports it as equal to "" at the very end of the Wizard run. Same thing happens if I actually add "DeploymentType=NEWCOMPUTER" to customsettings.ini.

I reinstated the TaskSequence Wizard page based on a previous posting, selected my Task Sequence in the Wizard at install and voila it worked!

So what has changed? Why can I no longer skip the TS Wizard page? What is resetting DeploymentType from NEWCOMPUTER to blank? Where should I be looking? Why does an update make things worse?

Logs available, any and all help appreciated!

STEVE

Happy New Year!

I am testing MDT in my local LAN environment and have been able to successfully deploy several Windows 10 test instances both to VMs and to actual physical hardware on the network.

But I do want to understand why the process of PXE boot to WDS server and the subsequent install of a selected system is so slow? Is it just the fact that everything has to come over the network or is there something else I am missing?

In my testing - the last being to physical hardware - I am estimating this deployment took 50 minutes to deploy. The same via USB key at the machine takes no more that 7 or 8 minutes tops.

Just wondering what the point of this if it takes so long? Is there some optimization that I have missed - or is this just the way it is?

I did have WSUS inline as part of a few of the tests but removed it as it seemed to take forever for an install to actually install updates from the server. But even after removal - it seems like my MDT script is doing nothing for 20 minutes after the OS looks like it is deployed.

Appreciate an insights on your install times or other things that I need to be looking at.

Cheers!

B

My Win10 deployment failed shortly after applying the custom OS image and unattend.xml. Looking into the logs, it seems the first instance of a failure was here in the SMSTS.LOG

Expand a string: %_SMSTSMDataPath%\Logs

Clear local default environment

D:\_SMSTaskSequence does not exist

Failed to create D:\_SMSTaskSequence

Failed to create user-specified local data path D:\_SMSTaskSequence. Error 0x80070003

We do not find an available volume to store the local data path

...

Failed to save environment to (80070057)

Failed to persist execution state