locked
Task Sequence - Build and Capture a reference os image RRS feed

  • Question

  • Setting up OSD for the first time in SCCM 2012. First I added Windows 7 SP1 via the "Operating System Installer" node using the original Volume License source files since we need to add that first in order to build a reference system into order to capture an image (wim), add it to the "Operating System Images" node and deploy it via a standard Task Sequence. Once I added the OS Installer package, I went to create a Build and Capture Task Sequence using the "Build and capture a reference operating system image" template. Unfortunately, when I got to the "Install Windows" step, the only choice was to pick an OS Image Package (wim) and not an OS Installer package from an original installation source, so basically you are dead in the water until you add a captured wim to the "Operating Systems Image" node to complete the TS wizard. Then you can go back and edit that Task Sequence by removing the "Install WIndows" step and add the step "Apply Operating System Image" step to use the OS Installer package. The other option is to build a custom Task Sequence from scratch using the "Apply Operating System Image" step instead of the "Install Windows" step. Anyone else notice this issue? 

    Tuesday, August 21, 2012 10:00 PM

All replies

  • Sounds strange, i have about 8 diffrent enviroments and have never seens this before. Are you sure you are using the:  Build and capture a reference operatingsystem image ?
    Tuesday, August 21, 2012 10:29 PM
  • Yep.

    1. Right click on Task Sequence Node | Create Task Sequence
    2. Select "Build and capture a reference operating system image" | Next >
    3. Specify task sequence information  (Enter Task Sequence name: | Choose Boot image | OK | Next >)
    4. This is when I get the "Install the Windows operating system" window that only gives me the option of choosing an Image package.
    Tuesday, August 21, 2012 10:40 PM
  • But if you click browse you will have a list of all of your Operating System Installers packages.

    Tuesday, August 21, 2012 10:51 PM
  • Not in my case. When I click browse, I only see the "Operating System Images" node which in my case is blank since I haven't added any any captured images (wims) yet. When I click browse, I know I am in the "Operating System Images" node since I created a folder in both nodes with different names and I only see the folder I created in the "Operating System Images" node and not the folder I created in the "Operating Systems Installers" node. 
    • Edited by scarneol Tuesday, August 21, 2012 11:20 PM
    Tuesday, August 21, 2012 11:20 PM
  • Normally you see a step called "Apply Operating System Image" in the Task Sequence that gives you the option to apply os from a captured image or apply from an origianl installation source. In my case,  instead of seeing the "Apply Operating System Image" step, I see a step called "Install Windows" that only gives me the option to apply a captured image.    
    Tuesday, August 21, 2012 11:30 PM
  • If you're using a ConfigMgr task sequence the above screenshot is the step you should be seeing when prompted to choose an OS to install.When you click browse that should show the list of 'Operating system installers'.

    Just want to confirm you're using ConfigMgr 2012 (not 2007) and that you're using a ConfigMgr 'Build and capture' task sequence, not an MDT integrated task sequence.

    It sounds like the option in the first windows of the 'Create a Task sequence wizard' is still set to 'Install an existing image package'

    • Edited by -Johno- Wednesday, August 22, 2012 12:13 AM
    Wednesday, August 22, 2012 12:08 AM
  • Did you say "OEM"? If so, stop. You are not allowed to reimage using OEM media; it violates the EULA and there are also technical challenges in doing so.

    Jason | http://blog.configmgrftw.com

    Wednesday, August 22, 2012 1:32 AM
  • I see a similar screen but when I click browse, I only see the list of 'Operating System Images' where you seem to see "Operating system installers". By the way, I haven't added any captured images yet so no images show up in either folder.

    Also, I apologize for using the term OEM. It is Windows 7 SP1 Enterprise VL media.



    • Edited by scarneol Wednesday, August 22, 2012 2:10 AM
    Wednesday, August 22, 2012 1:58 AM
  • Your screenshot is indeed similar but not the same. Where the first text box in my screenshot asks for the 'package', yours asks for the 'Image package' which is from the 'Install an existing image package' selection on the first step of the wizard.

    If you do have 'Build and capture a reference operating system image' selected on the first screen. If you click the back button after selecting ' 'Build and capture...' and giving the task sequence a name and boot image, is that option still selected?

    As a long shot maybe try installing the Cumulative Update 1 for ConfigMgr 2012

    http://support.microsoft.com/kb/2717295

    Edit: Just noticed the options left pane in your screenshot does indeed correspond with those listed in the 'Build and capture a reference OS' selection, whereas they are different for the 'Install an existing image package' selection, e.g. no 'Capture image' step listed


    You're running ConfigMgr 2012 RTM right? not a Beta or RC version?
    • Edited by -Johno- Wednesday, August 22, 2012 2:21 AM
    Wednesday, August 22, 2012 2:15 AM
  • An "Image Package" is the same thing as an OS Installer -- they just didn't update the dialog box from 2007.

    CU1 has nothing to do with this.

    Have you imported an OS Installer into the console? That must be done before the task wizard is started.


    Jason | http://blog.configmgrftw.com

    Wednesday, August 22, 2012 2:24 AM
  •  

    Just to compare, when I select browse I get the above window listing 'Operating System Install Packages' compared to scarneol's screenshot showing 'Operating System Images'

    Wednesday, August 22, 2012 2:37 AM
  • Yep, no dispute there, but you had to manually import those OS Installers. There is no mention of him doing so.

    Jason | http://blog.configmgrftw.com

    Wednesday, August 22, 2012 2:45 AM
  • First of order of business was to add the Windows 7 SP1 source files via the "Operating System Installer" node since we need to add that first in order to build a reference system using the oem media before you can capture an image (wim) to deploy it via a standard Task Sequence.
    Second sentence of their first post, they did mention OEM in that line but that appears to have been a mistake.
    Wednesday, August 22, 2012 2:51 AM
  • Yeah, but it didn't say how he did this. I suspect he assumed that the wizard would do this for him and that he didn't have to manually create an OS Installer packager.

    Jason | http://blog.configmgrftw.com

    Wednesday, August 22, 2012 3:02 AM
  • So Johno mentioned this "You'rerunning ConfigMgr 2012 RTM right? not a Beta or RC version?" which got me thinking about which version of SCCM 2012 I am actually running since I am still testing SCCM 2012 in my test environment. Well with the recent release of SCCM 2012 SP1 CTP, we wanted to take a look at the new Mac and Linux management capabilities so I forgot that my last install of SCCM 2012 was with SCCM 2012 SP1 Customer Technology Preview. I feel pretty stupid I didn't catch this right away although I still find it odd that this version of SCCM (SP1 CTP) exhibits this behavior.  

    Thanks for your help Johno, and for the record Jason, I know exactly the difference between OS Installers packages and OS Image packages and how to add them to their respective node. I guess the opening line "First order of business was to add the Windows 7 SP1 source files via the "Operating System Installer" node wasn't clear enough." I have since gone back and edited the original to make it more clear.   





    • Edited by scarneol Wednesday, August 22, 2012 1:08 PM
    Wednesday, August 22, 2012 3:12 AM
  • Hi guys - I just installed SCCM 2012 SP 1 today and am now experiencing exactly the same issues as the OP.  I have added an OS Installer, redistributed the boot images, tried to create a build & capture task sequence, but when I click to add the "image package" the list is blank... Going to try to remove my OS Installer(s) and start from scratch... frustrating.
    Friday, September 21, 2012 5:18 PM
  • I just installed the SP1 in my test lab and am having the exact same issue.  I'm going to try building a custom task sequence to work around it.

    Initially I tried importing my windows server 2008 r2 trial installer, didn't show up.  so I imported a retail copy of windows 7 ultimate - same thing.  Somehow I remember something similar happening during my admin course but I'm a horrible student and forgot to take notes on how we worked around it.

    Friday, September 21, 2012 8:27 PM
  • I wonder if this is a known issue?  I can't find any other posts here concerning this... Was working just fine before SP1.. Wonder if I can roll back..?
    Monday, September 24, 2012 11:57 AM
  • Why do you need to rollback? You didn't install SP1 *beta* in production, did you?

    Jason | http://blog.configmgrftw.com

    Monday, September 24, 2012 2:09 PM
  • No - I certainly didn't install the Beta SP1.  Obviously I'm looking for a solution to this - if I can roll back to before, then my build and capture would work again I assume.  It had been before this upgrade.
    Monday, September 24, 2012 2:12 PM
  • Then what did you install? SP1 is beta only currently.

    Jason | http://blog.configmgrftw.com

    Monday, September 24, 2012 2:14 PM
  • This:

    http://www.microsoft.com/en-us/download/details.aspx?id=30133

    I didn't notice the "CTP" in the title.... I suppose that equates to a "beta"...

    Ugly that you can't uninstall the thing afterwards... Might be rolling back to a previous image.

    Monday, September 24, 2012 2:17 PM
  • That's not even the beta, that's pre-beta. I have no idea if you can uninstall it or not. You may want to call CSS.

    Jason | http://blog.configmgrftw.com

    Monday, September 24, 2012 2:20 PM
  • Okay-

    A workaround for anyone in the same boat and interested - Just create a new custom task sequence and then you can Add->Images->Operating System Image 

    Then you can select to use original installation media finally - here is the option:

    With that change, I can finally see my OS Installer in the list - just have to re-create the normal steps to build and capture... 

    Monday, September 24, 2012 2:22 PM
  • Forgive me, but what is "CSS"?
    Monday, September 24, 2012 2:24 PM
  • Microsoft, Customer Support Services

    Jason | http://blog.configmgrftw.com

    Monday, September 24, 2012 2:42 PM
  • I have the same issue in my lab environment.

    I have installed the SP1 BETA on a server 2012 box.

    When I try to create a build and capture TS it doesn't find any of the install.wim I just imported.

    (I'm using the same .wim files I've used previously with ConfigMgr 2007 and 2012 RTM and it worked fine)

    The reason is that it looks in the wrong place.... It look for it among the operating system images.

    I guess this is a bug :)

    A workaround would be to import the install.wim under images and add an (install.wim) at the end.

    Create and run your B&C TS. Give it a good name. Delete the one with the (install.wim) - when you no longer need it.

    Or even better - install MDT and integrate it with your ConfigMgr environment.

    Then create a MDT BnC TS which looks in the correct folder!

    :) good luck.


    Tuesday, October 9, 2012 7:18 AM
  • I guess this is a bug :)


    Make sure to file a feedback item on connect.microsoft.com then.

    Torsten Meringer | http://www.mssccmfaq.de


    • Edited by TorstenMMVP Tuesday, October 9, 2012 7:32 AM
    Tuesday, October 9, 2012 7:31 AM
  • done! :)
    Tuesday, October 9, 2012 9:24 AM
  • I am also experiencing this exact issue after the SP1 CTP update.
    Friday, October 19, 2012 7:53 PM
  • I too am unable to add a "Operating system installer" package to my Build and capture task sequence for a Windows 8 deployment with System Center 2012 SP1 Beta.

    Sure hope there's a solution real soon.

    Saturday, November 10, 2012 9:32 AM
  • Just to say I have the same issue as well, and I only installed Sp1 to review and work on Win 8 \ 2012 deployments which SP1 is suppossed to "provide"..... which as it is now in Beta doesn't work.... *face plant MS*

    as an interim solution\s:

    As mentioned earlier create a TS from scratch

    Export and import previously created Build and Capture TS.

    Friday, November 16, 2012 11:18 AM
  • Just to say I have the same issue as well, and I only installed Sp1 to review and work on Win 8 \ 2012 deployments which SP1 is suppossed to "provide"..... which as it is now in Beta doesn't work.... *face plant MS*

    They call it beta software because not all the bugs have been worked out yet. Do not install pre-release Service Packs, or other software, into production environments. You will be fully unsupported by Microsoft until you are running a supported version of the product.

    http://en.wikipedia.org/wiki/Software_release_life_cycle#Beta

    "Beta (named after the second letter of the Greek alphabet) is the software development phase following alpha. It generally begins when the software is feature complete. Software in the beta phase will generally have many more bugs in it than completed software, as well as speed/performance issues."


    If this post was helpful, please click the little "Vote as Helpful" button :)

    Trevor Sullivan
    Trevor Sullivan's Tech Room
    Twitter Profile

    Friday, November 16, 2012 1:53 PM
  • I have SCCM 2012 SP1 (RTM) and I am experiencing this same issue.  Clearly this was never fixed prior to SP1 going to RTM?
    Friday, January 4, 2013 12:06 PM
  • Simply saying you "have the same issue" doesn't really add any value to this thread. You should typically add exact details -- these forums are not meant for "discussions", they are meant to try to provide solutions and help.

    Jason | http://blog.configmgrftw.com

    Friday, January 4, 2013 3:35 PM
  • Just to add that same issue here with RTM SP1.
    Monday, January 7, 2013 12:12 PM
  • I can confirm also that the standard task sequence build and capture template does not allow the selection of OS install packages, only OS Images.  However, that said, I really do recommend that people should integrate MDT 2012 and use the templates it provides (which include a standard client task sequence that can build and capture for you!)

    Don't be afraid of MDT, it is your friend and the templates make short work out of building task sequences that handle USMT, refresh and new computer scenarios.


    My Personal Blog: http://madluka.wordpress.com

    Monday, January 7, 2013 12:41 PM
  • Just to add that same issue here with RTM SP1.

    That not an issue. It's by design. The wizard itself only lets you select OS images (not installers), but you can still use an OS installer if you modify the task sequence created by the wizard.

    Torsten Meringer | http://www.mssccmfaq.de

    Monday, January 7, 2013 2:23 PM
  • Wouldn't it make more sense to be the other way around, to perform build and captures from OS Installation media rather than an OS Image package?

    My Personal Blog: http://madluka.wordpress.com

    Monday, January 7, 2013 3:11 PM
  • So, this thread continues to confound me because I simply do not see this issue. When choosing the B&C TS type in the wizard, OS Installers are presented to me on the Install Windows step during the wizard and when I choose a deployment TS in the wizard, OS images are presented to me in the Install Windows step. The text in the step says "Image Package" for both, but when pressing the Browse button, the correct type is presented in the picker. Is this simply an issue of the text prompt being incorrect? To me, that's what appears to be happening.

    Jason | http://blog.configmgrftw.com

    Monday, January 14, 2013 3:39 PM
  • I just installed SP1 RTM yesterday and I have the same issue.

    This is my new Proof-of-concept server with SCCM 2012 SP1. Currently no Operating system Images, but I had uploaded and distributed 5 versions of MSDN windows (which Appear under 'Operating System Installers').

    Now, I create my FIRST task sequence as a Build and Capture task , because I don't have any Images (just the install Media)...Select the Browse button and nothing is listed. You will note it is actually asking for an 'Image Package' not an Operating System installer... which I find unusall as its a BUILD and CAPTURE task sequence.

    So the next test I did, is to add a 'Operating system Image'.. I didn't have any on hand so I just pointed to the install.wim of the Media.

    NOW when I go back , choose the Build and Capture task sequence - Use the drop down box, the image (install.wim) is now listed.

    So in summary, its confusing.. If your building an environment from scratch , with no pre-existing saved .WIM's... surely the first option you are going to do is BUILD and CAPTURE a .Wim. If your task sequence is only programmed to look at .WIM's - why is there the option of Operating System Installers? ignoring MDT.

    Tuesday, January 15, 2013 3:40 AM
  • With SP1 you can no longer use the setup.exe installer you would have in the past with Windows 7. This is outlined in the What's New page for SP1, where it mentions "The build and capture task sequence was updated to apply an operating system image instead of running Setup.exe for installation. You can still run Setup.exe for Windows 8 deployments by editing the task sequence in the task sequence editor."

    You instead have to use the wim file found on the Windows 7 media. There's a great post that goes over this in detail at http://scug.be/sccm/2013/01/13/configmgr-sp1-windows-7-deployment-is-not-supported-anymore-from-the-setup-exe/


    • Edited by Benjamin Watt Tuesday, January 15, 2013 10:43 PM Corrected typo
    • Proposed as answer by Benjamin Watt Tuesday, January 15, 2013 10:43 PM
    Tuesday, January 15, 2013 8:39 AM
  • I think Benjamin hit on the issue here. My post above was about RTM, but in SP1, things have changed to align with actual Windows deployment supportability.

    Jason | http://blog.configmgrftw.com

    Tuesday, January 15, 2013 2:27 PM
  • ahh, yep that explains it... so just to clarify, what happens to windows XP without a .WIM file? you can now only do this via a custom task sequence, capturing only a base .WIM .. then create another task sequence to add your customizations?
    Tuesday, January 15, 2013 9:15 PM
  • The build and capture task sequence was updated to apply an operating system image instead of running Setup.exe for installation. You can still run Setup.exe for Windows 8 deployments by editing the task sequence in the task sequence editor. (meaning the root path of the iso)

    http://technet.microsoft.com/en-us/library/jj591552.aspx

    So add the Install.Wim to Operating System Images in Console.


    Nicolai

    Tuesday, February 5, 2013 8:24 PM
  • Hi,

    Check out "Build, Capture and deploy Windows 7 and Windows 8 in SCCM 2012 SP1" on http://www.toolzz.com/?p=879
    This describes all the steps to build a working image.

    __________________________________________
    Willemjan van Laarhoven | http://www.toolzz.com


    Wednesday, February 27, 2013 9:01 PM
  • Install MDT and do it through an MDT task sequence, this was the only way I could see to do it.

    MCP, MCDST, MCTS x 6, MCITP x 3

    Please don't forget to mark this post as an answer if it is the solution to your problem!

    If you like trance music, please subscribe to my podcast Trancendance Podcast

    View my MCP Certifications

    Follow me on Twitter

    • Proposed as answer by Brian_Jones Tuesday, May 7, 2013 11:16 AM
    Tuesday, May 7, 2013 11:16 AM
  •   I can confirm that MDT integration only permit to add Windows 7 operating system sources as "Operating System Installer" but TS with this binaries fail to inyect drivers. Error on Windows Panther folder says Cant add drivers to drivers catalog. I found this can be happend with W7 drivers and WinPE 4.0 (Must say this issue is present with Intel 82579LM) When run TS in virtual environmet there is no error cause virtual use generic drivers. 

      Any idea about this??

    thanks in advance.

    VGC.
    CHILE


    Friday, September 13, 2013 12:44 AM
  • I have the same issue here with SCCM 2012 SP1 RTM... appears to be a bug, but I see someone mentions to just create your own build and capture by custom task.  What the heck is worth having a template to build and capt when it doesn't even work.  I was sure Micro$oft got this right by now???


    Richland, WA IT

    Friday, September 27, 2013 11:55 PM
  • Since there's no answer yet, I'll propose mine:

    Import the install.wim file from the Windows disc as an 'Operating system image', and use that instead of the 'Operating System Installer' option. I've always had problems using it and forgot about it, and came to this thread while troubleshooting why it kept failing. I don't know what it's purpose is, but you're better off using the install.wim in the \sources\ folder of the install media, and importing that as an OS Image, that should work fine.


    -MM

    Edit, I'll also add that you shouldn't use this install.wim to deploy OSes, but to do a build and capture. It sounds weird but the reason for that is when the OS gets laid down from install.wim it uses drive letter D, I believe this is by design from MS, don't know why though, but once sysprepped and redeployed your new wim will grab C:.
    • Proposed as answer by MMoore313 Thursday, October 10, 2013 3:56 PM
    • Edited by MMoore313 Thursday, October 10, 2013 4:01 PM added pertinent info.
    Thursday, October 10, 2013 3:56 PM
  • It sounds weird but the reason for that is when the OS gets laid down from install.wim it uses drive letter D, I believe this is by design from MS, don't know why though, but once sysprepped and redeployed your new wim will grab C:.

    That's why they introduced the OSDPRESERVEDRIVELETTER variable which can be used to force the default wim being applied to the C: drive.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, October 11, 2013 8:20 AM