Microsoft Deployment Toolkit
Documentation Library Create a LocationServer.xml File to Support Multiple Locations |
The simplest method for creating and using LocationServer.xml is to create a LocationServer.xml file and add entries for each deployment server in the environment (this can be either at the same location or at different locations).
Construct the LocationServer.xml file by creating a new section for each server, and then adding the following information:
· A unique identifier
· A location name, used to present an easily identifiable name for that location
· A UNC path to the MDT server for that location
Listing 16 illustrates how the LocationServer.xml file is created using each of these properties using a sample LocationServer.xml file configured for multiple locations.
Listing 16. Example LocationServer.xml File to Support Multiple Locations
<?xml version="1.0" encoding="utf-8" ?>
<servers>
<QueryDefault></QueryDefault>
<server>
<serverid>1</serverid>
<friendlyname>
Contoso HQ, Seattle, USA
</friendlyname>
<UNCPath>\\STLDS01\Deployment$</UNCPath>
</server>
<server>
<serverid>2</serverid>
<friendlyname>
Contoso NYC, New York, USA
</friendlyname>
<UNCPath>\\NYCDS01\Deployment$</UNCPath>
</server>
</servers>
Using this format, specify different server entries for each location (as shown in Listing 16) or for situations in which there are multiple servers within a single location by specifying a different server entry for each server at that location, as shown in Listing 17.
Listing 17. Example LocationServer.xml File to Support Multiple Servers at Multiple Locations
<?xml version="1.0" encoding="utf-8" ?>
<servers>
<QueryDefault></QueryDefault>
<server>
<serverid>1</serverid>
<friendlyname>
Contoso HQ DS1, Seattle, USA
</friendlyname>
<UNCPath>\\STLDS01\Deployment$</UNCPath>
</server>
<server>
<serverid>2</serverid>
<friendlyname>
Contoso HQ DS2, Seattle, USA
</friendlyname>
<UNCPath>\\STLDS02\Deployment$</UNCPath>
</server>
</servers>
Related Topics