MDT 2013 Update 1 private – What’s new!

On Friday Microsoft released a quick update to the MDT 2013 Update 1 Beta.

Within the script it’s being called 6.3.8231.Private

Overall there are just a few small script changes, but one big

What’s new

  • Client.xml and StateRestore.xml – Removed hard coded references to build 6000 ( Server.xml was fixed for the first Beta, but somehow these files got missed).
  • Sysprep.wsf – Code added to properly distinguish between Windows above and below Build 6000. This is strange to me, since MDT 2013 only supports Windows 7 and above, why add *EXTRA* code to support XP?
  • ztigather.wsf – Code added to distinguish between Windows 5.0 vs 6.0 by checking for build number 6000.
  • ZTIUtility.vbs – Whoops, Bug! While modifying the version in the header (line 10), the MDT team forgot to modify the version on Line 40, meaning that all the bdd.log files will reflect version “<version>” instead of a real number, go ahead and copy the version from Line 10 and add to line 40. The MDT team added some new code to support parsing of build and revision numbers.
  • ZTIPreReq.vbs – This change is a concern. Looks like the MDT team added code to handle processing the Windows Script Host Version number. In XP it was 5.6, in Windows 7 through 8.1 it’s 5.8, and now in Windows 10 Build 10041 it’s 5.12, for those of you have been following along with the 10.0 > 6.3 and the 10041 > 7600 version number problems you can see that there will be problems here as well since 5.6 > 5.12. However the fix may have some unintended consequences, as the author also changed the version check from 5.6 to 5.8, meaning that it should fail on any OS *Before* Windows 7 and Server 2008 R2. This script, as you may recall is used to verify the OS Version within Litetouch.vbs. The unintended consequence is that it should block running Litetouch.vbs from Windows XP, Vista, 2003 and 2008 (R1), meaning you can’t refresh *from* these OS’es.


OK, let’s check the MDT fix scorecard to see what they have addressed, and what they did not.

  1. Perhaps the biggest missing component is a new task sequence for the new Windows 10 “OS Upgrade”. There have been several blog posts on the subject, so I would have expected to see it by now.
  2. .\Templates\Server.xml has a fix for ImageBuild > 6 in Sysprep, but .\Templates\Client.xml is missing that fix.
  3. Still a lot of XP and Vista legacy code in LTIApply.wsf and LTISysprep.wsf.
  4. Readers of this blog may recall my fix for LTIApply.wsf and split WIM’s. Johan has mentioned some concerns about the performance here.
  5. Only minor fixes to ZTIWindowsUpdate.wsf. I have several other updates on my blog.
  6. I have a minor quibble about the new Function GetMajorMinorVersion. It’s not a function, it’s a Sub since it does not return any values. I would have preferred that the function return the Major and Minor OS version as a Float.
  7. I have 20 or so bugs on Connect, and so far I can see only the split wim fix in the Preview.
  8. Although MSFT has fixed several bugs related to the version number jump “6.4” > “10.0” they didn’t fix any build number problems “6000” > “10007”.
  9. I can see that Microsoft added some entries for ServerManager.xml, but they copied the Windows 10 entries from above (see how Roles ID 12 is repeated twice), I wrote a script a while back to programmatically generate the ServerManager.xml file from the OS itself. You can see my changes on MDTEx.
  10. Would also like to see some LTI support for Windows 10 new Component Package model.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s