locked
MDT Customsettings.ini vs MDTDB vs TS conditions with SCCM confusion RRS feed

  • Question

  • Sorry for the long post but need some clarification. To this point I've just been using SCCM for Win 7 deployments and not really taking advantage of MDT. So I'm trying to learn more about MDT integrated with SCCM for more complex ZTI's scenarios - ie. location specific apps, device make/model drivers ect. I'm getting confused around the customsettings.ini vs MDTDB vs TS conditions and the recommended/how way you do it. It reminds me of how I used to deploy XP and just a massive VB script which handles everything based on the location, model, user and other variables. I'm just worried at keeping it dynamic, like %model% = install %model% instead of hardcoding values.

    eg 1) I have a few laptop & desktop makes/models and I want to install drivers/software based on the type. At the moment I just have in the TS a condition which does a WMI call and if true then install that specific driver. What advantages does Customsettings.ini or MDTDB bring apart from being able to reuse the gathered info of device model in the script?

    eg 2) I have departmental/location apps and regional settings based on AD OU's/Sites/IP subnets ect. So if IP=x.x.x.x, AD OU = dep1 install these apps/configs.

    Which method do you use to handle these situations and any tips regarding customsettings.ini vs MDTDB vs TS conditions?

    Tuesday, May 1, 2012 4:42 AM

Answers

  • 1) For drivers you can add a WMI statement in the TS and let that detect the model and apply the correct driver package

    2) There are several ways to do that. The MDT database is a good idea, it already has examples on how to use locations and roles.


    Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund

    • Marked as answer by Sabrina Shen Thursday, May 31, 2012 2:44 AM
    Tuesday, May 1, 2012 5:32 AM
  • Does using the Customsettings.ini or MDT database override the unattend.xml, I saw on another thread someone said you shouldn't use unattend.xml with customsettings.ini? What is your preferred method for managing location based apps/settings?

    well, I would go for MDT Roles and Locations to deploy apps & settings. Customsettings.ini section (MDT DB) will take precedence over unattend.xml hence  I'd suggest not to modify default unattend.xml.

    Regards, Sachin

    • Marked as answer by Sabrina Shen Thursday, May 31, 2012 2:44 AM
    Tuesday, May 1, 2012 11:23 AM

All replies

  • 1) For drivers you can add a WMI statement in the TS and let that detect the model and apply the correct driver package

    2) There are several ways to do that. The MDT database is a good idea, it already has examples on how to use locations and roles.


    Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund

    • Marked as answer by Sabrina Shen Thursday, May 31, 2012 2:44 AM
    Tuesday, May 1, 2012 5:32 AM
  • Thanks Kent. Yep already using that method for drivers.

    I've read a few examples for location based apps/settings using MDTDB and will give it a shot.  Does using the Customsettings.ini or MDT database override the unattend.xml, I saw on another thread someone said you shouldn't use unattend.xml with customsettings.ini? What is your preferred method for managing location based apps/settings?

    Tuesday, May 1, 2012 7:09 AM
  • Does using the Customsettings.ini or MDT database override the unattend.xml, I saw on another thread someone said you shouldn't use unattend.xml with customsettings.ini? What is your preferred method for managing location based apps/settings?

    well, I would go for MDT Roles and Locations to deploy apps & settings. Customsettings.ini section (MDT DB) will take precedence over unattend.xml hence  I'd suggest not to modify default unattend.xml.

    Regards, Sachin

    • Marked as answer by Sabrina Shen Thursday, May 31, 2012 2:44 AM
    Tuesday, May 1, 2012 11:23 AM