Issue with MDT 2010 Update 1 and Windows AIK for Windows 7 SP1 Supplement

re: Issue with MDT 2010 Update 1 and Windows AIK for Windows 7 SP1 Supplement

MS-Student — Tue, 20 Nov 2012 13:21:24 GMT

こんにちはマイケルさん、私はTechnetのチュートリアルを参考にしてWindow RE イメージの作成を勉強していています。するとその他のパッケージ追加コマンドを実行したところで、0x800f081eエラーが発生してパッケージは追加できない。その理由を調べたがTechnetオプションコンポーネントのセットアップログ診断ツール記載の0x800f081eエラーコードの説明では｢適用可能なパッケージではありませんでした｣のわかりきった答え、ユーザーが求めているのはなぜ適用可能とならないのかと言うことなのです、また解決策も結局は「CSSに問い合わせてください」となっていていて、これではエラーの理由もその解決策も解らずさらに調べていてビルド番号が違いが原因と言うことが解りましたが、WindowsREイメージ作成でのパッケージの追加の解決策が不明なため質問します。

　WindowsREイメージ作成方式では0x800f081eエラーが発生し既定パッケージ外のパッケージは追加できないので、WindowsPEイメージ作成方式でWindows RE作成をしようとすると、パッケージの追加処理はどれでもエラーなく実行できるけれども、WAIKにはWinPE-SRTパッケージは含まれていないのでWindowsREイメージ作成そのものが不可能と言うことになります。

　ということは、Windows 7とWAIKではパッケージをWinPE-HTAパッケージなどをカスタマイズ追加したWindows REは作成できないことになります。

カスタマイズパッケージ追加したWindowsREイメージ作成をしたいときはWinPE-SRTパッケージの含まれているWindows 7のWindows OPKを使用するよりほかにない、ということになります。

　しかしせっかくWAIKが入力されているのに、Windows OPKのダウンロードから始めるのは面倒です。Windows 7SP1とWAIKのパッケージファイルのビルド番号の違いを解決してその他のパッケージ追加を行う良い方法はないのでしょう？教えてください。

re: Issue with MDT 2010 Update 1 and Windows AIK for Windows 7 SP1 Supplement

Mark — Wed, 18 Apr 2012 16:14:11 GMT

I'm having similar issues in MDT 2012 with the AIK SP1 supplement installed. The error isn't identical, and I unfortunately don't have it in front of me, but DISM reports something along the lines of unable to open winpe-hta.cab. In some cases, there were two sequential backslashes (like C:\Program Files\Microsoft Deployment Toolkit\\something\\something) in the directory given in the error output, which I thought may be related.

I've removed AIK SP1 and the error has disappeared.

Is this a known issue?

Modifying settings.xml in the above fashion did not make a change.

Sorry for the inexact error reporting.

Thanks!

re: Issue with MDT 2010 Update 1 and Windows AIK for Windows 7 SP1 Supplement

Michael Niehaus — Sun, 26 Feb 2012 01:06:40 GMT

The Settings.xml file can be edited with Notepad. Make sure after you change it that you "comletely regenerate" the boot image when you next update the deployment share.

re: Issue with MDT 2010 Update 1 and Windows AIK for Windows 7 SP1 Supplement

pwhite106 — Thu, 23 Feb 2012 16:31:51 GMT

I changed the settings.xml file but it still just reboots. Can I do this in "notepad" or do I need to use another editor. Is there a better solution for this now?

re: Issue with MDT 2010 Update 1 and Windows AIK for Windows 7 SP1 Supplement

AndyChips — Wed, 07 Dec 2011 10:49:34 GMT

Thank you so much for this. It fixed my problem right away. We shouldn't have to deal with bugs like this though.

re: Issue with MDT 2010 Update 1 and Windows AIK for Windows 7 SP1 Supplement

grrrrr — Wed, 27 Apr 2011 19:15:04 GMT

MDT 2010 is driving me crazy!!! The fix for sp1 causes issues that need a fix, and that fix needs a fix.......

Stop the madness

re: Issue with MDT 2010 Update 1 and Windows AIK for Windows 7 SP1 Supplement

DG — Mon, 11 Apr 2011 20:41:04 GMT

I am still waiting on that answer too. It seems most logical to update the registry and all would be fine. That could have been scripted as part of the update. Xcopy, regfix, done.

re: Issue with MDT 2010 Update 1 and Windows AIK for Windows 7 SP1 Supplement

Dave — Tue, 05 Apr 2011 20:25:24 GMT

As Eric T mentions... can we update the registryvalue to get it working? I'm about to set up MDT2010 but have no installation to test on.

re: Issue with MDT 2010 Update 1 and Windows AIK for Windows 7 SP1 Supplement

Phil Wiffen — Thu, 24 Mar 2011 15:29:13 GMT

Thanks for blogging this Michael! This issue was "doing my head in", to use a British phrase ;)

re: Issue with MDT 2010 Update 1 and Windows AIK for Windows 7 SP1 Supplement

Eric T — Wed, 16 Mar 2011 15:37:55 GMT

Thank you for the explanation of the problem. We actully just started using EFI-based servers, so having a version of AIK / MDT that allows us to use the SP1 WinPE is a big help. Our issue manifested itself when we updated the boot images, then tried to boot from them...WinPE did exactly what it should do. It tried to run the wizard HTA, found that there was no HTA processor available because it was an optional pack, and just fell off the end of the script and rebooted.

Here's a question about a third option -- couldn't we just modify the registry (which keys?) to point MDT to the later AIK files? That would allow the Toolkit to search for boot files with the updated version number in the deployment share, while keeping all of our RTM media in the deployment share.

What do you think of that?