none
CustomSettings.ini & TaskSequenceID no longer processed the same after Update 1 patch RRS feed

  • Question

  • Hi All, 

    After patching from 2013 to 2013 U1 I noticed that some settings that should be applied as per TaskSequenceID definitions in the CustomSettings.ini file were no longer working. These were previously working perfectly pre-patching but now do not seem to be processed, the Default sequence still processes as normal.

    It was setup to perform the JoinDomain process in the various TaskSequenceIDs rather than Default as some types of deployment should not auto join to the domain. This was also the primary reason it was noticed to no longer be working.

    If you copy the JoinDomain settings (and DomainAdmin user/pass/domain values) from one of the TaskSequenceIDs and put them into Default, then the JoinDomain process runs as expected and the machine is joined on deployment completion.

    An example of a TaskSequenceID and Default as defined in CustomSettings.ini (any company ID has been removed):

    [DEPLOY-W7PRO]
    SkipCapture=YES
    MachineObjectOU=OU=_WDS,OU=*** Computers,DC=*****,DC=com
    JoinDomain=*****.com
    DomainAdmin=MDT_***
    DomainAdminDomain=*****.com
    DomainAdminPassword=*************
    Administrators001=*****\ITG_ALL

    [Default]
    OSInstall=Y
    SkipAdminPassword=YES
    SkipComputerName=NO
    SkipProductKey=YES
    SkipComputerBackup=YES
    SkipBitLocker=YES
    SkipDomainMembership=YES
    SkipUserData=YES
    SkipLocaleSelection=YES
    SkipTaskSequence=NO
    SkipTimeZone=YES
    SkipApplications=NO
    SkipSummary=YES
    SkipBDDWelcome=YES
    _SMSTSOrgName=Running %TaskSequenceID% on %OSDComputername%
    EventService=http://***deploy1:9800
    SLShareDynamicLogging=\\***deploy1\Logs$\%OSDComputerName%


    If you look at the server side logs for deploying with the settings in TaskSequenceID or all in Default you see the following difference early in the log file in the OSDNetworkJoinType value.

    TaskSequenceID deployment:

    Default deployment:

    On checking the client side log you see the following:


    Interesting to note that the TaskSequenceID does not appear to be set until after the CustomSettings.ini file has finished being processed. So when the TaskSequenceID is called, the value is blank so nothing is processed...

    Can anyone explain why this is occurring? Is this a known issue?


    • Edited by Duplicate Tuesday, February 9, 2016 9:51 PM
    Tuesday, February 9, 2016 9:45 PM

All replies