locked
CustomSettings.ini config not skipping wizard panes RRS feed

  • General discussion

  • Hello folks - Interesting scenario here where the CustomSettings.ini file is not skipping (or allowing certain) Wizard panes. I'm not entirely sure where the issue is, or if I'm simply misunderstanding the operation between the two - it is possible it's interacting correctly and I've been mistaken.

    Screen shot showing the wizard panes, I cannot attach yet. Coming soon

    CustomSettings.ini:

    [Settings]
    Priority=Default
    [Default]
    _SMSTSORGNAME=MyOrg
    UserDataLocation=AUTO
    DoCapture=YES
    OSInstall=Y
    TimeZoneName=Central Standard Time
    TimeZone=Central Standard Time
    UILanguage=en-US
    UserLocale=en-US
    SystemLocale=en-US
    KeyboardLocale=0409:00000409
    AdminPassword=password123
    MachineObjectOU=OU=Computers,DC=my,DC=domain,DC=com
    JoinDomain=mydomain.com
    DomainAdmin=username
    DomainAdminDomain=mydomain.com
    DomainPassowrd=password
    NetworkLocation=Work
    SLShare=\\computer\Logs
    ProductKey=KEYREMOVED
    USMTOfflineMigration=FALSE
    UserDataLocation=NONE
    OptionalOSFeatures=NetFx3
    BdeInstallSuppress=YES

    HideShell=NO
    ApplyGPOPack=NO

    SkipTaskSequence=NO
    DoNotCreateExtraPartition=YES
    SkipAppsOnUpgrade=NO
    SkipAdminPassword=YES
    SkipProductKey=YES
    SkipPackageDisplay=YES
    SkipComputerName=YES
    SkipDomainMembership=YES
    SkipUserData=YES
    SkipLocaleSelection=YES
    SkipTimeZone=YES
    SkipApplications=NO
    SkipBitLocker=YES
    SkipSummary=YES
    SkipCapture=YES
    SkipFinalSummary=N

    EventService=http://computer:9800

    Is there a way to see what CustomSettings.ini file is being used during deployment? I have two shares, a Build and a Deploy share. PXE via WDS, I'm seeing the correct Task Sequence name for the share I'm trying to deploy from (Deploy share) and the above CustomSettings.ini file from that share is above.

    I'm stumped.

    Thursday, May 18, 2017 7:57 PM

All replies

  • Any MDT experts have an idea? From what I can tell there is not an "order" to which the rules should be configured - if this is wrong do advise.
    Tuesday, May 23, 2017 3:50 PM
  • Can you give an example of what isn't being skipped?

    Which settings take priority

    1. Unattended.xml has the lowest priority
    2. CustomSettings.ini supersedes Unattended.xml
    3. Database supersedes both CustomSettings.ini and Unattended.xml
    4. Task Sequence Variable specified in a Task Sequence supersedes the Database, CustomSettings.ini and Unattended.xml

    I'd recommend setting things like the product key or OS features via the unattend or task sequence instead of customsettings. Mostly because it makes your deployment share more flexible for support multiple operating systems and task sequences.

    FYI NetworkLocation is deprecated, so don't use it.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Tuesday, May 23, 2017 6:51 PM
  • Screen caps are below. What I've also been noticing, is my SMSTSORGNAME=MYORG is also not showing. When the deployment progress is on the screen, the generic "organization" is populating.

    It's almost like the CS.ini file for my deployment share is not being used.... how could this be?


    • Edited by Paulemf Monday, June 12, 2017 8:09 PM
    Monday, June 12, 2017 7:54 PM
  • Screen cap

    Monday, June 12, 2017 8:10 PM
  • Monday, June 12, 2017 8:11 PM
  • Monday, June 12, 2017 8:12 PM
  • Monday, June 12, 2017 8:12 PM
  • Monday, June 12, 2017 8:12 PM
  • Monday, June 12, 2017 8:12 PM
  • Monday, June 12, 2017 8:13 PM
  • Monday, June 12, 2017 8:13 PM
  • Have tried creating a new deployment share? You should not be seeing a VBscript error during the wizard. From my point of view there's no way of telling what's going on in the background, if scripts have been modified, etc.

    I'd say start with a new clean Deployment Share and test with that. You only need to do the basics like importing an OS. Don't bother importing drivers or other applications. Make a new VM in Hyper-V and build your boot image for the new deployment share. You only need just enough to boot into the wizard to see if it uses your custom settings file.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Monday, June 12, 2017 8:39 PM
  • I'll give this a go - thanks, Dan.
    Monday, June 12, 2017 9:21 PM
  • Deploying from a newly built share does find the correct CS.ini. It has introduced other issues that I'm sorting through.

    I'll report back

    Thursday, June 22, 2017 2:38 PM