Hi There,

I'm trying to have more than one task sequence being deployed from one boot image.

I have created the Operating System Images & Installers for a number of O/S types and injected the drivers of the hardware into the boot image. I have also created different device collections associated to the O/S and subsequent Task sequences and added these systems to the device collections and boot the hardware it fails as if it can't find the hardware drivers within the boot image. However, if I place the device into the the first device collection everything boots and works correctly.

Can someone tell me if what I'm trying to do is possible and if so how can I achieve my goal?

I know that this forum is for SCCM 2007 and I'm using 2012, but I can't find the correct forum for SCCM 2012..

 

• Edited by CS Kevin Wednesday, February 18, 2015 3:51 PM wrong version listed

Yes, most folks use a single boot image (or just two, one for each architecture) for all of their task sequences.

There's nothing special that needs to be done to enable this.

I think you may be confusing the purpose of drivers in the boot image though; that drivers in boot images have nothing to do with OS being deployed or the drivers for the OS being deployed. Drivers in boot images merely facilitate the initial network communication and writing of files to the local disk during the WinPE phase of the TS (which occurs after the first reboot and before the Setup Windows and ConfigMgr task). Once the Setup Windows and ConfigMgr task happens, the boot image and its drivers are irrelevant.

So, yes, you must include drivers in the boot image for all the models you are deploying to with the following caveats:

- You only need to add NIC drivers and sometimes storage drivers (because as mentioned that's the only thing significant during the WinPE phase)

- Boot images come with a lot of built in drivers so you should only add drivers to a boot image if it doesn't already include a suitable one. Trial and error is the only way to really test this.

The collection a device is in makes zero difference whatsoever. The only way what you describe above is possible is if different boot images are in fact being used.

What exactly is failing and how are you verifying this?

Finally, the 2012 OSD forum is at https://social.technet.microsoft.com/Forums/en-US/home?forum=configmanagerosd . (Hopefully a moderator will move this thread)