machine imaging

Laptop Machine Imaging with the Lancaster-Lebanon IU13.

Imaging Process starts with creating an Base Image from Scratch. I started by creating a Task Sequence from a existing image to help me start. I can then combine all the machines into one sequence once I have one working…

Creating a Task Sequence

The Imaging process within SCCM is more difficult than some of the more modern methods of imaging. First I used an existing Task Sequence and cloned that sequence to create a base Task Sequence that could be modified without breaking other deployments.

Combining Task Sequences into One.

Our goal with this new Imaging Process is to create one Task Sequence that can be used to image any machine that the Lancaster Lebanon IU13 might own. Achieving this was a easy process after doing some research out on the internet. First, I had to get the model information for each laptop and insert a query into the sequence so that it only applies that laptop’s driver packages. This is an important step as other laptops might have incompatible drivers. I achieved this by using a WMIC query. The Windows Management Instrumentation Command line allows us to grab information about the computer and it’s windows compartments. I used this to grab the computers model number with csproduct get name. This would output a string that would consist of the computer model number. This then could get put into a task sequence group and add options to only run if the model number equal the string. The command that was used to achieve this would have been something like this:

SELECT * FROM Win32_ComputerSystem WHERE Model LIKE “%255522G%”

 This would allow the driver package step which was inside of the group to only run if the model number matches that computer. The 255522G indicates the computer model number.