Hi there, I try to import in SCCM a WinPE 4.0 boot image created in a lab environment with MDT2012 and Windows ADK. I get the finalized boot image error. in the boot image are the new HTA and WMI stuff what sccm2007 supposted to need. anybody? it's frustrating. regards Roger PS: I am also seeking on a step by step guide to capture and deploy Windows 8 with SCCM2007 as is should be possible to deploy windows 8 with SCCM 2007SP2R3

There's no official support for deploying Windows 8 with ConfigMgr 2007 and it's not officially supported in ConfigMgr 2012 until SP1, so I'm not surprised that you're having issues importing a WinPE 4.0 image. It's unlikely that Microsoft will release another service pack for ConfigMgr 2007 to support Windows 8 deployments but time will tell :)

well that is strange becourse in the documentation of MDT2012 there is sccm 2007 integration with states that is for the deployment of win8 and so on.

well that is strange becourse in the documentation of MDT2012 there is sccm 2007 integration with states that is for the deployment of win8 and so on.

You're either reading the documentation wrong or its poorly worded.Jason | http://blog.configmgrftw.com

You're either reading the documentation wrong or its poorly worded.Jason | http://blog.configmgrftw.com

I'm also interested in this. I've created both an x86 and x64 WinPE 4.0 boot image and used oscdimg to create bootable ISOs. I can boot up into WinPE on a VM host without issue. The issue is when trying to import into SCCM 2007 SP2 R3, it fails saying they are not finalized. I'm going to go out on a limb and guess that SCCM 2007 does not know how to proper process and use the new WinPE image. I guess we have to wait and see if Microsoft releases an update. In regards to MDT 2012, I do recall (like OP stated) that there was "support" for SCCM 2007. However, I'm guess at least right now it is not FULL support. If anyone has more info, I'd like to hear it on Win PE 4.0 and SCCM 2007 Thank you!

I'm also interested in this. I've created both an x86 and x64 WinPE 4.0 boot image and used oscdimg to create bootable ISOs. I can boot up into WinPE on a VM host without issue. The issue is when trying to import into SCCM 2007 SP2 R3, it fails saying they are not finalized. I'm going to go out on a limb and guess that SCCM 2007 does not know how to proper process and use the new WinPE image. I guess we have to wait and see if Microsoft releases an update. In regards to MDT 2012, I do recall (like OP stated) that there was "support" for SCCM 2007. However, I'm guess at least right now it is not FULL support. If anyone has more info, I'd like to hear it on Win PE 4.0 and SCCM 2007 Thank you!

MDT 2012 support has nothing to do with and is completely independent from supporting WinPE 4.0. MDT is a toolkit that enables advanced deployment scenarios and in turn uses WinPE and the WAIK or ADK. None of these are part of MDT; they are part of the core Windows product. There is no more info to be had. ConfigMgr 2007 does not support Win 8, WinPE 4.0, or the ADK. I've not heard any info about 2007 supporting Win 8 at all. I suspect that they *may* provide an update to support it as a managed OS but similar to SMS 2003 and Win 7, it will never support deploying Win 8 and the Win 8 deployment tools.Jason | http://blog.configmgrftw.com

MDT 2012 support has nothing to do with and is completely independent from supporting WinPE 4.0. MDT is a toolkit that enables advanced deployment scenarios and in turn uses WinPE and the WAIK or ADK. None of these are part of MDT; they are part of the core Windows product. There is no more info to be had. ConfigMgr 2007 does not support Win 8, WinPE 4.0, or the ADK. I've not heard any info about 2007 supporting Win 8 at all. I suspect that they *may* provide an update to support it as a managed OS but similar to SMS 2003 and Win 7, it will never support deploying Win 8 and the Win 8 deployment tools.Jason | http://blog.configmgrftw.com

Jason, I understand that MDT 2012 is a toolkit. However, MDT/WAIK/ADK/SCCM are all closely interrelated. What I don't understand is the following: 1. MDT 2012 supports integration with SCCM 2007. If 2007 cannot leverage the new MDT 2012 features....why offer the integration? 2. MDT 2012 release documentation references using WinPE 4.0 to deploy Windows 7. "When installing Windows 7 using Setup.exe with Windows PE 4.0 from the Windows ADK, two error dialog boxes are displayed while still in Windows PE. The dialog boxes do not affect the deployment, but you must click OK in each of them before the deployment process will continue." So, one would think that integrating MDT 2012 with SCCM 2007 would allow you to deploy Windows 7 using WinPE 4.0. Currently, this is not possible since you cannot import a WinPE 4.0 WIM to SCCM 2007. 3. SCCM 2012 was JUST released a couple of months ago and needs to be update to support Windows 8 RTM. Large Enterprise customers (like myself) cannot just updated an environment with 8 Primaries and 110 Secondary's overnight. I would hope Microsoft would release an update to SCCM 2007 as it is not end of life. Don't get me wrong. I love all the new features of SCCM 2012 and we have an active project to look towards moving to it. However, it isn't going to happen this year.

