Using multiple Boot images

[boyjaew2]

Just a quick question:

 

Is it completely unheard of to use separate boot images for different PC model's driver packages? It seems like it should be unnecessary, but I have HP elitebooks (99% of our environment) and then about a dozen Alienware R4s I recently became responsible for and the last time I tried to use those drivers in my x64 boot image it broke the OSD operation for the HPs and I ended up having to nuke my boot image and rebuild it.

 

I have everything fixed now and image deployment works again for the HPs, but I need to capture an Alienware image with totally different NIC and storage drivers and don't want it to screw up the working boot image.

[Rocket Man]

You can have as may Boot images as you wish with a naming convention suited......just inject in the appropriate NIC driver for a specific model and name it appropriately to save confusion...create TS for that model and use the custom boot.wim.

 

I do this as i have 15 remote DPs and lots of different models......so if a particular machine does not boot I just create a new boot.wim, add the driver and distribute and attach to TS...this way it prevents having to update the same boot.wims and redistrbute out to all 15 DPs

 

Rocket Man

[boyjaew2]

Excellent, thanks for the feedback! Glad to know I'm doing something correctly. I'm currently going BONKERS trying to capture and image for an Alienware R4. If your super bored and not quite tiring of answering questions have a peep at my current issue here - http://www.windows-noob.com/forums/index.php?/topic/5070-how-can-i-capture-an-image-using-capture-media-in-configmgr-2012/page__st__20#entry23589

 

I have no idea why it's not working.

 

Thanks, again