TechNet Home > Desktop Deployment > Tasks & Tools > Deployment Process

BDD Scenarios: Automating Application Deployment

Scenario 2: Using Default Gateway Values Directly in CustomSettings.ini

Published: March 8, 2005

In order to select packages based on the default gateway values of the computer, the DefaultGateway literal value should be included in the "Priority" line of the CustomSettings.ini file.

[Settings]
…
Priority=MacAddress, DefaultGateway, Default
…

With all other values, this would cause the Zero Touch Installation rules engine to look for a section matching one of the default gateway values of the computer. However, with the DefaultGateway value, special processing is performed: the rules engine will check a DefaultGateway section to find the name of the real section that should be used.

[DefaultGateway]
192.168.0.1=HOUSTON
11.1.1.11=REDMOND
172.28.20.1=REDMOND
…

In this case, the "REDMOND" section would be used for two different default gateway values (11.1.1.11 and 172.28.20.1), while the "HOUSTON" section would be used for the third value (192.168.0.1). Location-specific packages can then be specified in those sections.

[REDMOND]
Packages1=XXX00004-Program name 4
Packages2=XXX00005-Program name 5

[HOUSTON]
Packages1=XXX00006-Program name 6
Packages2=XXX00007-Program name 7
Packages3=XXX00008-Program name 8

Based on this, different packages (and a different number of packages) would be installed on HOUSTON computers versus REDMOND computers.


**
In This Article
•Executive Summary
•Introduction
•Scenarios
•Scenario 1: Role-Based Application Installation
•Scenario 1: Using Role Values Directly in CustomSettings.ini
•Scenario 1: Using Role Values to Query a Database
•Scenario 1: Retrieving the Role Value from the Database
•Scenario 2: Location-Based Application Installation
•Scenario 2: Using Default Gateway Values Directly in CustomSettings.ini
•Scenario 2: Using Default Gateway Values to Query a Database
•Scenario 2: Using Default Gateway Values to Query a Database by Site
•Scenario 3: Hardware-Specific Application Installation
•Scenario 3: Using Make and Model Values Directly in CustomSettings.ini
•Scenario 3: Using Make and Model Values to Query a Database
•Scenario 4: Computer-Specific Application Installation
•Scenario 4: Using MAC Address Values Directly in CustomSettings.ini
•Scenario 4: Using MAC Address Values to Query a Database
•Scenario 5: Dynamic Computer-Specific Application Installation
•Scenario 6: User Self-Provisioned Computer-Specific Application Installation
•Scenario 7: User-Customized Dynamic Computer-Specific Application Installation
**