MDT 2013 Update 1 Now Available


9/15 Update: We have re-released MDT 2013 Update 1. Please see this post with revised release notes and updated known issues.

 

The Microsoft Deployment Toolkit (MDT) 2013 Update 1 is now available on the Microsoft Download Center. This update requires the Windows Assessment and Deployment Kit (ADK) for Windows 10, available on the Microsoft Hardware Dev Center. (The page also includes other Windows kits; remember for deployment you only need the Windows ADK for Windows 10.)

Significant changes in MDT 2013 Update 1:

  • Support for the Windows Assessment and Deployment Kit (ADK) for Windows 10
  • Support for deployment and upgrade of Windows 10
  • Support for integration with System Center 2012 R2 Configuration Manager SP1 with the Windows 10 ADK (see this post on the Configuration Manager Team blog for more information on using the Windows 10 ADK with Configuration Manager)

Here is a more detailed list of some specific changes in this release:

  • Support for new Enterprise LTSB and Education editions of Windows 10
  • Support for modern app (.appx) dependencies and bundles
  • Improved support for split image files (.swm)
  • Switched to using DISM for imaging processes (instead of deprecated ImageX)
  • Deployment Workbench revisions for deprecated content
  • Enhanced accessibility within the Deployment Workbench
  • Revised lists of time zones, regions and languages in the Deployment Wizard
  • Removed Start menu shortcut for “Remove PXE Filter”
  • Several MVP recommended fixes for Windows Updates, password handling, and PowerShell cmdlets
  • Added missing OOBE settings to Unattend.xml
  • Unattend.xml default screen resolution changed to allow for automatic scaling
  • Updated task sequence binaries from System Center 2012 R2 Configuration Manager SP1
  • New GetMajorMinorVersion function for integer comparison of Windows version numbers

We are still working to update the MDT documentation on TechNet, so in the short-term will use this blog to share any additional necessary information regarding this release.

Please continue to use the MDT Connect site to file bugs and feedback.

— Aaron Czechowski, Senior Program Manager

