MDT 2013 Update 1 re-released (build 8298)


As noted in my previous post, given the number of issues with the original build of MDT 2013 Update 1 (8290), we have released a newer build (8298) to address many of these issues. The Download Center is updated with the new build and is still considered MDT 2013 Update 1. Build 8290 is no longer available, no longer supported, and superseded by build 8298.

NOTE: it can take time for the files to fully propagate through the live downloads cluster, and to be refreshed on the Akamai caches. Please ensure the build version under Details is 8298. I have seen the updated page on a non-internal system; it's there, just be patient. Use the time to review the release notes below!

The following issues are fixed in build 8298

  • Multiple drive partitioning issues are addressed by significant revisions to the Format and Partition Disk step (see release note below), including:
    • Upgrading to MDT 2013 Update 1 does not work for UEFI systems
    • An extra unneeded partition is created on both UEFI and BIOS systems
    • You cannot specify a custom partition layout containing a "Recovery"-type partition needed for UEFI systems
    • LTIApply error, "There is not enough space on the disk"
    • WINRE_DRIVE_SIZE from ZTIDiskpart.wsf is Too Small
  • Multiple issues related to XML processing:
    • Application bundles returning error 87
    • Selecting a keyboard locale in the Deployment Wizard
    • Deployments failing due to Unattend.xml errors
    • ZTIPatches returning error "Object required (424)"
    • Cleanup after image capture doesn't remove LTIBootstrap entry
  • Several issues with the Windows 10 in-place upgrade task sequence including:
    • The upgrade process ends with warnings "Unable to create WebService class"
    • The upgrade task sequence is available from Windows PE
    • After upgrade a System_License_Violation blue screen appears
  • Applications that use a command file start using System32 as the working directory
  • Spanned images cannot be applied

Below are the revised release notes and list of known issues. These inclusive lists supersede the previously published lists. New entries are marked with an asterisk (*).

 

Release Notes

TechNet documentation is not updated

The MDT product documentation published on TechNet is current as of MDT 2013; it has not yet been updated for MDT 2013 Update 1.

Do not upgrade from Preview to RTM

MDT 2013 Update 1 Preview should be uninstalled before installing the final MDT 2013 Update 1. Do not attempt to upgrade a preview installation or deployment share. Although the product documentation is not updated for MDT 2013 Update 1, the information on upgrading an installation still holds true.

Windows System Image Manager will fail to validate MDT Unattend.xml templates

The Windows System Image Manager (WSIM, a component of the Windows ADK used to create and modify unattended installation answer files) does not allow blank values which exist in the default MDT Unattend.xml templates. When using WSIM option, Validate Answer File, it will return validation errors, such as "The 'HorizontalResolution' element is invalid – The value '' is invalid according to its datatype 'HorizontalResolutionType' – The string '' is not a valid UInt32 value."

MDT removes blank values before injecting the file during deployment, so Windows always receives a valid XML answer file.

Integrating with System Center Configuration Manager

When integrating MDT with Configuration Manager, follow the version of the Windows ADK. MDT 2013 Update 1 only works with the Windows 10 ADK, so make sure it is used with a version of Configuration Manager that supports and also uses the Windows 10 ADK.

Image files larger than 4 GB are not split by default

Split image (.SWM) support is now off by default. It must be enabled by modifying %DeployRoot%\Control\Settings.xml with the following:

<SkipWimSplit>False</SkipWimSplit>

Using HideShell with Windows 10

The behavior of the HideShell option changed with Windows 10. Michael Niehaus explains this in great detail on his blog.

Changes to the Format and Partition Disk step *

The Format and Partition Disk step in the task sequence is now more closely aligned with the similar step in Configuration Manager; it will explicitly show all of the partitions that are created when the task sequence runs.

  • Backwards compatibility remains when using a task sequence that was created in a prior version of MDT. You should expect the same behavior as previously.
  • The DoNotCreateExtraPartition variable is deprecated. It should not be used with new task sequences (as the partitions are explicitly created by the task sequence step).

Changes to permissions of new deployment shares *

New deployment shares will now be created with more restrictive permissions. You should review these permissions and adjust accordingly for your access requirements.

Upgraded deployment shares are not modified, but the former default permissions are overly permissive. You should review the permissions on the share and directory and adjust accordingly for your environment.

 

MDT Known Issues

Static IP not restored when using media deployment

When doing a media deployment and using a static IP the static IP does not get restored.

