Once we have Task Sequence we should move on to building media. Because at this point we just have a big folder full of stuff programmed and ready to be pulled down, but nothing preconfigured to grab it.
Go into the “Advanced Configuration” and expand so that you can see
These four are placed in a very sensible order for a reason, I’ll try to give the “Instant Condensed” version of what they are.
When you create an Image, it will need to reference JUST HOW MUCH you DO and you DON’T want in that image. Your actual Deployment point (if you have multiple images) might well be 45 gigabytes of applications, Operating Systems and Service Packs and (if you were like our hapless ITPro friend in Part 8) Drivers.
If you broke everything down into a nice compartmentalized folder structure, This (YES RIGHT HERE) is where it all pays off. As you can see Microsoft has predefined some basic Selection profiles which (if you are working on a single deployment for a Single client site) might just meet your needs find. The names pretty much say it all
The whole Enchilada. The kitchen sink. Every O/S, Driver, File, Application, Service Pack nook and cranny that is in my deployment. RELEASE THE KRAKEN!
Ok just gimme the drivers and O/S to go. This SHOULD be pretty light (Unless again, you were that silly fool in Part 8)
All Drivers and Packages
All Service Packs under Packages, All drivers (Hmm Beefier! But hold the mayo0
I think that guy in Part 8 may have been involved in this Deployment, just give me all the stuff imported under Packages
I’m on a Diet. Just give me the O/S. Perhaps a straw?
Creating a Selection Profile (like everthing in MDT 2010) is very easy. Right click on Selection Profiles and choose (what else?) “New Selection Profile”
You’ll have to give the Profile a name. Make it sensible as you may have to later on call it up programatically.
And now after clicking on NEXT here, HERE is why you want the organization! When you get to your Selection Profiles, they select those folders you created (not the individual contents)
So the more granular you need your Selections, the more you should organize your folders. It also makes troubleshooting easier as you might be wondering why a deployment on 3 machines is crashing. If it’s a bad driver and you’ve organized your drivers VERY well you could ACTUALLY create a Selection Profile (or clear the configuration in an existing Selection Profile) and test that way
So looking at THIS particular Selection Profile It appears (because of the way I organized and named the Folders) I’m building a very specific selection of Software, Drivers and even Packages. You can even break your Task Sequences down by folders.
Clicking next twice and Finish and we now have a new Selection Profile
Next time? We Build MEDIA!