none
Linked MDT deployment share ignoring CS/BS.ini RRS feed

  • Question

  • Hi,

    I've created a linked deployment share for MDT 2013, at one of our remote offices, but am having issues with it picking up the CustomSettings.ini or Bootstrap.ini.

    I know these don't copy across with the sync, but I've amended the blanks ones on the remote share. The problem is, when deploying from the share, it seems to be ignoring the CS & BS.ini files completely, in that, I'm presented with, what I suspect is the BDD Welcome screen, despite adding entries in the CS to ignore:

    [Settings]

    Priority=DefaultGateway, Default

    Properties=MyCustomProperty

    [Default]

    SkipBDDWelcome=YES

    OSInstall=Y

    SkipCapture=NO

    SkipComputerName=NO

    SkipLocaleSelection=YES

    SkipAdminPassword=YES

    SkipDomainMembership=YES

    SkipProductKey=YES

    UILanguage=en-GB

    UserLocale=en-GB

    KeyboardLocale=0809:00000809

    SkipTimeZone=YES

    TimeZoneName=GMT Standard Time

    BitsPerPel=32

    VRefresh=60

    XResolution=1

    YResolution=1

    DomainAdmin=xx

    DomainAdminDomain=xx

    DomainAdminPassword=xx

    JoinDomain=xx.xx.xx

    WSUSServer=WsusServer

    SLShareDynamicLogging =LogLocation

    [DefaultGateway]

    0.0.0.0=Ipswich

    0.0.0.0=Ashford

    0.0.0.0=Ashford

    [Ipswich]

    Deployroot=\\ips-server\deploymentshare$

    [Ashford]

    Deployroot=\\Ash-server\deploymentshare$

    Does anyone have any ideas which would cause this? I'm guessing it will be user error somewhere along the line :)

    Thanks
    Tuesday, May 19, 2015 1:44 PM

All replies

  • This is expected.  Customsettings.ini and bootstrap.ini don't sync.  Just like creating media and such you have to populate the customsettings.ini and bootstrap.ini.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, May 19, 2015 5:35 PM
    Moderator
  • DFS-R is a better way to go, if you mark the other member as read-only then you can make sure changes only happen from one share and trickle down to the other, plus lots of bandwidth saved. It also saves you from issues like this.

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


    • Edited by Dan_Vega Wednesday, May 20, 2015 1:25 AM
    Tuesday, May 19, 2015 9:54 PM