Freigeben über

MDT 2010 and Windows AIK Supplement Revisited

  • Artikel

In my previous post titled Issue with MDT 2010 Update 1 and Windows AIK for Windows 7 SP1 Supplement, I mentioned some challenges if you wanted to use Windows PE 3.1 and still use Windows RE from a Windows 7 SP1 BOOT.WIM file.  One possibility proposed for dealing with this is to manually modify the Windows AIK version so that MDT knows a new version has been installed.  That sounds easy enough, renaming HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ComponentStudio\6.1.7600.16385 to instead be HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ComponentStudio\6.1.7601.17514.

I did try this out, and encountered two issues to note:

  • Deployment Workbench doesn’t really like the change.  After changing this key, you’ll get warnings from Deployment Workbench saying that the version of WIMGAPI (6.1.7600.16386) is different than the version of Windows AIK (6.1.7601.17514).  There’s no workaround for this – you would just need to live with the annoyance of the warning, which will be displayed any time Deployment Workbench needs to use Windows AIK components.
  • The Windows AIK team can’t support the change, primarily because it’s not something they have tested to see if there are any other unexpected side effects.

So while the workaround of editing the registry key may work, we can’t really recommend it.

For a longer-term solution, we have modified the Deployment Workbench code in MDT 2012 Beta 1 (see https://blogs.technet.com/b/msdeployment/archive/2011/06/01/microsoft-deployment-toolkit-2012-beta-1-now-available.aspx if you missed that announcement) so that it checks the version of the Windows AIK WINPE.WIM file, rather than checking the Windows AIK version in the registry.  As a result, MDT 2012’s behavior is:

  • Windows PE 3.0 WINPE.WIM present in the Windows AIK folder and Windows 7 RTM or Server 2008 R2 RTM source files in the deployment share?  MDT will create a boot image from the Windows 7 RTM BOOT.WIM and it will include Windows RE.
  • Windows PE 3.1 WINPE.WIM present in the Windows AIK folder and Windows 7 SP1 or Server 2008 R2 SP1 source files in the deployment share?  MDT will create a boot image from the Windows 7 SP1 BOOT.WIM and it will include Windows RE.
  • Any other combination?  MDT will create a boot image from the Windows AIK WINPE.WIM file and it won’t contain Windows RE.

Comments

  • Anonymous
    January 01, 2003
    Yes, that's a typo which I've now fixed.

  • Anonymous
    June 09, 2011
    For the paragraph "For a longer-term solution, we have modified the Deployment Workbench code in MDT 2010 Beta 1...." shouldn't that say "MDT 2012 Bets 1"?

  • Anonymous
    August 08, 2012
    Hi Michael, Can you clarify this a little further? "•Windows PE 3.1 WINPE.WIM present in the Windows AIK folder and Windows 7 SP1 or Server 2008 R2 SP1 source files in the deployment share?  MDT will create a boot image from the Windows 7 SP1 BOOT.WIM and it will include Windows RE." As I read it, it states that I have to locate the winepe.wim from the Windows AIK folder? Isn't that the same? Or should I be finding windows PE 3.1 winpe.wim and dropping that into the windows AIK folder so it uses that instead of the AIK winpe.wim? I'm missing something here... Currently I am having the issue where my deployment update is only using the AIK Winepe.wim so I'm sure I'm in the right blog as it won't show Windows RE at all but DART is integrated (just not able to use some of the tools without RE) ;) Thanks.  

  • Anonymous
    August 09, 2012
    Hey Michael, I figured it out. I just needed to update my win pe from 3.0 to 3.1 in AIK to properly work with mdt 2012 and win 7 sp1. Thanks for your blog, if i didn't get the hint to look there I would probably still be chasing the wind. :)