Workarounds:

  • Modify Litetouch.wsf to enable MEDIA deployments (Keith Garner explains in this forum post)
    or
  • Add an extra Apply Network Settings action (alternative suggested by Johan Arwidmark on his blog)

Static IP not set in Network Adapter Configuration Wizard

When initializing a deployment in Windows PE and clicking Configure Static IP Address, if you uncheck Enable DHCP and enter static IP information, the following Network Settings Error will display:

WMI Function: Adapter.EnableStatic(IPAddress,SubnetMask) FAILURE: -2147467259

This warning may also be seen in the results screen and log files during a deployment.

Workaround: a static IP can be manually set from Windows PE using netsh, but otherwise there are no workarounds at this time.

UDI wizard does not handle the domain join account user name *

When using the OSDJoinAccount variable in CustomSettings.ini for a UDI task sequence, the wizard cannot be completed because the domain join account user name is encoded. The New Computer Details page will display an error, "User name format is invalid. Example is domain\user."

Workarounds:

  • Specify the OSDJoinAccount variable in the task sequence before the UDI wizard starts.
  • Alternatively, require the user to manually specify credentials in the UDI wizard.

Unable to browse for user data path *

In the LTI Deployment Wizard, on the User Data page, when selecting the Browse button, the Browse for Folder window does not display anything for selecting a path.

Workarounds:

  • Manually enter the path (do not browse).
  • Set the UserDataLocation variable in CustomSettings.ini.

The ZTIWinRE.wsf script and PrepareWinRE variable do not function properly *

If you specify PrepareWinRE=YES in CustomSettings.ini, Windows RE does not get enabled because the commandline is malformed.

The ZTIWinRE.wsf script is deprecated and should not be used.

Windows 10 language packs may not install *

We are still investigating an issue where Windows 10 language packs may not install during LTI.

Issues after successful Windows 10 in-place upgrade *

Following a successful upgrade to Windows 10:

  • Monitoring will continue to show the task sequence in progress until a user logs on.
  • A low rights user may receive an error at logon. This is a non-fatal error; the MDT script requires administrator elevation in order to display the final summary screen. Avoid this by using the variable, SkipFinalSummary.

 

Windows 10 Known Issues

The following are issues that are known to the MDT product team when doing Windows 10 deployments.

Issues with CopyProfile *

We are aware of reports of issues regarding the CopyProfile property in Unattend.xml. We have not been able to reproduce this issue, and are working with the Windows team to investigate further. If you have a reproducible issue with CopyProfile, please open a case with Microsoft Support to troubleshoot.

USMT LoadState fails on Windows 7 *

Using MDT 2013 Update 1 to deploy Windows 7 to an existing machine (refresh scenario), and using USMT 10 to capture and restore the user data will result in an error ("DismApi.DLL is missing") while restoring the user state on Windows 7. This is a known issue with loadstate; see https://support.microsoft.com/kb/3084782 for more information.

MDAC component fails being added to Windows PE

This is a known bug with DISM; it is external to MDT. DISM can sometimes fail to add the MDAC component to WinPE boot images. This seems to be a timing issue which most commonly occur when you are using SSD disks.

Workarounds:

  • Remove MDAC. On the deployment share properties, Windows PE tab, Features subtab, uncheck Microsoft Data Access Components (MDAC/ADO) support.
  • If you need MDAC for database connectivity, you can try updating your boot images from a system where the %TMP% directory is located on a non-SSD drive. This is not a guaranteed workaround, but has been seen to work

NOTE: we are also aware of reports of issues regarding the WMI component in Windows PE. We have not been able to reproduce this issue, and are working with the Windows team to investigate further. If you have a reproducible issue with Windows PE optional components, please open a case with Microsoft Support to troubleshoot.

Issues with Windows PowerShell in Windows PE

Windows PowerShell cmdlets in Windows PE may not function as expected. We are investigating this issue with the Windows team. If you have a reproducible issue with Windows PE optional components, please open a case with Microsoft Support to troubleshoot.

— Aaron Czechowski, Senior Program Manager

