Using the LocationServer.xml feature in MDT 2013

By Johan Arwidmark / May 28, 2015

MDT Lite Touch has a built-in functions to prompt for deployment share via the LocationServer.xml file. Most times I use the default gateway property to have clients automatically select the right server depending on what subnet they are on, but sometimes prompting can be useful too.

Note: By default the logic in this feature cleans any credentials provided in bootstrap.ini.

The LocationServer.xml feature

This feature allows for MDT to dynamically generate bootstrap.ini values for DeployRoot and is implemented as follows:

Create the LocationServer.xml file, and specify the various deployment servers.
Copy the LocationServer.xml file to the \Deploy\Control folder in your boot image. The easiest way is via the Extra directory to add feature on the deployment share.
Modify the Bootstrap.ini file to not include any DeployRoot value (since the LocationServer.xml feature dynamically sets it).
Update the deployment share (which updates the boot image), and replace the boot image on your WDS server.

Sample file

Here is a sample LocationServer.xml file that allow you to select between two deployment servers.

<?xml version="1.0" encoding="utf-8" ?>
<servers>
    <QueryDefault></QueryDefault>
    <server>
        <serverid>1</serverid>
        <friendlyname>
          ViaMonstra HQ, New York, USA
        </friendlyname>
        <UNCPath>\\MDT01\MDTProduction$</UNCPath>
    </server>
    <server>
        <serverid>2</serverid>
        <friendlyname>
          ViaMonstra BO, Stockholm, Sweden
        </friendlyname>
        <UNCPath>\\MDT02\MDTProduction$</UNCPath>
    </server>
</servers>

Deployment Wizard

This is how the deployment wizard looks after enabling the LocationServer.xml feature.

Happy Deployment, Johan