Partilhar via


MDT 2012 Update 1 has been updated

For those of you using ConfigMgr 2012, you may be interested in this.  When ConfigMgr 2012 Cumulative Update 1 was released, it was discovered that you could no longer create a new task sequence using MDT 2012 Update 1 and the “Create MDT Task Sequence” wizard.  When you tried, you would get an error like so:

Microsoft.ConfigurationManagement.ManagementProvider.SmsConnectionException: Failed to validate property Type. ---> System.Runtime.InteropServices.COMException: Failed to validate property Type.
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)
   --- End of inner exception stack trace ---
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters)
   at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)

A new MDT 2012 Update 1 download has now been released containing a fix for that:

https://www.microsoft.com/en-us/download/details.aspx?id=25175

From the text on that page:

MDT 2012 Update 1 version 6.1.2373.0 (Version 6.1.1 on this page) was made available for download on September 19, 2012 and adds support for System Center Configuration Manager 2012 CU1 and System Center Configuration Manager 2012 SP1 Beta. It can be identified as MDT build 6.1.2373.0 in the MDT Workbench console or in the installer program properties. This is the latest version and we recommend all users run the latest version when they can to ensure the smoothest experience during future upgrades.

So for those of you keeping track, the original MDT 2012 Update 1 release was build 6.1.2369.0, while the new release is 6.1.2373.0.  Other than this wizard fix and some documentation updates for ConfigMgr 2012 SP1 Beta, there are no other changes.  So if you are using ConfigMgr 2012, please download the new version, install it, and then repeat the “Configure ConfigMgr Integration” process to integrate the updated binaries into your ConfigMgr console.  (You don’t need to recreate any task sequences or change the MDT toolkit files package if you are already running MDT 2012 Update 1.)

If you are only using Lite Touch, you don’t need to upgrade, but there would be no harm in doing so.  Note that after doing this you would need to update your deployment shares, boot media, etc.

Comments

  • Anonymous
    January 01, 2003
    Yes, MDT 2012 Update 1 fully supports ConfigMgr 2012 RTM, ConfigMgr 2012 CU1, and ConfigMgr 2012 Beta.

  • Anonymous
    January 01, 2003
    Not presently, but Microsoft Support should be able to provide it to you.

  • Anonymous
    November 09, 2012
    Is there a location to download 6.0.2223.0?  Our deployment share is not upgraded and cannot be upgraded at this time, and I need to install the workbench on a new workstation. Thank you

  • Anonymous
    November 17, 2012
    The new version "6.1.2373.0" of "MDT2012Update1" I can install and integrate with "SCCM2012" no "SP1" "Ver 5.00.7711.0000" "Build Number 7711"? There are contraindications? or do I have to wait for the release of "Service Pack 1" "RTM" of "SCCM2012"? Scenario Production. social.technet.microsoft.com/.../bca7823c-1874-4cb3-8e4a-e2d511a09faa Thank you.

  • Anonymous
    January 08, 2013
    Hello Michael, I am seeing this issue with the latest version of MDT Update 1 and SCCM 2012 SP1.  Do you know if update 1 is compatibale with SCCM 2012 SP1?

  • Anonymous
    August 13, 2013
    Deben arreglar la implementacion por Multidifusion las versiones anteriores por lo menos lo soportaban con esta version pasa por alto la session de multidfusion.

  • Anonymous
    August 13, 2013
    Si es compatible asta con el sccm 2012 sp2 tambien lo probe con el sp1

  • Anonymous
    January 05, 2016
    I've already noticed 2 know issues with ConfigMgr 2012 Cumulative Update. http://goo.gl/Y8KCDb