Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
MDT 2012 for Multi Site Deployment

Proposed Answer MDT 2012 for Multi Site Deployment

  • Wednesday, November 28, 2012 3:53 AM
     
     
    Sign In to Vote
    0

    HI All,

       I am looking to build desktop imaging solution for Windows 7 for multiple sites which are connected via hub-spoke network topology.

      each site got Windos 2008 r2 Server and Windows 2003 R2 Servers ( File server0 No DFS but going to do it soon.

      So how do i setup?

    AS

     

All Replies

  • Thursday, November 29, 2012 2:42 PM
     
     Proposed Answer
    Sign In to Vote
    1

    1) Decide on a Master server. This is where you start your replications from. Needs to have good WAN connectivity with the other sites as your are going to move many GB of data

    2) Set up your master server just like any other MDT site.

    3) Define your Linked Deployment Share links (one for each site) on the Master server

    4) Check your replication settings for each site

    5) Replicate away. Keep in mind that CS.INI and BS.INI are specific to the sites and are not replicated

    6) If you use PXE boot, update the boot images for each site and mount them in WDS

    • Proposed As Answer by Tim.Harris Thursday, November 29, 2012 2:44 PM
    •  
     
  • Friday, December 07, 2012 12:54 AM
     
     
    Sign In to Vote
    0

    HI,

      Thanks, So i got following to bit clarify

        4) Check your replication settings for each site 

                     where do i check this?

        5) Replicate away. Keep in mind that CS.INI and BS.INI are specific to the sites and are not replicated

                  What do you mean by this?

       6) If you use PXE boot, update the boot images for each site and mount them in WDS

              So if i add or update MASTER server will not update the boot images in site share? 

       When i deploying client With this link Share, site will not use the Master server location bandwidth isn't it? 

    AS

     
  • Friday, December 07, 2012 1:35 AM
     
     
    Sign In to Vote
    0

    I think he means you can replicate your full deploy, or select items. you can also choose to update or recreate.

    once your replicate go to that server's mdt console, open the shared folder and choose properties and adjust your cs.ini and bootstrap.ini

    once you get that all done you will need to update your boot wims and move them to your wds server for pxe boot.

     
     
  • Wednesday, December 12, 2012 5:58 AM
     
     
    Sign In to Vote
    0

    Hi All,

     I have set the BS.ini as follows and but deployment wizard asking for thespecify which Deployment share to use?

    Settings]
    Priority=Default, DefaultGateway

    [Default]
    SkipBDDWelcome=YES

    [DefaultGateway]
    10.1.150.254=Melb
    10.5.118.254=SYD


    [Melb]
    DeployRoot=\\MELMDT01\OSDeploymentShare$

    [SYD]
    DeployRoot=\\SYDdc02\MDTSYD

    UserID=admin
    UserDomain=xxx.com
    UserPassword=xxx
    SkipBDDWelcome=YES
    SkipUserData=YES

     
  • Wednesday, December 12, 2012 12:44 PM
     
     
    Sign In to Vote
    0

        4) Check your replication settings for each site 

                     where do i check this?

        5) Replicate away. Keep in mind that CS.INI and BS.INI are specific to the sites and are not replicated

                  What do you mean by this?

       6) If you use PXE boot, update the boot images for each site and mount them in WDS

              So if i add or update MASTER server will not update the boot images in site share? 

       When i deploying client With this link Share, site will not use the Master server location bandwidth isn't it? 

    AS

    4) For each linked deployments shares you can specify which selection profile to apply while replicating. So you can replicate just the Application folder for one site and maybe the drivers for another.

    There are also flags:

    • Merge or Replace (I use Replace)
    • Copy Standard folder (that is self explanatory)
    • Automatically update boot images (I leave this off as the winpe boot image gets copied from the remote server to a local temp folder, updated and copied back - as I need to visit the remote servers anyway to apply the updated images to the WDS server might as well do it manually on each server, you might want to do it differently),
    • Access the linked deployemnt-share in single user mode (I am the only one doing this so I have this checked)

    5) Customsettings and bootstrap.ini are not replicated from the master server to the remote servers so that you can have different settings for each remote site (you need BS.INI to be different surely as it contains the share name).

    6) When you update the image from the MDT console you just create it in your deployment share folder structure (boot sub-folder). If you use WDS you need to import this new version of the boot image into WDS using its own console.

    Last question: Yes the remote site will not use the master server (well they could if BS.INI had the master server share name - this is why you need BS.INI to be specific to the remote sites).

     
  • Monday, December 17, 2012 4:42 AM
     
     
    Sign In to Vote
    0

    Thanks, Now my issue is with BS.ini and CS.ini to deploy?  pls look my above post.

     
  • Thursday, December 20, 2012 9:56 AM
     
     
    Sign In to Vote
    0

    I don't use the technique for specifyng multiple sites in CS.INI. I don't have the share name in CS.INI but only in BS.INI. So my CS.INI is generic and valid for all sites. BS.INI doesn't replicate so I can keep one for each site where it contains my share name.

    Examples:

    CS.INI

    [Settings]
    Priority=SetModelAlias, Default
    Properties=ModelAlias

    [SetModelAlias]
    UserExit=ITGModelAliasExit.vbs
    ModelAlias=#SetModelAlias()#

    [Default]
    OSInstall=Y
    UserLocale=en-gb
    KeyboardLocale=en-gb;0809:00000809
    TimeZone=85
    TimeZoneName=GMT Standard Time
    SkipBDDWelcome=YES
    SkipCapture=YES
    SkipAdminPassword=YES
    SkipProductKey=YES
    SkipComputerBackup=YES
    SkipUserData=YES
    SkipTimeZone=YES
    SkipLocaleSelection=YES
    SkipBitLocker=YES
    SkipDomainMembership=YES
    SkipComputerName=NO
    UserDataLocation=NONE
    UILanguage=en-US
    ApplyGPOPack=NO
    FinishAction=None

    BS.INI Site 1:

    [Settings]
    Priority=Default

    [Default]
    Debug=TRUE
    DeployRoot=\\ServerSite1\deploymentshare$
    SkipBDDWelcome=YES
    UserLocale=en-gb
    KeyboardLocale=en-gb;0809:00000809

    BS.INI Site 2:

    [Settings]
    Priority=Default

    [Default]
    Debug=TRUE
    DeployRoot=\\ServerSite2\deploymentshare$
    SkipBDDWelcome=YES
    UserLocale=en-gb
    KeyboardLocale=en-gb;0809:00000809

    etc.

     
  • Monday, January 07, 2013 12:38 AM
     
     
    Sign In to Vote
    0

    HI,

     Thanks, Now i'm bit confuse. So how many MDT Servers you got? My setup like this 1 x MDT 2012 Server in Main Site. all other locations got server shares and only WDS?

    Do i need MDT Server for each location?

    AS

     

     
  • Tuesday, January 08, 2013 4:53 PM
     
     
    Sign In to Vote
    0
    I have 20 servers plus the one on the centre. And yes they all have MDT 2012. This so I can edit the local settings with confidence.