Custom Tokens - Symantec ALTIRIS DEPLOYMENT SOLUTION 6.9 SP4 - V1.0 Manual

Custom Tokens

%
#
Alias
^
!
@
Deployment Solution
When the Job is executed the following happens:
The template file (Sysprep.inf) is examined and all tokens are located.
The unique token values for each computer are located in the Deployment Server
database and are used to create a new file for each computer.
The tokens in the new files have now been replaced with their applicable values and
the files are saved in the Deployment Server directory path specified in the task.
The name of the new file created is determined by a token variable used in the task
allowing each new file to have its own unique name.
Each unique file is then copied to the applicable target computer. As the files are
copied, they are renamed back to the correct name needed. In other words, all
computers will end up with a file by the exact same name (this may or may not be
needed depending on what this process is being used for.)
The destination of the file on the target computer and its final name are determined
by the Run Script task in the Job.
Custom tokens can be defined in a script or answer file to extract data from any MS SQL
Server database table. This is most commonly used when creating custom tables to
store additional computer inventory information. This token replacement feature allows
you to specify any SQL database, look up a specified value, and replace the custom
token with the value from the selected database (whether it resides on the local
computer or not).
Syntax One
%#Alias^!table name@column name%
Identifies the opening and closing of a variable token in the script.
Indicates that this is a custom token.
Specify the alias for an external database set up in the Tools > Options
> Custom Data Sources dialog. See
page 86.
When used, this will provide the information and credentials to gain
access to an external SQL database. If the Alias option is not used, the
values will be obtained from the same Deployment Server database the
Job containing this token is using.
Indicates that this is a global identifier token. All tokens by default will be
looked up using the Computer_ID value for which the token ID is being
replaced. This global identifier tells Deployment Solution to NOT use the
value in the computer_ID column. Instead, it will use the first value found
in the specified table.
Specifies that the following text is the table name in the Deployment
Database. This field is required for all user-defined tokens.
Specifies that the following text is the column name in the table. This field
is required for all user-defined tokens.
Examples:
Tokens: Dynamic Database Access
Custom data sources options on
441