Comments (136)

  1. DaGbyte says:

    Bravo!

  2. Anonymous says:

    As announced on the Microsoft Deployment Toolkit team blog , MDT 2013 Update 1 is available for download

  3. Rafael Vazquez says:

    Awesome. Thanks!

  4. Raja Ram says:

    wow thks!

  5. Anonymous says:

    News from Aaron Czechowski that many have been waiting for – the MDT 2013 Update is now available for

  6. dougkl says:

    Congratulations!

  7. Jerry L says:

    Thank you

  8. Young Pae says:

    OMG, thanks

  9. Thomas Marcussen says:

    Great! 🙂

  10. Sven says:

    Awesome!!

  11. stephan says:

    Now all our deployments fail with "SelectSingleNodeString(CommandLine) Missing Node." Actually OS deployment itself is working, but no applications get installed.

  12. Todd Meyers says:

    Is anyone else having a problem adding MDAC components and talking to the MDT database? And no, McAfee is not installed on the server. From DISM.log:

    2015-08-18 00:54:45, Info CBS Reporting package change for package: WinPE-MDAC-Package~31bf3856ad364e35~amd64~~10.0.10240.16384, current: Absent, pending: Default, start: Absent, applicable: Installed, target: Installed, limit: Installed, hotpatch status: StillGoing,
    status: 0x0, failure source: Not Applicable, reboot required: True, client id: DISM Package Manager Provider, initiated offline: True, execution sequence: 22, first merged sequence: 2, reboot reason: REBOOT_NOT_REQUIRED, RM App session: 0, RM App name: N/A,
    FileName in use: N/A, release type: Feature Pack, release quality: final, OC operation: False, download source: 0, download time (secs): 4294967295, download status: 0x0 (S_OK), Express download: False, Download Size: 0
    2015-08-18 00:54:46, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800706BE
    2015-08-18 00:54:46, Error DISM DISM Manager: PID=3820 TID=3428 Failed to get the IDismImage instance from the image session – CDISMManager::CloseImageSession(hr:0x800706ba)

  13. stephan says:

    I found that all applications with a batch file as installation command fail with code 1. Tried to replace the command "batchfile.cmd" with "cmd /c batchfile.cmd", but same result. Applications with exe files as installation commands are working though.

  14. Mathieu says:

    For the MDAC problem, see
    https://keithga.wordpress.com/2015/08/17/mdt-2013-uberbug01-mdac-and-the-fast-machine/ for possible workaround until MSFT release a fix

  15. stephan says:

    Yes, there is obviously a bug. When I specify a batch file as installation command (whether directly as "file.cmd" or via "cmd.exe /c cmd"), the command is executed in C:WindowsSystem32, not in the application directory. In both cases, Procmon shows
    that BDD.EXE creates a new process "cmd.exe /c file.cmd", and cmd.exe then searches the file in the path (c:windowsfile.exe, c:windowssystem32file.exe etc.), but not in the application directory.

    As a workaround, I created SFX archives for these directories, so that I can use an EXE file.

  16. paulo says:

    Hi,

    After update when i try to uptdate the Boot Images i am getting this error:

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

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

    Building requested boot image profile.

    System.Management.Automation.CmdletInvocationException:
    Unable to open the specified WIM file. —> System.Exception: Unable to open the specified WIM file.

    —> System.ComponentModel.Win32Exception: The system cannot find the path specified

    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()

    Anyone solve this?
    thx

  17. stephan says:

    @Paulo, have you installed the latest ADK?

  18. yannara says:

    Does it have official In-Place Upgrade TS template for Windws 10?

  19. Martin says:

    I am assuming that you have installed the AIK 10?
    Have you opened the Deployment Workbench "As Admin"?

    I managed to update my boot WIMs without issue and I just installed over the top of AIK 8.1 and MDT 2013. Previously I uninstalled older versions and just kept the folder structure of the deployment share.

  20. Martin says:

    Hmm, very odd, I am now unable to regenerate the Boot WIMs myself. Was able to before and now the process is unable to mount the WIM from the AIK.

  21. Martin says:

    And can again now. I closed and reopened the workbench, don’t know if maybe the previous update didn’t unmount the WIM properly or something.

  22. paulo says:

    Thank-you ALL
    Mean-while i solved.
    I make a mistake and had installed WDK instead ADK.
    Its working now

  23. Gabriel says:

    Awesome, super , great. Thanks a lot Deployment Team

  24. mammut62 says:

    Same problem for me, all applications give return code 1. I use batch files like "install.cmd" (see Stephan’s post and technet thread:

    https://social.technet.microsoft.com/Forums/en-US/8b471021-4a84-4366-9467-acf6d03cba38/mdt-2013-update-1-batch-files-are-searched-in-cwindowssystem32-not-in-application-directory?forum=mdt )

  25. Bryan says:

    @yannara

    I believe that is coming in Configuration Manager 2016.

  26. UZabatty says:

    Finally! "Added missing OOBE settings to Unattend.xml"

  27. Artur says:

    During the install Windows 10 a have: The program can’t start because MSVCP120.dll is missing from your computer!!!

  28. Todd Meyers says:

    Thanks @Mathieu for the MDAC problem link. Now how to obtain this "private fix" from Microsoft. :/

    New bug–my first validation step was to make sure MDT 2013 Update 1 broke nothing in the Windows 8.1 build process. However, running my Windows 8.1 build TS now gives me an error during minisetup:

    "Windows Could Not parse or process unattend answer file for pass [oobeSystem]. The settings specified in the answer file could not be applied."

    Which is bizarre, seeing as how I haven’t changed the unattend.xml file at all.

  29. Todd Meyers says:

    Follow-up from previous post. Anybody else getting Windows 8.1 deployment failures after upgrading? From setupact.log:

    2015-08-18 02:15:56, Info CBS Failed to open package file: \?C:windowsServicingSessions4980_2288056687.xml [HRESULT = 0x80070002 – ERROR_FILE_NOT_FOUND]
    2015-08-18 02:15:56, Info CBS Failed to read in xml content [HRESULT = 0x80070002 – ERROR_FILE_NOT_FOUND]
    2015-08-18 02:15:56, Info CBS Failed to load persisted information for session: 4980_2288056687 [HRESULT = 0x80070002 – ERROR_FILE_NOT_FOUND]
    2015-08-18 02:15:56, Info CBS Failed to load session: 4980_2288056687 [HRESULT = 0x80070002 – ERROR_FILE_NOT_FOUND]
    2015-08-18 02:15:56, Info CBS Startup: Failed to initialize exising session: 4980_2288056687 [HRESULT = 0x80070002 – ERROR_FILE_NOT_FOUND]
    2015-08-18 02:15:56, Info CBS Startup: delete session as corrupt since it fails to load, Session: 4980_2288056687 [HRESULT = 0x80070002 – ERROR_FILE_NOT_FOUND]
    2015-08-18 02:15:56, Info CBS Retrieved original failure status: 0x00000000, last forward execute state: CbsExecuteStateStageDrivers

  30. Zach says:

    WDS doesn’t list the new boot images created from MDT, is there a way to get them to show up when I pxe boot a computer to select a boot image?

  31. Kevin says:

    Ok, I update MDT and I tried to update my boot wims and I get this error:

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

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

    Building requested boot image profile.

    System.Management.Automation.CmdletInvocationException: Unable to open the specified WIM file. —> System.Exception: Unable to open the specified WIM file. —> System.ComponentModel.Win32Exception: The system cannot find the path specified
    — 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()

  32. Kevin says:

    When I go into the Windows PE properties tab it breaks:

    FX:{ffb8695a-66b4-4929-abb6-15cb8bd2ae3d}

    Could not find a part of the path ‘C:Program Files (x86)Windows Kits10Assessment and Deployment KitWindows Preinstallation Environmentx86WinPE_OCs’.

    System.IO.DirectoryNotFoundException

    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
    at System.IO.FileSystemEnumerableIterator`1.CommonInit()
    at System.IO.FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler, Boolean checkHost)
    at System.IO.Directory.InternalGetFileDirectoryNames(String path, String userPathOriginal, String searchPattern, Boolean includeFiles, Boolean includeDirs, SearchOption searchOption, Boolean checkHost)
    at System.IO.Directory.InternalGetFiles(String path, String searchPattern, SearchOption searchOption)
    at Microsoft.BDD.Core.DeploymentTools.GetFeaturePacks(String platform, String deploymentSharePath)
    at Microsoft.BDD.Workbench.DeployWindowsPE.RefreshData()
    at Microsoft.ManagementConsole.SnapInBase.ProcessNotification(Notification notification)
    at Microsoft.ManagementConsole.NamespaceSnapInBase.ProcessNotification(Notification notif)
    at Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification)
    at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification)
    at Microsoft.ManagementConsole.Executive.SnapInNotificationOperation.ProcessNotification()
    at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)

    I installed the Windows 10 ADK, updated MDT 2013 to update 1, and then updated the folder for the share. AAHHHHHHHHHHHHH!

  33. Kevin says:

    Nevermind, I did the samething as the other guy. I grabbed the WDK installer. IF YOU’RE HAVING THIS ISSUE YOU DIDN’T SCROLL DOWN FAR ENOUGH ON THE PAGE TO DOWNLOAD THE ADK.

  34. Rune3 says:

    "PowerShell is required to use the Deployment Workbench. Please install PowerShell then relaunch Deployment Workbench"

    Only problem is that Power Shell IS installed. Any suggestions?
    Using Windows 10 Professional.

  35. archetype22 psycosys nos says:

    uninstall powershell then star again.,got to windows toolprograms
    powerhell br it star again.

  36. CheleCuca says:

    Thank you!!!!!!

  37. archetype22 psycosys nos says:

    to install maybe the need to do it in safe mode with networking,in case of failsafe fireing itself,.

  38. archetype22 psycosys nos says:

    workbench first download

  39. archetype22 psycosys nos says:

    remenber you can only open the program in out safe mode an install it but you can download it in safe mode.

  40. Makaveli1976 says:

    Can’t wait to try this update!

  41. Josh says:

    @Todd Meyers Did you ever figure out what was causing the "Windows Could Not parse or process unattend answer file for pass [oobeSystem]. The settings specified in the answer file could not be applied." error. I’m experiencing that too on my Win8.1 deploys

  42. Squeezer999 says:

    @Josh I am getting the same error. Hitting shift-f10 and running ipconfig shows the systems have a 169.254.x.x ip address

  43. Josh says:

    I found the cause. Check and see if you have plaintext passwords in your unattend.xml files. If you have obscured passwords, try changing to plaintext. In windows SIM go to tools > hide sensitive data and make sure its unchecked otherwise it will overwrite
    the plain text passwords with the obscured value. doing this fixed the issue for me. this is not ideal obviously, but I may find alternative ways of setting the administrator account password outside of the unattend file. you can set the password in customsettings.ini
    but obv its not obscured that way.

  44. Todd Meyers says:

    @Josh, thanks for that info. I do have obscured passwords in unattend.xml and to be honest I don’t remember how those are set (obviously some automated part of the process). After unchecking hide sensitive data did you have to reenter the admin password
    or manually edit unattend.xml or what did you do? It sure sucks to have an MDT update break something that was working. I’m spending all my hours working on getting Windows 8.1 working again and no hours on Windows 10.

  45. Steve says:

    Trying to use the Add Windows Feature role to install hyper-V platform and tools during OSD. The task completes successfully and Hyper-V gets installed. The problem I have is that the action of installing this breaks the task sequence and the TS doesn’t
    resume rather the system reboots into running windows. I have tried adding in my own reboot switch but it never gets to that state. The only way I have found around this is to have the hyper-v install as the very last step but that is not good because then
    I can’t run my health check script to validate the install before it exits the sequence. Anyway to get all of hyper-v to install during OSD and have the TS resume?

  46. veechee2 says:

    Todd Meyers:

    I just upgraded and am having the same issue with oobeSystem installing Windows 8.1. Looking at my log files and the unattend.xml file, here is what I think is happening:
    I set the admin password during lite touch installation, however, I have default password specified in my customsettings.ini that will be used if I don’t change it durning the lite touch wizard. What happened during install is the password I set in the wizard
    is getting injected into the unattend.xml file without being encrypted/hashed, yet the

     value is not being set to true, which would indicate it is not encrypted/hashed.  So I think Windows can't understand the password that is being passed.<br/><br/>--START SNIPPET--<br/><component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="<a href="http://schemas.microsoft.com/WMIConfig/2002/State">http://schemas.microsoft.com/WMIConfig/2002/State</a>"><br/>			<UserAccounts><br/>				<AdministratorPassword><br/>					<Value>UnencryptedPasswordEnteredInWizardAppearsHere</Value><br/>					<PlainText>false</PlainText><br/>				</AdministratorPassword><br/>			</UserAccounts><br/>			<AutoLogon><br/>				<Enabled>true</Enabled><br/>				<Username>Administrator</Username><br/>				<Domain>.</Domain><br/>				<Password><br/>					<Value>UnencryptedPasswordEnteredInWizardAppearsHere</Value><br/>					<PlainText>false</PlainText><br/>				</Password><br/>				<LogonCount>999</LogonCount><br/>			</AutoLogon><br/>--END SNIPPET--<br/><br/>I am going to try to re-run the installation now without changing the password in the wizard to see if it makes any difference...<br/><br/>If anyone knows how to overcome this issue permanently I appreciate the help!

  47. Jeff25 says:

    Not sure if this is a bug in MDT 2013 U1 but after deploying a new Windows 10 image to a clean drive (UEFI), the Recovery partition has a drive letter assigned. Any reason for this?

  48. veechee2 says:

    Todd Meyers:
    It appears to get ‘false’ to go away in unattend.xml you need to delete the password hashes that are in the file (in both AutoLogon – Password and UserAccounts – Password).

  49. veechee2 says:

    "Revised lists of time zones, regions and languages in the Deployment Wizard"
    Where can we find a listing of all of these? The wizard is no longer displaying the time zone I had selected in my customsettings.ini file (Singapore Standard Time). Instead it shows Pacific Standard Time.

  50. veechee2 says:

    "Yes, there is obviously a bug. When I specify a batch file as installation command (whether directly as "file.cmd" or via "cmd.exe /c cmd"), the command is executed in C:WindowsSystem32, not in the application directory. In both cases, Procmon shows
    that BDD.EXE creates a new process "cmd.exe /c file.cmd", and cmd.exe then searches the file in the path (c:windowsfile.exe, c:windowssystem32file.exe etc.), but not in the application directory."

    GAH this has broken almost ALL of my applications! I just deployed three comptuers and they got almost no apps, and most didn’t even create an error message!

  51. Anonymous says:

    Applies to: Windows 10   MDT 2013 Update 1 Now Available
    http://blogs.technet.com/b/msdeployment

  52. Allenpu says:

    There is no progress bar shows on screen when it’s at the step of Install Operating System.
    Does anyone meet this?

  53. veechee2 says:

    Really frustrated you released such broken software. Mucks the admin passwords and can’t install applications (both under Windows 8.1; can’t comment on Win 10 yet).

  54. cmiscloni says:

    MDT falure 5624: " Dism Error applying Image" after upgrade to Update 1.
    Try to install to another server with new Deployment Share but same problem !!
    🙁

  55. rajaram says:

    After Upgrading MDT 2013 U1
    Image Deployment Working fine
    Sysprep and capture is not working
    Able to select task sequence by running LiteTouch.vbs after no response
    When i tried LTISysprep.wsf manually and its not working.
    Help me on this!
    Thks in advance.

  56. cmiscloni says:

    After some investigations, seems to work only with Windows Source installation but not with old existing image capturing with old version of MDT 2013.

  57. richsmif says:

    right, lets get going and see what happens!!!

  58. aslakt says:

    I’m experiencing Application errors after upgrading from 2013 to Update 1.
    Anyone else?

    Event log entry:

    http://schemas.microsoft.com/win/2004/08/events/event"&gt;

    1000
    2
    100
    0x80000000000000

    291518
    Application
    XXXXXXXXXXXXXXXXXXX


    rundll32.exe
    6.3.9600.17415
    545045a2
    KERNELBASE.dll
    6.3.9600.17415
    54504ade
    e06d7363
    00014598
    ae4
    01d0da57485f56db
    C:WindowsSysWOW64rundll32.exe
    C:WindowsSYSTEM32KERNELBASE.dll
    8b30166a-464a-11e5-80d9-005056931861

  59. paulo says:

    Same here Capture Image not working.
    i get ZTI ERROR – Unhandled error returned by LTISysprep….
    (-2147024894 0x800700002)

  60. Igwemo Pielczyk says:

    DISM for imaging processes….Great Job guys 🙂

  61. richsmif says:

    Applying Operating System timer has gone – just sits there and then completes. Bit strange gives the feeling its crashed?

  62. richsmif says:

    Oh and after the "getting ready" screen now, I just get Windows could not complete installation, To install Windows on this computer, restart the installation.

    When you do, it just goes in a loop.

  63. Anyone know how to split the wim image? This was done automatically in MDT 2013 u1 preview release. No longer happening since updating to MDT 2013 Update 1. Is there a property that can be set in CustomSettings.ini?

  64. Raphael says:

    Got a problem with the capture …

    Windows Script Host
    Unable to find script :
    "\serverdeploymentshare$ScriptsLTICopyScripts.wsf"

    I’ve made another "capture" task and it’s working great ! I think that the "capture" task have to be rebuilt after the MDT 2013 U1 upgrade …

  65. Darrel says:

    Appears that during ztiapplications.wsf, the %deploydrive% variable is either not being set or used with my applicaton installs. This results in app install scripts being run in the wrong context and failing. With mdt2013, %deploydrive% was usually Z:,
    and with update1, it is not set at least during ztiapplications.wsf.

  66. Tried to file a bug report but the report form keeps crashing: LTIAPPLY.swf is missing a colon in /swmfile in the function ApplyImage . this is causing application of spanned images to fail.

  67. Darrel says:

    As others have mentioned, rolling back ztiapplications.wsf to version 6.3.8216.1000 resolved my command script app install mapping issue, as now %deploydrive% is utilized during this script.

  68. Jeff25 says:

    @Raphael: I had the exact thing happen to me as well with my capture TS and doing the same worked for me also.

  69. Matthew says:

    I have tried several times to do an upgrade (Running LiteTouch.VBS) from Windows 7 Enterprise x64 to Windows 10 Enterprise x64 and every time after it gets to the desktop and restarts I get a Blue Screen with "System_License_Violation" message. Anyone
    else tried and gotten this message?

  70. tony says:

    Matthew… Yes I’m getting the System License Violation as well when I run an in place client upgrade.

  71. Matthew says:

    Tony,
    Thanks! It’s good to know I’m not the only one. I’ll try and put in a bug report. If you happen to find a fix, I’ll keep checking this thread.

  72. Matthew says:

    Tony,
    My report got filed when I thought it failed. Here is the ID Number: 1688684

  73. tony says:

    Will do Matthew! Very frustrating problem. I’ve been trying different things all day to no avail. We use KMS in our org. The first boot after the upgrade everything works fine and Windows is activated. Subsiquent reboots produce the blue screen and System
    License Violation. I can recover to previous OS fine. Very strange. I can upgrade no problem from install media. Only happens using MDT 2013 Update 1 and upgrade task sequence.

  74. Bob Hyatt says:

    As mentioned, batch/command line problems. Customsettings.ini isn’t being processed properly, so task sequence based domain join ou’s are not working and finally, none of our VB scripts in various apps will write to a seperate log file,stored on the client.

  75. Brandon Mills says:

    I have a host of new problems after upgrading my deployment share. The main one is the application deployment bug for cmd scripts, which seems mindboggling that this somehow escaped the preview stage. I’m getting error code 1 and error code 87 on applications
    that deployed just fine under MDT 2013 without Update 1.

  76. Chris says:

    @ Matthew @ Tony
    I am also receiving the System Violation BSD. Please keep this thread posted if either of you have found workarounds.

  77. mike says:

    I’m having an issue with configuring a static IP on a VMware VM when booting up in the new PE. Seems like the EnableStatic WMI method is throwing an unknown error. I can manually set an IP address via netsh though. Here’s some of the BDD.log:

  78. Jeff25 says:

    @Bob, I’ve had this problem on the last few versions of MDT. It has to do with the "DeployWiz_SelectTS.vbs" file mentioned here:

    https://social.technet.microsoft.com/Forums/en-US/320aafee-07d2-4b96-9138-a902fec7edf5/mdt-2012-custom-rules-by-tasksequenceid-not-working-now?forum=mdt

  79. tony says:

    Will do @ Chris. So far I haven’t been able to figure out the License Violation Error.

    Discovered another problem using a drive letter variable in Advanced options of the Format and Partition task sequence. Doesn’t work if I create a command line task and add the variable to the Start in box. Worked fine before upgrading to U1.

  80. Turge says:

    Lou.. about not being to split the wim, I noticed MS added this to ControlSettings.xml: True

    Try setting it to false I guess…

  81. Max says:

    Per Task Sequence settings still do not work. Can this please be fixed?
    This is the best solution I have found for this:
    http://blog.mikewalker.me/2013/04/mdt-2012-use-different-settings-per.html
    I don’t see why we have to keep modifying DeployWiz_SelectTS.vbs to get this functionality.

    Microsoft, please add this to the next MDT update!
    Thank you.

  82. Jeff25 says:

    Rules are still not processing for me. I used a previous "fix" to get rules processing by using an older version of DeployWiz_SelectTS.vbs but this is causing me problems in in MDT 2013 U1 specifically with Capture User State. Is there a fix for getting
    rules processing again?

  83. Max says:

    @Jeff,
    Don’t drop in the old version of DeployWiz_SelectTS.vbs. Whatever fix you are using, you need to add the code by hand to the latest version of DeployWiz_SelectTS.vbs. The link I provided above is the best solution I found. But there are slightly easier ones
    out there, with less code to add.

  84. Todd Meyers says:

    Deploying Windows 10 to a Hyper-V VM, and the Format and Partition Disk step from a new Standard Client Task Sequence (the one that creates two partitions, an OSDisk using 99% free space and a Recovery using the remaining space) causes a TS failure. Replacing
    this with the Format and Partition Disk step from a TS created with MDT 2013 works just fine. Anybody else seen this?

  85. Anonymous says:

    Friday Five gives you the top five things you need to know for this week that happened in the world of

  86. Turge.. That worked. Setting SkipWimSplit in controlsettings.xml to "False" worked..Wim file is now splitting for media deployments. Thank you..

  87. Max says:

    @ Todd, I had the same thing happen in a VMWare Workstation VM. I just removed the Recovery partition and set the OSDisk partition to 100%.

  88. Jeff25 says:

    @Max, after you posted that link, that’s what I did so thank you for that. However, my next issue is USMT failing during scanstate. We redirect our User’s Documents, Music, etc folders to a network share so I want to ignore those during capture. I created
    a Config.xml and set USMTConfigFile=Config.xml in my rules but it keeps failing on a file inside of Documents for my domain account (which it should be ignoring I assume). I am logging in and firing off deployment as Administrator. My main problem is that
    I’m not sure where Config.xml actually needs to reside. Although I’m not sure this is the way to go about in the first place.

  89. Miroslaw says:

    Why was ltiapply.wsf ApplyImage function updated to use dism.exe instead of imagex.exe in version 6.3.8290.1000 (a.k.a. same as this blog’s reference). The use of dism to apply eliminates the progress reporting that the task sequencer showed during the
    Apply Image step. So the progress report being very important to me, I optioned to use imagex.exe (the version that shipped with MDT package) and see no issues applying any window’s WIM. Why was dism.exe switched to and not explained why? What am I missing?

  90. Miroslaw says:

    Please don’t say that imagex.exe is getting deprecated and then include both 32/64 bit binaries in the MDT latest package. If you are removing imagex.exe then add progress reporting to dism.exe and the ability to dump in XML format a header of a WIM file,
    please!

  91. Todd Meyers says:

    @ Miroslaw, I totally agree in terms of the missing functionality. ImageX has been deprecated, that is the reason for dropping it and switching to DISM. There was also a bug in ImageX during WIM captures where it essentially hung for several minutes and
    therefore took much longer than is should. I’m on your side, but those are the technical justifications. They need to add the progress awareness to DISM.

  92. @Jeff says:

    I think sysinternal’s procmon would go a long way in terms of answering where that config.xml file needs to reside. Run your workflow that causes the failure while capturing the file events and perhaps networking as well and search for config.xml. This
    should lead to the event itself and you might see failure indications near by in the trace as to why.

  93. Horst2 says:

    How do I deploy Windows 10 Professionell with MDT? It only let me Import Windows 10 Enterprise.

  94. djstead says:

    Have upgraded to MDT 2013 update 1 and now getting error when click on OS Info in most ‘Post OS task Sequence’ tasks, but not all tasks, seems that the oldest ones are working, newer ones are not???. If I create a new task sequence using ‘Post OS task
    Sequence’ template, I can create the sequence but again the OS info tab on task produces error below.

    FX:{ffb8695a-66b4-4929-abb6-15cb8bd2ae3d}
    Object reference not set to an instance of an object.

  95. SUSD says:

    After updating to 2013 update 1, our OU selection no longer works. Indicates "Invalid OU format (must start with OU=)". We have the domainoulist.xml listing our OUs. It doesn’t seem to be working with SUSD it does work with ou=xxx. It did work prior to
    updating.

  96. SUSD says:

    After updating to 2013 update 1, our OU selection no longer works. Indicates "Invalid OU format (must start with OU=)". We have the domainoulist.xml listing our OUs. It doesn’t seem to be working with "DomainOU Value=" it does work with "DomainOU". It
    did work prior to updating.

  97. EyesHalfOpen says:

    Have an issue loading the DISM v3.0 CMDLET Module for Powershell, withing Powershell 5.0. The module, and it’s cmdlets appear, however importing the module throws a fileloadexception on Microsoft.Dism.Powershell.dll or one of its dependencies.

  98. KevSchu says:

    Ever since updating to 2013 U1, Ref image creation using MDT 2013 u1 appears to be working fine. However during deployment using SCCM + MDT the OSDJoinAccount is not setting, and computers are not joining the domain.

    Setupact.log shows as some random string of characters

    Using SCCM 2012 R2 SP1 CU1 + MDT 2013 U1. ADK10, WinPE10, USMT5

  99. justin_ms says:

    Batch file path issue, error 87 on bundles, WSUS error 9902 (applies patching once, does not do subsequent patches). Have rolled back. Product is not release quality.

  100. An Vo says:

    In my environment, I install MDT 2013 and ADK for windows 8.1, everything work OK.

    After I upgrade to MDT 2013 update 1 and ADK for windows 10

    During the deployment process, 2 errors were reported:

    Failure (5624): 87: Run DISM: /Apply-Image /Image-File:"\ts-wdsreminstimageswindows10install.wim" /index:1 /ApplyDir:W: /SWMFile "\ts-wdsreminstimageswindows10res.rwm"
    Litetouch deployment failed, Return Code = -2147467259 0x80004005

    After that, I press F8 and run from command line with the correct command as follow:

    DISM: /Apply-Image /Image-File:"\ts-wdsreminstimageswindows10install.wim" /SWMFile:"\ts-wdsreminstimageswindows10res.rwm" /index:1 /ApplyDir:W:

    and the operation completed successfully

    How can we correct this in MDT 2013 update 1 ?

    Regards,
    An Vo

  101. Anonymous says:

    This post is to serve as the release notes and known issues list for the current release of MDT 2013

  102. An Vo says:

    When I install MDT 2013 Update 1 and ADK for windows 10 on new server. The same error as above.

    Wish MDT Team working on this bug soon.

    Regards,
    An Vo

  103. Spanned image says:

    An Vo there is a bug in the ltiapply.wsf that applies spanned images in MDT 2013 update 1. Search for /SWMFILE and remove the space and add a colon so it looks like this /SWMFILE: . that should fix the issue until it is resolved. There is a bug logged
    on this on connect if you’d like to go vote on it.
    https://connect.microsoft.com/ConfigurationManagervnext/Feedback/Details/1692057

  104. Zackis says:

    Does the MDT 2013 Update 1 replace WDS in 2012 or 2012 R2? Will it still allow PXE booting ( booting from the NIC) or is there some other option available?

  105. Max says:

    MDT and WDS are two different things. WDS is a role within Windows Server. But yes, MDT and WDS integration is still there and PXE booting is definitely supported.

  106. Truong an vo says:

    @Spanned image: thanks for your response.

    After I edit file LTIApply.wsf, It work ok, but the Deployment process do not display process bar (%) as the previous version of MDT 2013 , it only display apply image …

    Could we correct this issue ?

    Regards,

    An Vo

  107. Max says:

    @Truong an vo, it cannot be done at this time. DISM does not provide progress output. They requested the Windows team to add that functionality to DISM.

  108. Stefan says:

    Here is a more detailed list of some specific changes in this release:
    Improved support for split image files (.swm)
    Known Issues:
    Split image files do not apply

    Really?

  109. Surbhi says:

    Sysprep is breaking the start menu for all users except the account from which sysprep was run. So, start menu doesn’t launch anymore in other user accounts after sysprep.
    Anyone facing this issue? Any suggestions please? I tried a powershell command I found on blogs to fix it, but it didn’t work!

  110. Jeff25 says:

    Can anybody else confirm CopyProfile in Windows 10 is broken? Cortana is missing and the desktop folder for all users in Quick access points to the Administrator profile if I set CopyProfile=True in my TS. This is incredibly frustrating and has halted
    any rollout I was planning.

  111. maxim says:

    After updating all my task sequences fail on the oobe pass stating they can’t decode the admin password.
    Nothing has to these unattend.xml files.

    Has this update changed the ways MDT (de)codes hashed passwords and is there action required to get this corrected?

  112. PauloV says:

    Hello,

    I am capturing an image and at the end I am getting 2 warnings.

    Operating System deployment completed successfully

    During the deployment process 0 errors and 2 warnings were reported

    Details…..

    Unable to create webservice class
    Unable to create webservice class

    Any ideas

    Thank-you
    regards

  113. Anonymous says:

    208 Microsoft Team blogs searched, 45 blogs have new articles. 115 new articles found searching from

  114. Rick says:

    A very stupid question, but I feel the need to ask…going to the Update 1 which allows for Win10 deployment, it still also allows Win7 and 8.1 deployment as well, correct? I want to make sure that this edition isn’t strictly for 10 only.

  115. Mirfster says:

    @ Justin_MS: For the Error 87, you should reference "http://blogs.technet.com/b/msdeployment/archive/2015/08/25/mdt-2013-update-1-release-notes-and-known-issues.aspx".
    There is a workaround/fix for this.

    Regarding "WSUS Error 9902 "; I was seeing this as well. Ended up being caused by the Windows Defender Patches/Updates in my WSUS. Since we use SEP (and it disables Defender), I simply "Declined" all of the Defender Updates in WSUS. This seemed to get me through
    without issue.

    If you do required Defender, then you may have to have it install those patches prior to the updates being installed. Not 100% sure, but give it a whirl.

  116. Mirfster says:

    I see a lot of repeated questions/issues that have been addressed/identified at "http://blogs.technet.com/b/msdeployment/archive/2015/08/25/mdt-2013-update-1-release-notes-and-known-issues.aspx".
    Would be nice if the blog was updated to include that link or any other pertinent ones to help.

  117. Surbhi says:

    Discovered that disabling windows firewall service was breaking the start menu. Enabled service, and start menu works just fine!

  118. Antrhony D. says:

    Hi all, On the new Windows 10 upgrade task , I encounter an error in the upgrade goes well up but after restart MDT displays a message "you must be running with administrator rights, the deployment cannot proceed" do you have a solution? or tips … thanks
    in Advance

  119. @Antrhony D. – that is an issue that we’ve seen as well, but I haven’t added to the list yet. It’s because the script expects to be elevated but can’t in this instance. It’s a non-fatal error, just means that you won’t seen the final summary.

  120. Bård Witzø says:

    I had the same 9902 error on WSUS updates for Defender. After the image is captured it’ll keep looping on Windows updates for Defender. I ended up Declining one update in WSUS which solved the whole problem –> Definition update 1.195.3530 for Defender

  121. alfred says:

    I am getting error: ZTI Error – Unhandled error returned by LTIApply: Invalid procedure call or argument (5)

    Can anyone help me?

    full details here:

    https://social.technet.microsoft.com/Forums/en-US/f1f7bf12-c8df-4b4c-be59-e4fab814a0dc/mdt-2013-update1-8298-zti-error-unhandled-error-returned-by-ltiapply-invalid-procedure-call-or?forum=mdt

  122. Mario F says:

    Cross posted: Is there a repository for the original version of MDT 2013? As of right now, the download link is dead; I can only download 2013 Update 1. Due to all the issues, I only want to put Update 1 in my dev environment as I have a working MDT 2013
    deployment using DFSr working as intended.

  123. young says:

    The link to:
    https://connect.microsoft.com/ConfigurationManagervnext/MicrosoftDeploymentToolkit does not work for me. Is there permission need or profile need to be created?

  124. anon-a-mouse says:

    You guys can’t seriously expect people to start using update 1 in a production environment, right? I mean, this is riddled with bugs – I have enough bugs to workaround in 2013 already! Please fix all of these bugs and release update 2 soon!

  125. facebook says:

    application directory. In both cases, Procmon shows that BDD.EXE creates a new process "cmd.exe /c file.cmd", and cmd.exe
    http://www.google.com">facebook

  126. facebook says:

    As a workaround http://www.google.com">facebook

  127. Rob says:

    Anyone still having issues with a failing deployment share update on 2012R2? Just tried it and it bombed on me.

  128. Morne says:

    I must say way to many bugs in the new build cannot capture ens. So company said sorry we will not be deploying windows 10 because if this have that many bugs just think of all the bugs in windows 10 .So Ms fix the problems so that i can do my job supporting
    your Software.

  129. BillC3 says:

    If your deployment share update is failing, try un-ticking ‘MDAC’ in the deployment share WinPE components section.
    Fixed my problems anyway.

  130. will this work for Server 2016? says:

    will this work for Server 2016?

  131. raidzero says:

    Has anyone ran into windows 10 deployemnt were the video card drivers are disabled and the error code is 12 (resources are not avialable) weird thing is that if I run the install manually everything is fine. and I have not found any answers into this issue

  132. Radizero says:

    Has anyone ran into windows 10 deployemnt were the video card drivers are disabled and the error code is 12 (resources are not avialable) weird thing is that if I run the install manually everything is fine. and I have not found any answers into this issue

  133. Rob says:

    "If your deployment share update is failing, try un-ticking ‘MDAC’ in the deployment share WinPE components section. Fixed my problems anyway."

    Nope, Still bombs, have the output, but don’t know of any way to post it in here-Long File

  134. Rob says:

    OK, Scratch that last posting, I got it to work. Thanks BillC.