BDD Scenarios: Automating Application Deployment

Scenario 1: Using Role Values Directly in CustomSettings.ini

Published: March 8, 2005

Custom key values can be used directly in the CustomSettings.ini file to find a section that has the same name as the current value of the variable. For example, assume the file has been updated to include the following lines in the CustomSettings.ini.

[Settings]
…
Priority=MacAddress, DefaultGateway, Role, Default
CustomKeysUserData=UDShare, UDDir, UDProfiles, SLShare, OSInstall, 
Packages(*), Administrators(*), PowerUsers(*), DriverPath(*), Role
…

Now, after searching for custom key values using the computer's MAC address and default gateway, it will look for a section whose name matches the current value of the Role custom key. For example, assume that the CustomSettings.ini file has the following computer-specific section, located using the MAC address of the current computer.

[00:03:FF:CB:4E:C2]
Role=Accounting

This would assign the value "Accounting" to the Role custom key. That value would then be used (based on the inclusion of "Role" on the Priority list) to find a section in the CustomSettings.ini file named Accounting.

[Accounting]
Packages1=XXX00001-Program name 1
Packages2=XXX00002-Program name 2
Packages3=XXX00003-Program name 3

The three packages specified would then be installed on the computer during the state restore phase of the deployment process.


**
In This Article
**