A friend (You know how you are…) asked me today “I need to have different application bundles in the MDT Wizard based on location, any ideas?” and since I cant refuse to help a friend, here is a solution.
Use WizardSelectionProfile, Selection Profile and Default Gateway
So here is a step by step, kind of.
You need to add DefaultGateway to the customsettings.ini to match your environment. So it should look something like this:
WizardSelectionProfile=Wizard – HQ
WizardSelectionProfile=Wizard – BO
Create the Application folder
In the Deployment Workbench, create a Application folder, where you can store the applications that should be available at the BO site, something like this.
Create your WizardSelectionProfile’s
In the Deployment Workbench, Advanced Settings, Selection Profiles – Create a Selection Profile called “Wizard – HQ”. It should contain everything that should be selectable at the HQ site. In this case the folder is not available at HQ.
In the Deployment Workbench, Advanced Settings, Selection Profiles – Create a Selection Profile called “Wizard – BO”. It should contain everything that should be selectable at the BO site. In this case all folders are available.
Test and verify.
That should be it, so the net result would be something like this:
Running the Wizard at the BO
and running at HQ will give you this.
Categories: Lite Touch, MDT
Another Excellent Post! Keep up the Good Work Mike!
Working on it my friend, working on it :-)
Thanks for the great information. Could we do something like this based off the Gateway IP to decide which domain a machine should be joined? For instance, looking at automating a lot of our Server installs. 99% of all our new builds are all VM’s. So, when they start off, they should get a Gateway IP of the zone they will be in based off the cluster, etc. I haven’t tried it yet, but it should be possible, correct? This also can be done with the MDT integration within the ConfigMgr console?