Creating Unique Files Using Tokens; Tokens; Token Replacement Template Files - Symantec ALTIRIS DEPLOYMENT SOLUTION 6.9 SP4 - V1.0 Manual

Creating Unique Files Using Tokens

Tokens

Token Replacement Template Files

Deployment Solution
Explanation of Script
FS2 is the alias name.
hardware is the table name
Ram_Free is the column name to find the value in.
If a job using the above script was assigned to the PC-1 computer (with the computer_id
of 500001), the values specified are located in the database and appear on the client's
computer. The message shows the DS database search results.
User's Display Message
C:\
This computer has 213 MB of free RAM
Press any key to continue...
There are times, during the deployment of a computer, where the computers being
deployed need a unique file to complete the deployment process. Example: when using
the Microsoft System Preparation (sysprep) program, a unique configuration file is
needed to ensure that each computer gets a unique computer name and that it gets
assigned to the correct Domain (among other things.) An answer file used to perform
unattended operating system installations is another example. In both of these
examples, much of the configuration file is the same for all computers being managed
with only a portion of the file contents needing to be unique.
The challenge is to get a file with the unique entries to the computers being managed
without manually visiting each computer and without having to create each file
manually.
To meet the demands of this challenge, Deployment Server has the ability to
automatically create and distribute a unique text file to meet these needs. This process
is known as the Token Replacement Process.
The token replacement process is accomplished using a template (reference) file which
is automatically customized as needed through the use of tokens (variables) and saved
as a unique file. This unique file is then sent to the individual computer. (See Figure
below.)
An Altiris token is a type of variable that can be replaced with unique data from the
Deployment Server database. Each computer can have its own unique value for each
token. Example: the token name of %NAME% stores the name of a computer being
managed as seen in the Deployment Server console view, while the token name of
%DOMAIN% stores the Microsoft Workgroup/Domain a computer belongs to. Depending
on the individual computer, there may or may not be a value stored in the Deployment
Server database for every possible token.
Token names are case sensitive. See
To understand the token replacement template file, consider the needs when using
Microsoft's System Preparation program (Sysprep.) When using Sysprep, each computer
Tokens: Dynamic Database Access
"System Tokens" on page 436.
439