While I understand the confusion, it's just that confusion of what each technology or product is responsible for. I'm sure there's frustration also, but that doesn't change the reality that is Microsoft and its products. MDT is produced by the Solution Accelerator team which is not in any way affiliated or connected to the Windows product group. They have to file DCRs when they discover things and have no direct influence over the direction of Windows. WAIK and ADK are teams within the core Windows product group though so there is no real connection. Same with ConfigMgr, it's a separate product group which has no direct connection to the Windows product group or the Solution Accelerator team. As big of a company as you are, Microsoft is bigger. Like it or not, these are huge products we are talking about and not simply a few lines of code here or there. Trying to synchronize all of the products would add years to the product development lifecycles and basically nothing would get done. 1. MDT is also a stand-alone product so just because MDT supports something does not Mean ConfigMgr does. MDT is not about deploying Windows 8, it's about deploying Windows. It's a toolkit to make it easier and streamline the process. MDT 2012 offers many other (new and old) features that have nothing to do with the version of Windows being deployed. 2. As mentioned in #1, MDT is also a stand-alone product that does not depends upon ConfigMgr; however, when it is integrated into ConfigMgr, it merely extends ConfigMgr's core functionality and thus is restricted by ConfigMgr's own OS support. 3. Actually, ConfigMgr 2012 as a product has been finished since December, long before the final form of Win 8 was even close. Full support for Win 8 is going to be included in SP1 -- this was publically announced at TechEd and is supposed to be available before the end of the calendar year. SMS 2003 was about 6-7 years old when Win 7 came out so it may not be a fair comparison, but ConfigMgr 2007 is now about 5 years old. As mentioned, I do think that will support Win 8 as a managed system but won't offer anything in the way of OSD because things have so dramatically changed with the ADK. As a big customer though, please give this feedback to your TAM -- there's nothing I can do about it no matter what I think or say. Jason | http://blog.configmgrftw.com

Jason, Thank you for the insight. I'll reach out to our TAM and see if she can dig up any information. Again, thanks for the input.

Jason, Thank you for the insight. I'll reach out to our TAM and see if she can dig up any information. Again, thanks for the input.

Jason, Thank you for the insight. I'll reach out to our TAM and see if she can dig up any information. Again, thanks for the input. Well many thanks for a the answers. I am able to capture and deploy win8 Images with sccm 2007, but the capture takes a manual USB prep. have Fun with win8 Roger

Jason, Thank you for the insight. I'll reach out to our TAM and see if she can dig up any information. Again, thanks for the input. Well many thanks for a the answers. I am able to capture and deploy win8 Images with sccm 2007, but the capture takes a manual USB prep. have Fun with win8 Roger

It appears to deploy fine using WinPE 3.0 and SCCM 2007. I had some issue with the config man client (namely a certain patch included in the install that didn't like Windows 8), but it is deploying like a champ now. We are still pursuing our SCCM 2012 environment, but it is nice that I can do some early work with Windows 8 since there have been people inquiring about it.

It appears to deploy fine using WinPE 3.0 and SCCM 2007. I had some issue with the config man client (namely a certain patch included in the install that didn't like Windows 8), but it is deploying like a champ now. We are still pursuing our SCCM 2012 environment, but it is nice that I can do some early work with Windows 8 since there have been people inquiring about it.

MDT has nothing to do with WinPE dude.. WinPE is a part of the WAIK, which is now the ADK. Yes.. MDT 2012 does say it supports Win8 and Server 2012 but it doesn't say it supports an SCCM OSD deployment of Win8 and SCCM2012. Yes.. MDT 2012 says it supports integration with SCCM 2007 (and it does) but for Win7/Server 2008R2 and below. MDT is a tool on it's own which can be used for Light Touch deployments and there are plenty of other Zero Touch Deployment tools out there.. SCCM is just one tool of many which can integrate with MDT.