9/15 Update: We have re-released MDT 2013 Update 1. Please see this post with revised release notes and updated known issues.
The following information is deprecated, but kept live for historical reference.
This post is to serve as the release notes and known issues list for the current release of MDT 2013 Update 1 (v6.3.8290).
The list of known issues below provides a number of workarounds that are currently available to help unblock affected customers. We will revise the list as needed. Given the number of issues with this build we will release a newer build of MDT 2013 Update 1 in the next several weeks to address as many of these issues as we can. Watch this blog for more information.
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. 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.
Split image (.SWM) support is now off by default. It must be enabled by modifying %DeployRoot%\Control\Settings.xml with the following:
The behavior of the HideShell option changed with Windows 10. Michael Niehaus explains this in great detail on his blog.
- Recovery partition consumes the majority of the disk on BIOS systems
- LTIApply fails with DISM error 112, There is not enough space on the disk.
- Recovery partition is unnecessarily visible on both UEFI and BIOS systems
- You can’t specify a custom partition layout containing a recovery partition for UEFI systems
When doing a media deployment and using a static IP the static IP does not get restored.
- Modify Litetouch.wsf to enable MEDIA deployments (Keith Garner explains in this forum post)
- Add an extra Apply Network Settings action (alternative suggested by Johan Arwidmark on his blog)
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.
After successfully upgrading a system to Windows 10 the MDT monitoring fails to report information. You will see the following warnings:
Unable to create WebService class
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.
- 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 similar issues regarding Windows PowerShell and WMI components in Windows PE (as well as some functional issues with these components). We have not been able to reproduce these issues, and are working with the Windows team to investigate further. If you have a reproducible issue with these components in Windows PE, please open a case with Microsoft Support to troubleshoot.
Windows 10 upgrade task sequences are available when starting a deployment from Windows PE or on a non-matching architecture, however the in-place upgrade scenario is only supported when started from the full OS (it cannot be started from Windows PE) and from the correct architecture.
Workaround: Modify your upgrade task sequence properties to exclude client platforms that are not applicable. On the task sequence properties, General tab, select This can run only on the specified client platforms and then choose platforms that you want to target, for example, All x86 Windows 7 Client. This example will exclude Windows PE and Windows 7 x64 systems.
If you have an application that uses a command file (.cmd) as the installation command line it will be launched from C:\Windows\System32 instead of the application’s working directory.
Workaround: See the associated bug on Connect for sample edits to ZTIApplications.wsf.
Application bundles will successfully install but the following warning is logged in ZTIApplications.log:
SelectSingleNodeString(CommandLine) Missing Node.
as well as the following error:
Application <app bundle name> returned an unexpected return code: 87
Workaround: See the associated bug on Connect for sample edits to ZTIApplications.wsf.
Changing the keyboard locale in the Deployment Wizard will result in a script error:
Type mismatch: 'SetNewKeyboardLayout'
This error is non-fatal. Click Yes and continue.
- Specify the keyboard locale in CustomSettings.ini and hide this wizard page.
- Edit %DeployRoot%\Scripts\DeployWiz_LanguageUI.xml to remove
onchange="SetNewKeyboardLayout"from line 62.
Using the "Install Language Packs Offline" or "Install Updates Offline" step in an MDT-integrated task sequence in Configuration Manager results in the language packs or updates not injected, and the following errors in the ZTIPatches.log:
ZTI ERROR - Unhandled error returned by ZTIPatches: Object required (424)
This error is only seen in logs, the deployment appears to be successful otherwise.
Workaround: apply updates and language packs online
If you split a large image file to create .SWM file(s), then applying this split image file will fail.
Workaround: edit %DeployRoot%\Scripts\LTIApply.wsf, both lines 915 and 918, to add a colon and remove a space, for example on line 915 change:
sCmd = sCmd & " /SWMFile """ & sRWMPath & """"
sCmd = sCmd & " /SWMFile:""" & sRWMPath & """"
Do the same on line 918.
If you have edited unattend.xml and then start a deployment with the wizard page for administrator password enabled, or specified AdminPassword in CustomSettings.ini, the deployment will fail during Windows OOBE:
Windows could not parse or process Unattend answer file [C:\Windows\Panther\unattend.xml\ for pass [oobeSystem]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows=Shell-Setup].
Workaround: edit %DeployoRoot%\Scripts\ZTIConfigure.wsf lines 343 and 344 to append
PlainText. For example, on line 344 change:
oCurrent.parentNode.selectSingleNode("PlainText").text = "true"
oCurrent.parentNode.selectSingleNode("unattend:PlainText").text = "true"
Do the same on line 343.
Towards the end of a MDT-integrated task sequence deployment in Configuration Manager a Windows Script Host popup will appear with a message similar to the following:
Can not find script file "C:\LTIBootstrap.vbs".
(The drive letter may be different depending upon the specific scenario.)
Workaround: Script changes are possible but difficult and challenging. Johan Arwidmark provides an option on his blog (see Issue #2).
After capturing an image and rebooting back to the drive, autologon is still configured and an error will appear about LTIBootstrap is not found. This is a minor, non-fatal error that does not affect the captured image.
Workaround: Script changes are possible but difficult and challenging, especially given the minor severity of the issue.
A deployment fails with the following error from DISM:
Error: 87 (The parameter is incorrect)
With further detail in the dism.log:
Failed to get the filename extension of the image file
Workarounds: This is seen when the server name is only two characters, for example DC, such that the /ImageFile parameter is similar to the following:
"\\dc\DeploymentShare$\Operating Systems\Windows 10 Enterprise x64\sources\install.wim"
Use a deployment share on a server whose name is three or more characters.
If you must use a server with a two-character name, specify its fully qualified domain name in bootstrap.ini, for example