Looking at a comparison of the files in MDT 2013 Update 2, here’s a quick overview of the changes in the scripts when compared with those in MDT 2013 Update 1:
- DeployWiz_Initialization.vbs. Change the task sequence filtering logic to only display upgrade task sequences from a running OS (not bare metal).
- DeployWiz_UserData.vbs. Fixed a bug that would blank out the user data location if UDDir and UDShare aren’t specified.
- Fixed a bug that causes static IP settings to not be restored for media-based deployments.
- Modified the upgrade handling logic.
- Only reboot when upgrade succeeds, not when it fails.
- Modified progress reporting logic when applying unattend.xml using DISM.
- LTIBootstrapUpgradeSummary.vbs. New script for in-place upgrade.
- LTICleanup.wsf. Added logic to copy new scripts for in-place upgrade.
- LTISysprep.wsf. Added logic to re-arm Office 2013 or Office 2016 activation, if either version is present.
- SetupComplete.cmd. Modifications to upgrade logic.
- SetUpgradeStatus.wsf. Removed no-longer-used script.
- SetupRollbackup.cmd. Modifications to upgrade logic.UpgradeSummary.wsf. Removed no-longer-used script.
- LTIApplyGPOPack.wsf. Added logic to apply a Windows 10 GPO pack (although there is no such thing).
- ZTIBde.wsf. Fixed bug with Windows 10 version checking.
- ZTIExecuteRunbook.wsf. Fixed bug with XML handling that prevented runbooks from being invoked or monitored.
- Fixed bug with Windows 10 version checking.
- Fixed bug with the handling of language pack CAB files with spaces in their path.
- Fixed progress reporting logic to handle new DISM progress output in the ADK for Windows 10 version 1511.
- Fixed issue where Pro SKU wouldn’t display high-end SKU features (changes in Windows 8 and above).
- ZTIWinRE.wsf. Fixed Windows 10 version checking.
So overall that’s fairly minor – primarily lower-impact bug fixes, and some desired improvements to the Lite Touch in-place upgrade process mentioned at http://blogs.technet.com/b/msdeployment/archive/2015/12/22/mdt-2013-update-2-now-available.aspx. A few other key fixes called out in that blog:
- Fixes to the task sequence logging. In MDT 2013 Update 1, the task sequence log went from very verbose to almost non-existent. With MDT 2013 Update 2, it’s back to very verbose.
- Fixes to default deployment share permissions – maybe still a little more secure that you would like, but at least the new security is functional.
- A better in-place upgrade experience.
Overall, this is a highly recommended upgrade for anyone using earlier versions of MDT (well, as long as you’re not still working with Windows Vista, or heaven forbid Windows XP).
Remember, before upgrading to MDT 2013 Update 2 make sure you have a backup of your existing deployment share. And if you are concerned about the potential impact, first upgrade a copy of your deployment share before upgrading the production one.