I am currently trying to figure out a way to combine three different Stand Alone builds on to one flash drive. I have been successful doing so with two on the same with network builds. However, the stand alones have a slightly different structure that is throwing me off. I have tried tools like SARDU, WinSetupFromUSB, and xboot. None of them seem to work. The farthest I have gotten is to booting in the flash but then receiving the error of not being able to read the task sequence. Any guidance would be appreciated. Please let me know if you'd like any other information. 

• Moved by John Marcum [MVP]MVP Tuesday, July 05, 2011 3:28 PM (From:Configuration Manager Setup/Deployment)

I have been successful doing so with two on the same with network builds.

What is a network build? If you are talking about using regular boot media, then that's not really what you are doing because boot media is not specific to any task sequence.

As for stand-alone media in ConfigMgr, the in-box process is a one-to-one between the media and a specific task sequence.

All the other things you mentioned above have nothing to do with ConfigMgr so not sure what you are expecting.

If using stand-alone media, why not combine the images into a single WIM (if using more than one WIM, although the question would then be why are you using multiple images) and then use a single task sequence that dynamically deploys based upon some other variables like maybe user input?

Jason, 

Thanks for the quick response. By network build, I mean that most everything is pulled down from the network as far as software, drivers, etc. 

The tools I mentioned I tried using in order to boot to different iso's that we have. This was successful when pulling everything down from the network; however, the stand alone iso's seem to have a slightly different structure that is throwing off the grub4dos that was previously used for "network builds."

I am using stand-alone media due to the university setting that I am in. We have a very diverse setting which does not always allow for network connection. I would like to be able to combine the different builds into a single WIM; however, I'm not sure how to do so with a Win7 x86 build, a win7 x64 build, and a WinXP x86 build. If you could point me in the right direction, it would be greatly appreciated. 

As a side note, I am beginning to research MDT 2010 with the custom WIM's to see if that will help at all.

Here's an good overview of merging WIMs: http://deployment.xtremeconsulting.com/2010/12/16/combining-wim-files/. That along with a dynamic task sequence should get you where you want to be.

I'm curious as to why you had to resort to third-party tools for the "network builds" though? Given that boot media in ConfigMgr is not specific to a task sequence there's no reason to combine multiple boot images onto a single piece of media, Also by defintion, task sequences always load everything over the network at run-time so I'm not sure if there's some significance to you calling them "network builds" either?

I have one environment that allows for the deployment of an OS via the network; however, another environment that I am working with does not allow for network based builds – which is why we need to use Standalone media with the entire task sequence on a set of DVDs or USB sticks.  In short, the network at these branch sites just cannot support the amount of data that would be pulled across the pipes for an OS build.  We would like to go with a 32 GB USB stick since the end users that will deploy the OS to computers have at the very least 4 different images they would need to pick from.  What we really need to do is combine all of those task sequences on to one thumb drive and let the installer pick which task sequence gets deployed on the end system.  

I have exactly the same scenario, if someone have a solution ? 

How about, adding multiples OS images to a TS, apply required OS based on a TS variable. generate a TS variable by build options chssoen by technician using HTA or OSD++ or any other option to create a TS variable. In this scenario, you add all your images to the TS then create a offline media. Based on technican choice that particular WIM file will be applied.

I too am looking for a way to accomplish this. To elaborate a bit more When using a WINPE Boot disk to boot Machines on the Network using SCCM 2012 R2 OSD Images, SCCM will display multiple Images (Task Sequences) available to choose from like Corporate 32bit, or corporate 64bit, or other variations.  Is there a way to add more than one stand alone Media versions of these same Images to a single say 64gb or 128gb USB stick? I would prefer to keep them separate as they get updated at different intervals, and yet be able to match up to the choices available when using Network boot or PXE boot to SCCM method.

There is nothing built in for this no. Not saying it can't be done, just something you will have to figure out how to do yourself or get creative.