locked
SCCM 2012SP1 with MDDT 2012 and CustomSettigns.ini RRS feed

  • Question

  • Is CustomSettings.ini within Windows settingspackage the only CustomSettings.ini used when deploying workstations using MDT Task Sequence through SCCM. I mean does CustomSettings.ini in DeploymentShare\Control be ever used in this situation.

    Also can i use same settings in SCCM integrated CustomSettings.ini than in plain MDT driven CustomSettings.ini? 

    Thursday, June 6, 2013 12:06 PM

Answers

  • Yes, since the settings package is just a package.  It won't change unless you update it from source or have it set to update from source automatically on a schedule.  If you need to make changes, update the source, update the package, and then try it and it should make use of the new "package".

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    • Marked as answer by Jouni J Friday, June 7, 2013 6:04 PM
    Friday, June 7, 2013 5:48 AM
    Answerer

All replies

  • No, the CustomSettings.ini in the DeploymentShare\Control wouldn't be used.  SCCM doesn't even know how to get to it since it isn't processing the MDT BootStrap.ini file that has the path to the DeploymentShare.

    Mostly, yes, you can use the same settings.  There are obviously some settings that simply don't apply when used with SCCM (like the Skip variables for skipping the Panes, as those are used in MDT, not MDT+SCCM).


    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Thursday, June 6, 2013 1:36 PM
    Answerer
  • Ok..thanks for clearing this up Geek. Yet another question though.

    Are settings packages static? I mean if i create an settings package with cs.ini in it, can i later change settings in that particular cs.ini and those changes will become effective?

    Friday, June 7, 2013 5:17 AM
  • Yes, since the settings package is just a package.  It won't change unless you update it from source or have it set to update from source automatically on a schedule.  If you need to make changes, update the source, update the package, and then try it and it should make use of the new "package".

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    • Marked as answer by Jouni J Friday, June 7, 2013 6:04 PM
    Friday, June 7, 2013 5:48 AM
    Answerer
  • By updating package from source do you mean Update Distribution Points command?
    Saturday, June 8, 2013 6:47 AM
  • Yes, essentially.  Every package has a "source folder" that it got the contents of the package from before sending it to the Distribution Points.  You need to update the file in that source folder, then Update the Distribution Points with a new version of the package (since the source has changed).

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Saturday, June 8, 2013 7:05 AM
    Answerer