Jump to content


bennettjd

Creating a New Win7 boot wim for SCCM 2012 SP1

Recommended Posts

I am testing to different models in my environment to move from SCCM 2007 R3 to SCCM 2012 SP1. I have run into an issue do to SCCM 2012 boot wim's are windows 8. We have some intel p4's that we have and they do not support the boot wim of windows 8. I took the x86 boot wim that I had from the sccm 2007 R3 deployment and tried to import that into SCCM 2012 SP1. It tells me that the image is not finalized.

 

I have downloaded the WAIK 3.0 and tryied importing the wimpe.wim straight up and it would not. I am not sure if there is a way to take the install.wim from the dvd or another wim. I do not need very much in the wim, I use vbscripting. Or if there is a wim that i can download from someone to try?

 

I need help finding out if there is something different that i need to do to create an boot wim and finalizing it to work with SCCM 2012 SP1.

Share this post


Link to post
Share on other sites


I have the ADK. This only uses the windows 8 wimpe. I need to create a windows 7 for the Intel P4 processors. Thanks for the reply

Share this post


Link to post
Share on other sites

I have the ADK. This only uses the windows 8 wimpe. I need to create a windows 7 for the Intel P4 processors. Thanks for the reply

Ive been trying to do the same but for our virtual machines running on esx 4.1 but the problem is that it looks like WDS is using some kind of windows 8 boot loader before it loads the winpe image so even if you use a winpe 3.0 boot image it still won't load.

Share this post


Link to post
Share on other sites

I am experiencing the exact same issue, and have a post on the technet forums regarding this:

 

http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/8faa337b-a648-49b4-8431-49c022b96e04

 

Based on my testing and research this occurs with any processors that do not support the NX bit. As of the Win 8 RTM release Microsoft has been enforcing a setting by which Win8 can only be installed on processors that support this functionality. As a genral rule of thumb pentium 4 processors that support Hyper-Threading and above or processors that support 64-bit operating systems (ie. Core Duo, Core 2 Duo, etc) seem unaffected. Because WinPE 4.0 is based on Win8 Bootloader this seems to be causing the problem, even though you only plan to install windows 7.

 

Regardless i have a call in with Microsoft support as in my opinion this is completed unnacceptable, i will post back any further leads.

 

Thanks

  • Like 2

Share this post


Link to post
Share on other sites

I am facing the same problem. We have old computers with no NX option in BIOS settings. I tried everything to add WINPE version 6.1 with no luck

Share this post


Link to post
Share on other sites

I am experiencing the exact same issue, and have a post on the technet forums regarding this:

 

http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/8faa337b-a648-49b4-8431-49c022b96e04

 

Based on my testing and research this occurs with any processors that do not support the NX bit. As of the Win 8 RTM release Microsoft has been enforcing a setting by which Win8 can only be installed on processors that support this functionality. As a genral rule of thumb pentium 4 processors that support Hyper-Threading and above or processors that support 64-bit operating systems (ie. Core Duo, Core 2 Duo, etc) seem unaffected. Because WinPE 4.0 is based on Win8 Bootloader this seems to be causing the problem, even though you only plan to install windows 7.

 

Regardless i have a call in with Microsoft support as in my opinion this is completed unnacceptable, i will post back any further leads.

 

Thanks

Did you find anything out or can you shed some more light on the subject?

Share this post


Link to post
Share on other sites

I have recieived an email from my support agent explaining that he has brought the issue to the product grp and that he would get back to me with a possible solution for this type of situation. I will post back as soon as i hear something further

  • Like 2

Share this post


Link to post
Share on other sites

It's funny you ask in that way, lol. I used pretty much the same sentence when I emailed the support agent back myself. In essence yes they have and another TechNet user received the same response on a similar opened ticket. I am using the following thread on TechNet forums as the current forum for discussing this issue and possible solutions:

 

http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/8faa337b-a648-49b4-8431-49c022b96e04

 

i'll try to update this thread as information comes to me as well. If you read the post by adflet999 , he mentions a possible hack that involves ripping SCCM 2012 SP1 info using DISM from WinPE 4.0 boot images and integrating these components back into a 3.1 image to in essence trick SCCM into thinking the 3.1 image is in fact a 4.0 image. A novel idea and hopefully something comes of it as we are struggling with this one ourselves

 

Regarding the response from my support rep...they have essentially responded word for word as they did to adflet999 and have refunded us for the support call as this was a design change and there is no official workaround, nor plans to release one in the near future.

 

Thanks

Share this post


Link to post
Share on other sites

Binarymime,

I was following your thread, and it looks like there's a somewhat decent solution now available, which was mentioned early on in the thread, but no exact details given...

 

Unfortunately, the first step is a little tedious as it requires you to setup SCCM in a VM all over again, but I was able to get this to work for our older workstations so it makes it worth it to me...

  1. Build an SCCM 2012 RTM server (Site code TST) and copying off the boot.TST0001.wim from D:\Program Files\Microsoft Configuration Manager\OSD\boot\i386
  2. Create a bootable USB using the Task Sequence wizard in you SCCM 2012 SP1 installation
  3. Copy the boot.wim, off the newley created USB (D:\sources\boot.wim) and mount the image using DISM. This should be winPE4.0
  4. Browse the mounted image and copy the (d:\sms\bin\i386) to a local drive for later use.
  5. Mount the boot.TST0001.wim, which is winPE3.0, and copy the above directory (which should contain all the SMS SP1 OSD functions) into the same location on the mounted wim. Click yes to overwrite all files.
  6. Un-Mount and commit the boot.TST0001.wim, rename it to boot.wim and copy to the USB key in place of the WinPE 4.0/Overwriting this

What I hadn't thought about at the time, was that you might have been able to find a VM from Microsoft that already had ConfigMgr installed as some sort of trial (if such a thing exists)...this would save you having to setup SCCM 2012 RTM yourself.

 

I would also note that it would be a good idea to add the USB stick drivers to your WinPE image, otherwise you might get an error that says WinPE cannot read from the task sequence disk.

 

Now, what this means is that you're looking at LTI for all your old workstations, and no ZTI...this could be very problematic depending on your organization. Also, I believe that the workaround as was proposed will not allow you to import this boot image into SCCM, because even though it has the 4.0 binaries, I think SCCM will still recognize it as a WinPE 3.0/3.1 image.

 

I'll try here shortly and let you know what happens.

 

[edit]

Yeah, it won't let you import the hacked boot image.

Edited by h4x0r

Share this post


Link to post
Share on other sites

If you have a volume licensing agreement, then you can download the non-SP1 version there. Unfortunately, just the boot.wim file will not work...it needs to be the "boot.TST0001.wim" file that SCCM creates, so that it has all the CM components with it.

 

Does anyone know what all is included with the modified boot.wim that CM creates? I wouldn't have a problem sharing it out, if I knew for certain that there wasn't any info stored in the those binaries that could be used to compromise my CM environment on some level.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks h4x0r, for the prompt reply and the info. Unfortunately, I can't seem to find it in my volume licensing site. Nothing can be easy can it? Microsoft really sold us up the river on this one when they didn't realize that some organizations are non-profit and have tight budgets that don't allow hardware refreshes on a regular basis.

 

Let me know if you find it suitable to share out the correct file.

Share this post


Link to post
Share on other sites

That's odd...here's what I see in our volume licensing download section when I search just for "System Center 2012"...you can see the RTM products, and then below them are their SP1 counterparts.

 

post-7827-0-27652500-1364835636_thumb.jpg

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...