Automating MDT 2012: Laptops vs. Desktops in your Customsettings.ini file

If you’re like me, you’re managing about an equal number of laptops and desktops in an enterprise environment. With a little bit of tweaking of the MDT 2012 customsetting.ini file and some trial and error, you can get MDT 2012 to:

  • Automate the naming of the systems at deploy time – The example below will assign a name based on wether it’s a laptop or desktop and use the last four of the serial number.
  • Automate the OU the system is droped into at join time. – Often Laptops live in a different OU than desktops, so here you can
  • Automate what software will go on what. – Need VPN on laptops only? No problem we can do that as well.

Below is an example of how you can automate the configuration of these three basic settings in the deployment of these two separate systems.

Managing Basic Deployment Settings for Laptops and Desktops is easy with MDT 2012.

If tweaking the customsetting.ini file is absolutely new to you, check out : The Deployment Bunny’s Custom Settings.ini Explained Guide or my MDT 2012 CustomSettings.ini Tips & Tricks