SCCM 2012 OSD Task Sequences - Image Deploymet Options

I'm managing an SCCM environment and I'm trying to keep my organization from using more than one TS if not needed. I'm creating another .wim file and wanted to know is there anyway to use the "Options" tab at the "Apply Operating System" step to create a condition to choose a "Capture Image" to apply.

I read somewhere that an .wim file can contain more than one image but not sure how to go about adding it.

The imagex command line tool allows you to append additional named images to an existing .wim
imagex.exe /compress maximum /check /verify /APPEND D:\Mount E:\Test.wim "Second OS"
where D:\Mount is where you have the existing WIM mounted to and you want E:\Test.wim to be a copy of the original .wim
Imagex tool is part of Windows AIK.

Yes there is. There are two ways:
1) create a single, multi image WIM
2) create different WIMs and use WMI

Option (1) is viable and just requires you to choose the WIM index number in the Apply OS step. I've never done it but it's on my "to do" list. The down-side is that the WIM will be very big if you have lots of variants which might have replication issues.

Option (2) is to use the options tab and set WMI conditions. I have done this and it worked great. It's the same method you use to filter machine drivers.
Create a sub-group
create "apply Sales image" options tab = add condition "select * from win32_product where model like "%OptiPlex%"
create "apply Engineer image" options tab = add condition "select * from win32_product where model like "%HP Elitebook 430%"
rinse and repeat.

The tricky part for you is to establish what WMI filter suits what department. If Sales all use one hardware type it's dead easy, but I doubt they do. The alternative is to query by OU. I test queries in WMI Tools (free download from MS) first and then when I'm happy paste the string into the task-sequence and test on physical hardware.

Just a query - what images are you using for who, as in why do need separate WIMs in the first place? For us, we had a "new OS" and a "legacy OS" for people who were too cautious to want anything new.
Having said that we had one WIM for the new OS that supported Intel and AMD by flipping the HAL files just before applying.

Mike

0

Featured Post

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Possible fixes for Windows 7 and Windows Server 2008 updating problem. Solutions mentioned are from Microsoft themselves. I started a case with them from our Microsoft Silver Partner option to open a case and get direct support from Microsoft.
If s…

By default the complete memory dump option is disabled in windows . If we want to enable the complete memory dump for a diagnostic purpose, we have a solution for it. here we are using the registry method to enable this.

The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7.
Start the SARDU utility:
Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…

With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…