Comments (89)

  1. Anonymous says:

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

  2. Anonymous says:

    Looks like Aaron and team have been busy ramping up the latest build release of MDT 2013 Update 1 which

  3. Anonymous says:

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

  4. Anonymous says:

    Microsoft vient de republier une nouvelle version de Microsoft Deployment Toolkit (MDT) 2013 Update 1 en version v6.3.8298. La version précédente (v6.3.8290) avait été publiée un peu trop rapidement et comportait d.

  5. mmarable says:

    Excellent! Thanks Aaron and please thank the team for all the work they have done on MDT.

  6. OlavT says:

    Are MDT 2013 Update 1 (Build 8290) considered a preview that should not be upgraded to new version?

  7. regarding: MDAC component fails being added to Windows PE
    It also works perfectly fine when you use a remote connection from another machine, so by installing ADK and MDT on another computer and then remotely open the deployment share and then generate the boot image, it works.

  8. Max says:

    Thanks for the updated build! Will there be another build coming to address the remaining issues or is this the last build for 2013 Update 1?

  9. Jeb says:

    our deployment share has been upgraded with mdt 2013 update 1 preview back in may and we been using it since then. Can we still upgrade it without any problem since it’s stated: Do not upgrade from Preview to RTM?

  10. You can upgrade from 8290 to 8298. Task sequence template did change (Format and Partition Disk especially) so recommended to recreate task sequences.
    No more Update 1 builds planned. Update 2 coming later this year to coincide with some other releases in Q4.

  11. Anonymous says:

    Good news – an updatede version of the MDT has been released, here are the fixes that have been included

  12. Ian Wall says:

    For SMB providers that are using MDT to reimage consumer laptops etc with retail mages, is there any information on importing Windows 10 retail / OEM wim files? Doesn’t seem to work and customers are not going to want / be allowed to use Enterprise edition.
    I understand I’m not the only one coming across this.

  13. grundlichkeit says:

    I am so disappointed to say that the issue with the osdjoinaccount is still not solved.
    even more: I tried the workaround the past hour or so and it does not work either…

    I declared the variable OSDjoincaccount in the top of my UDI ts with the variable domainusername

    I then removed the variable from the customsettings.ini

    when I test this I don’t get the message: username format is invalid
    instead I can clearly see the osdjoinaccount as filled in by the TS var, but when I try to click next on this page of the wizard I get: usercredentials are invalid. please enter a valid username and password

    the only way it works is when i also declare the OSDjoinpassword variable/value in the ts, but this is not really desireable

    I do not want the operator either to manually fill in the account/password, this defeats the purpose of having a wizard…

    will this issue be corrected or what ???

  14. Delt says:

    I’ve installed this new version and still can’t capture. Before I had an error about "network not found".

    Now, I’ve got a "white screen" "Operating system deployment completed successfully".
    Inside the capture folder I’ve got no wim.

  15. geopar says:

    Updated to 8290, still issues to apply language pack offline during os deployment. Script which should run to apply computername (countrycode+macaddress) dont run, temporary computername (previous computername logged instead of new temporary in status
    messages). Someone any suggestions?

  16. geopar says:

    Sorry, Updated to 8298 mentioned in previous comment

  17. Dave says:

    The download for both x86 and x64 aren’t working for me – anyone else having download issues?

  18. yannara says:

    Is it possible to import In-Place Upgrade TS template from MDT 13 U1 to Confmgr?

  19. Awis13 says:

    How about disabling bitlocker on Windows 10 machines, as bitlocker version also is 10.something previous MDT was not able to disable bitlocker? Thanks. Or I have missed something regarding this?

  20. Anonymous says:

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

  21. pan123sel says:

    download is not working for both x86 and x64 as Dave pointed.

  22. pan123sel says:

    Just an update on download – i am able to download individual files using Click Here link next to each file. Checking both and selecting Try again does not download.

  23. bittin says:

    Nice upgraded at work today and saw this on Mikael Nyströms twitter 🙂

    hm Update 2 for MDT sounds fun :p

  24. For those that are having issues: blog comments are a tough way to troubleshoot. I recommend one of the following:
    – Post to the MDT forum (https://social.technet.microsoft.com/Forums/en/home?forum=mdt). MVPs and others in the community watch and respond to posts there
    – Call Microsoft Support – get a case open and get some professional help
    – File a bug on our Connect site (https://connect.microsoft.com/ConfigurationManagervnext/MicrosoftDeploymentToolkit). Not the fastest way to get help, but we do
    investigate everything that is reported.

    yannara – MDT task sequences cannot be imported into ConfigMgr. But you can get a sample task sequence for in-place upgrade for ConfigMgr 2012 R2 SP1 from the ConfigMgrTeam blog (http://blogs.technet.com/b/configmgrteam/archive/2015/06/16/revised-content-for-the-win10-in-place-upgrade-via-task-sequence-for-configmgr.aspx),
    and the ConfigMgr Technical Preview has had an integrated task sequence since TP1 in May (https://technet.microsoft.com/library/dn965439.aspx#BKMK_WIn10Upgrade). If you look
    at the three you’ll see some striking resemblences between them all.

  25. adam says:

    I think someone is broken in the unattend.xml, after the Setup Windows and ConfigMgr step runs and the system reboots, I get the error on bootup "Windows could not finish configuring the system. To attempt resume configuration, restart the computer"

  26. Omar says:

    The New Build 8298 Validation Error.

    When i try to update the DeploymentShare i do get a error saying: "One or more errors must be resolved before changes can be applied" and that the UNC Path : "invalid UNC Path specified". The path is correct, i even used the IP address instead of the Computer
    name, but still not working.. anyone who can help?

  27. Omar says:

    @Delt.
    I had the same problem when i capture it says it is deployed successfull but there is no image, the problem is in the CustomINI, i did had SkipCapture=Yes. Check if you have the same problem make it =NO.

    Hope it helps.

  28. @Omar – have you reviewed the share and folder permissions on the deployment share, as stated in the release notes?

  29. Omar says:

    @Aaron, Thanks i did it now and allowed Everyone Read/Write permission and it works well.. Thanks

  30. Aslak says:

    @Omar and @Aaron – I would still consider this to be a bug. It’s fair enough that you now need to specify share permissions to make deployments work. But the field specifying the UNC path should be able to validate, or at the very least demand that the
    share is valid before you are able to configure other options in the same GUI! You could end up configuring all sorts of stuff related to WinPE, just to be told off by the UNC validation… Yes you could keep the GUI open, fix permissions then apply again.
    But this is not helping anyone and will just cause headache. Why not use the credentials of the user that creates the Deployment Share instead of this "CREATOR OWNER", that clearly does not point to the user that created the share…?

  31. Jacques LEVAVASSEUR says:

    I always have problem when i tried to create a winpe boot image with adding winpi-wmi. I open a case in
    https://connect.microsoft.com/ (1816860). I add the dism.log. Only add in my DS WINDOWS 10 OS nothing special.

  32. 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

  33. ash says:

    UEFI devices still don’t work, you have to turn it to legacy to boot

  34. Mario F says:

    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.

  35. Jeb says:

    You can upgrade from 8290 to 8298. Task sequence template did change (Format and Partition Disk especially) so recommended to recreate task sequences.

    So… what happens when you have 8216 installed? can we just install it and then remake all the task sequences or i need to make a new deploymentshare from scratch?

  36. -veechee- says:

    RE: Changes to the Format and Partition Disk step in build 8298
    I looked at the new Task Sequence, and it assigns 99% of the disk to the OSDisk (C:), and then the remaining 1% to WinRE. On a 512 GB disk, that would mean around 5 GB goes to WinRE. Is that correct? Or will it still just use the variables in the ZTIDiskpark.wsf
    (499 MB for WinRE)?
    Also, the Task Sequence gives me the impression the WinRE partition gets created at the END of the disk, whereas before WinRE was the first partition on the disk. Is this right? If so, why the change?

  37. cmcdjm says:

    Hello Guys

    We have upgraded our MDT 2013 to Update 1 build 8298.

    And we have quite a few issues that we didn’t have before.

    We have some pretty simple task sequences we use to build images, one for each OS. Currently
    Windows 7×64, Windows 8.1×64 and Windows 10×64. Each os has a separate virtual machine in our VMware environment. We don’t capture the image in MDT since our deployment system requires and older WinPE to run (Capasystems.com).

    I pick the Syspreb task so it does what needs to be done at the end of the build. Shutdown the machine when it’s done, pxe boot into capa and then proceed to capture the image.

    This is pretty basic and has worked in the past.

    After the upgrade I boot from the litetouch ISO like we normally do and using a VMxnet3 driver make the connection to the share and this runs smoothly all the way to the sysprep part.

    When the machine is done syspreping it completely "drops all network connections" and the build "fails". See the attached pictures.

    I’m having a hard time figuring out why this happens – Any ideas?

    Tried with different drivers, old and new. Even tried running it on hyper-v but it yields the same results. Every task sequence was built from scratch since the format part was changed.

  38. campusdave says:

    I’m having a similar issue to cmcdjm. I’m running LiteTouch.wsf and attempting to do a full wim capture from my reference VM.

    We use MDT 2013 to deploy Windows 7 x64, Windows 8.1 x64 and now Windows 10 x64 and recently updated to the latest build (8298).

    Now when the machine is done with sysprep it drops network connection and the rest of the task fails.

    Would love any insight or advice on what we can do to get this working.

  39. afcastagna says:

    Regarding "MDAC component fails being added to Windows PE" known issue, I found that DISM also failed for all other added components during the "Update Deployment Share". The fix was to completely uninstall both Windows 10 ADK and MDT — then manually
    remove the left over folders, and reinstall both after a reboot.

    I believe it stems from not completely removing the Windows ADK 8.1 and MDT 2013 (without update 1) prior to installing the latest and greatest. I figured this would help others.

  40. adam says:

    The OEM TS generates an access deny error in the end of copying the image. No entry in the log.

  41. aarivers says:

    I’m having issues with making a Win10 Image using this update.I’m on a VM using the VLSC iso. I can start the lighttouch script and things look to be going well, then after it gets through the sysprep phase it loses the network connection and the script
    errors out before it reboots. When it reboots it never goes into the PE environment and never captures the image. I don’t get any failed deployment errors on reboot but it starts going through the initial setup because of sysprep.

  42. Amil Bansal says:

    For all those facing "Network connection lost post sysprep" issue… This is happening because sysprep is removing ALL the drivers (yeah! even the default ones) during the Generalize phase of sysprep! (Why Microsoft Why??!). To fix this issue in my deployments,
    I have added PersistAllDeviceInstalls tag (https://technet.microsoft.com/en-us/library/ff716298.aspx) in the Task Sequence’s Unattend.xml. The only downside to this tag is that even the
    custom plug and play drivers, installed before sysprep, will be retained which is undesirable for a reference image. While me and my team are contemplating if my clients will ever face an issue, I would ask Microsoft to give at least a reasonable justification
    to this drastic change in sysprep Generalize behavior or give us a better workaround. I don’t understand why even the default drivers are being removed…

    Thanks.

  43. Nisse says:

    So what about the problem with running *.bat files iread a while ago? Is this fixed or will i need to do silly things with my scripts to get around it ?

  44. Zach says:

    I am having an odd issue in our environment. I have a build and capture sequence that takes windows by itself images to a VM then updates with all windows updates and then captures the updated image. The issue I am having is when I deploy this updated
    image Once I get to the Apply Windows updates sequence of the task sequence after it restarts there. The computer name changes to DESKTOP-XXXXXXX instead of what was supplied in the Unattend.xml which it has all through the task sequence until it restarts
    from windows updates. Does any one have any idea on this?

  45. Zach says:

    Actually Upon doing some further research it seems that sysprep or something is working correctly as the computer will ignore the unattend.xml file and take the random name generated by the sysprep during the capture

  46. Code 46 says:

    Still got issue with running Command lines directly inside TaskSequences. Prob. same issue as Applications and System32. 🙁
    Or is it just me? 🙂

  47. Mikael says:

    I am having an issue with a specific model. A XPS 13 with a bad resolution 3200×1800. The wizard during the Win PE and after is not visible at 100%. Buttons are hidden, images doesn’t fit well etc ..
    Is there something to configure to correct this ?

  48. Code 46 says:

    Mikael, try these in CS.ini:

    ; == Auto-detection resolution ==
    BitsPerPel=32
    VRefresh=60
    XResolutiion=1
    YResolution=1

  49. vincent says:

    I am getting a error "Error while importing Microsoft Deployment Toolkit Task Sequence" with MDT2013 Update1 when I try to create a task sequence. Does anyone experience the same issue?

  50. Fredrik says:

    My version says that its updated, but i still get 5624 failure and the disk is small.
    It worked before, i am not sure before or after update, but i keep getting it i am unsure how to fix it.

  51. Cannot parse unattend.xml, says:

    windows-shell-setup. pass specialize. Any ideas? I have tried with and without product key. Checked company name,registered owner, organization and timezone all seem correct. The only one I am unsure about is DoNotCleanTaskBar.

  52. Bob Hyatt says:

    The issue with "Static IP not set in Network Adapter Configuration Wizard" Are there any plans to address this?

  53. Tom Erik Sundbye says:

    A comment to "grundlichkeit" posting.
    I ended up with the same issue with the UDI wizard not being able to add a computer to the domain with the OSDJoinAccount and OSDJoinPassword variables. However I was not able to get it working even when trying out the suggested workaround.

    But the odd thing was that I never upgraded MDT. I just upgraded ADK, from 8.1 to 10. And thats when the problem started. So I don’t think this is necessarily a MDT problem, as it worked when I used the WinPE bootimage from ADK 8.1.

  54. Sean says:

    I have a task sequence that keeps failing. It appears that the "Run this step as the following account" is not working. Anyone else have this issue?

  55. Dr Sylvester Benson says:

    GET YOUR PROBLEM SOLVE TODAY WITH MY PROFESSION IN ANY SPIRITUAL SPELL OR ANY KIND OF PHYSICAL BATTLE THAT NEED, MY NAME IS DR SYLVESTER AND THIS IS MY EMAIL FOR CONTACT (stbenson391@gmail.com) OR YOU CAN FOLLOW HIM UP ON FACEBOOK BY MY NAME (SYLVESTER E BENSON)
    ON FACEBOOK OR CALL ME ON MY MOBILE NUMBER +2348136090988, AM ALWAYS AVAILABLE TO RENDER YOU HELP WITH EXPERIENCE OF 32 YEARS IN SPELL CASTING AND HERBAL MEDICURE TO CURE ANY KIND OF DISEASE THAT YOU MAY HAVE, CONTACT ME ON ANY KIND OF ISSUES.

  56. GraceSolutions says:

    Hey MDT guys! I am pulling my hair out! I really need help! Over the past several years, I have been using MDT and have gotten pretty good at it, very in depth knowledge of the concepts. Anyways, my dilemma is the following. I cannot using custom scripts
    to join workstations to the domain as the last step in the task sequence. Previous MDT versions, worked great! I have written VbScript and Powershell variants, same result. I understand that certain values are Base64 encoded I have functions to decode them
    so that they can be passed through to the script. I will make an itemized list.

    Working Directory Path appears to no longer work in Command Line Step.
    Cannot copy files to C Drive root, it crashes task sequence.
    Can no longer pass credentials of user the authenticated to run the deployment in order to join the domain.

    I have been trying to debug for weeks and maybe I am missing something, but all the above things worked in MDT 2013, no update. What has been done to make those things not work when they probably did not need any tweaking?

  57. Craig Wilson says:

    Getting issues with adding additional nics where the variables for OSDAdapter1xxxxx are being applied to OSDISKyyyyyy

    Posted full details here:
    https://social.technet.microsoft.com/Forums/en-US/1bcfc6de-a45d-403a-b480-4ce7490e5013/deployment-fails-with-partitioning-error-when-trying-to-configure-multiple-nics?forum=mdt

    Blanking the values out in the Database configuration solve the issue, but doesn’t apply the NIC settings for the additional NICs

  58. WillMcG says:

    Issue I am seeing here when running on any modern device is that the deployment wizard when run from the litetouch.vbs will have scaling issues. running on standard resolution (1920×1080) looks fine buttons all align. running on Surface, or new Lenovo
    T450s. buttons and text all busted. I have applied the resolution fix, but this is not making any difference. is there some config in the litetouch.vbs that I can tweak to have it auto detect properly?
    Thanks.

  59. Mikael says:

    Thanks Code 46.
    I have the same problem buttons and images appears cuted, impossible to fix this at this point.
    When I watch the wpeinit.log, I can see that he try to put the resolution that I want (by default 1024*768) but it’s always failling.

  60. dustin.adam says:

    We are running into an issue with DirectAccess post MDT deployment: any computer we install Windows 10 on from an ISO (fresh install and in-place upgrade both), the clients can connect to our existing DirectAccess server as expected. However, every Windows
    10 install sourced from MDT (yes, I’ve installed the latest release) fails to establish a connection to our DirectAccess server with a DNS resolution error. At first I thought it was something wrong with our sysprep’d image of Windows 10, but even the in-place
    upgrade task exhibits the same issue, and there is no custom image in that binary, just the files from a Windows 10 ISO. I’ve run netsh traces and enabled verbose wfp logging, ultimately the issue seems to be that the Windows Filtering Platform is blocking
    DNS traffic. The only reason I’m positing the issue here is that we only see this problem on Windows 10 computers deployed through MDT 2013

  61. bklim says:

    I encountered an error "Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed" when I perform litetouch.vbs for upgrading Windows 7 to Windows 10. Did I have missed something? anyone can help?

  62. Brian D. Coryell says:

    Any way to enable on-screen keyboard for mdt thumbdrive deploy to Surface Pro 3? No usb kbd or cover kbd available, and no pxe possible (extenuating circumstances).

  63. rajaram says:

    Help me anyone on pushing windows updates through MDT while imaging by using downloaded updates and how to separate updates depends on OS(Win7, Win8 x64 x32 etc..).
    Thanks!

  64. Code 46 says:

    Mikael: Perhaps im wrong in this case, but have u tried to inject the Graphics drivers in WinPE boot image?

  65. Code 46 says:

    GraceSolutions: I have exactly the same problem. Have you find any better solution without rebuilding the actions inside TS? I had to hardcode the in the TS to get my commandlines to work without using the Working directory… Best regards

  66. Mikael says:

    Yes I inject the display driver during the WinPE, but it’s not very efficient :/

  67. join domain breaks task sequence says:

    I’m finding that when I try to join domain as part of the task sequence it just breaks the sequence and stays at the desktop without a failed error message. I have to manually restart the computer to continue with the rest of the task sequence.

  68. Nisse says:

    New ADK out for 10586? Do we need to install that it to deploy build 10586? some info please 🙂

  69. Rich says:

    Any news on being about to load Windows 10 1511 (Build 10596) into MDT as an OS?

  70. Travis says:

    Looking for an Update to the ADK, so we can start rolling 10586 through MDT 2013 Update 1.

  71. K says:

    Is there an updated ADK for 10586? If so, where is it?

  72. J says:

    According to a comment from Michael Niehaus on his blog (http://blogs.technet.com/b/mniehaus/archive/2015/11/11/removing-windows-10-in-box-apps-during-a-task-sequence.aspx#comments):
    The new ADK is available at the same download location as the old one (it replaced the old one),

    https://msdn.microsoft.com/en-us/windows/hardware/dn913721.aspx#adkwin10.

  73. AW says:

    For some reason, I am seeing Failure (5627): 14: Run DISM.exe Out of storage when deploying onto a VirtualBox guest only. Physical workstations and VMware virtual machines deploy without a problem. Any idea why that is and what a possible fix it?

  74. Bavo Bostoen says:

    New Windows 10 ADK Build 10586 – there are serious problems with it, do not install for the moment if you use MDT or SCCM. I do not understand why this is not mentioned on this blog also. But there is a post on the SCCM blog about this.
    Some more info can be found on Deployment Research site from Johan Arwidmark.

  75. Tony Pombo says:

    BUG: I reported this problem with 2013 and was surprised to see it still exists in the latest release.

    Line 86 in ServerManager.xml is:

    It should be changed to:

    Thank you.

  76. Tony Pombo says:

    I guess the blog doesn’t like the markup tags…

    BUG: I reported this problem with 2013 and was surprised to see it still exists in the latest release.

    Line 86 in ServerManager.xml is:
    <Feature DisplayName="Windows Media Center" Id="WindowsMediaPlayer" Parent="MediaPlayback" />
    It should be changed to:
    <Feature DisplayName="Windows Media Center" Id="MediaCenter" Parent="MediaPlayback" />

    Thank you.

  77. justin says:

    I am having an issue after upgrading to MDT 2013 Update 1. I have a few "Run Command Line" tasks that will not run anymore. They basically just use batch files that are stored on the local machine itself. For Example: I have it set to start in directory
    called "C:ITact" and in the Command Line input I put I enter "winact.bat" (this is a batch file that basically pulls the manufacturer license from the BIOS and activates it). This worked fine for MDT 2013 (before update) but now is not working for me. have
    tried using the the old ZTIapplications.wsf that people have mentioned that didn’t help. I am going to try just putting everything in the Command Line inout box and see if that helps, but other than that, does anybody have any suggestions?

    Thanks,

  78. tony says:

    MDT 2013 (and previous versions) included a CHM help file. Pressing F1 or clicking the help button loaded this file. Very, very helpful. Update 1 includes no help documentation. None at all. Not cool.

  79. Q80Warlock says:

    I’m getting so many issues Capturing and Deploying Window 10 1511 I guess we should wait for another release Update 2 anyone 🙂

  80. DreadfullyDespized says:

    The only really issue I am having with MDT 2013 Update 1 is the capture process is wonky. I have Task Sequences from MDT2013 that I brought over that still work and capture to the wim properly. When trying a newly created Task Sequence in MDT2013 Update
    1. It gives me a 2kb sized wim file. I get no errors in the task sequence at all when this happens.

    ZTIBackup.log
    Network store path set to: \huwds01DeploymentShare$Captures ZTIBackup 12/2/2015 4:01:49 PM 0 (0x0000)
    Backup file name already set to: W7X64-AUTO_12-2-2015.wim ZTIBackup 12/2/2015 4:01:49 PM 0 (0x0000)
    Using the backup path: \huwds01DeploymentShare$CapturesW7X64-AUTO_12-2-2015.wim ZTIBackup 12/2/2015 4:01:49 PM 0 (0x0000)
    Validating connection to \huwds01DeploymentShare$Captures ZTIBackup 12/2/2015 4:01:49 PM 0 (0x0000)
    Mapping server share: \huwds01DeploymentShare$ ZTIBackup 12/2/2015 4:01:49 PM 0 (0x0000)
    Already connected to server huwds01 as that is where this script is running from. ZTIBackup 12/2/2015 4:01:49 PM 0 (0x0000)
    Beginning backup of drive C: ZTIBackup 12/2/2015 4:01:49 PM 0 (0x0000)
    Event 41035 sent: Beginning backup of drive C: ZTIBackup 12/2/2015 4:01:49 PM 0 (0x0000)
    About to run command: "\HUWDS01DeploymentShare$ServicingX64dism.exe" /Capture-Image /CaptureDir:C: /ImageFile:"\huwds01DeploymentShare$CapturesW7X64-AUTO_12-2-2015.wim" /Name:"W7X64-AUTOCDrive" /Compress:MAX /ConfigFile:"\HUWDS01DeploymentShare$ToolsX64wimscript.ini"
    ZTIBackup 12/2/2015 4:01:49 PM 0 (0x0000)
    Command has been started (process ID 1828) ZTIBackup 12/2/2015 4:01:49 PM 0 (0x0000)
    Console > Deployment Image Servicing and Management tool ZTIBackup 12/2/2015 4:01:50 PM 0 (0x0000)
    Console > Version: 10.0.10240.16384 ZTIBackup 12/2/2015 4:01:50 PM 0 (0x0000)
    Console > Saving image ZTIBackup 12/2/2015 4:01:50 PM 0 (0x0000)
    Console > The operation completed successfully. ZTIBackup 12/2/2015 4:01:50 PM 0 (0x0000)
    Return code from command = 0 ZTIBackup 12/2/2015 4:01:50 PM 0 (0x0000)
    Successfully created image of drive C: ZTIBackup 12/2/2015 4:01:50 PM 0 (0x0000)
    Event 41037 sent: Successfully created image of drive C: ZTIBackup 12/2/2015 4:01:50 PM 0 (0x0000)
    Skipping drive D: because it’s not C: ZTIBackup 12/2/2015 4:01:50 PM 0 (0x0000)
    Skipping drive E: because it’s not C: ZTIBackup 12/2/2015 4:01:50 PM 0 (0x0000)
    Skipping drive X: because it’s not C: ZTIBackup 12/2/2015 4:01:50 PM 0 (0x0000)
    ZTIBackup COMPLETED. Return Value = 0 ZTIBackup 12/2/2015 4:01:50 PM 0 (0x0000)
    ZTIBackup processing completed successfully. ZTIBackup 12/2/2015 4:01:50 PM 0 (0x0000)

    I also previously had the not enough disk space errors. Once I changed my hyper-v vm from 40GB to 50GB it seemed to fix that issue. Hope this helps some.

  81. justin says:

    The Run Command Line task is still not fixed. Please note this for MDT 2013 Update 2. I have a few "Run Command Line" tasks that will not run anymore. They basically just use batch files that are stored on the local machine itself. For Example: I have
    it set to start in directory called "C:ITact" and in the Command Line input I put I enter "winact.bat" (this is a batch file that basically pulls the manufacturer license from the BIOS and activates it). This worked fine for MDT 2013 (before update) but
    now is not working for me.

  82. PhoenixATL says:

    Was there a fix for the CopyProfile issue? I tried searching around and have come up with nothing.

  83. ivan says:

    Does anyone else of problems with having to update the deployment share constantly?
    I update the deployment share, "burn" the ISO to a USB drive, boot from that drive practically everytime the username, password, domain is not accepted, even though everything is right. I scoot back to my place, update the deployment share again – hit enter
    on the other machine, and the previously entered credentials work again … I’m I doing something wrong?

  84. Vlad Stemate says:

    Hi Aaron, any ETA on the fix for Static IP not set in Network Adapter Configuration Wizard?

  85. val says:

    The Static IP issue is our main issue at the moment. As far as windows 10 MDT deployment goes. Software testing is still ongoing.