Symantec ALTIRIS DEPLOYMENT SOLUTION 6.9 SP4 - V1.0, Руководство пользователя

Страница: 440 / 503

Deployment Solution 440
Tokens: Dynamic Database Access
requires a Sysprep.inf file. This file is used, among other things, to set the NetBIOS
computer name for a computer and which Domain the computer will belong to (see the
sample Sysprep.inf file in the figure to the right.)
If the image being deployed to the computers contained this Sysprep.inf file and no
other changes were made, all computers would end up with the same computer name
and Domain when the Sysprep.inf files was used to configure the computers being
deployed. To solve this dilemma, a token replacement
template file is used.
The token replacement template file is a copy of the text file, which after being edited
needs to be copied to each computer. In this example it is theSysprep.inf file. The
unique text files that will be sent to the individual computers are created by taking the
contents of this template file and adding the unique data using tokens. Therefore, any
data in the template file that needs to be unique must be replaced with an applicable
token.
Example: to ensure that every computer gets a unique computer name, the Sysprep.inf
file is edited to use a token to provide this information instead of using the real
computer name. As seen in the figure to the right, this is accomplished by placing the
%NAME% token after the
ComputerName entry. Likewise, the entry that determines the
Domain is changed to use the %DOMAIN% token instead of the real Domain name.
After the tokens have been added as needed, this file is saved in the Deployment Server
directory structure and becomes the template file.
After going through the token replacement process, the tokens are replaced with unique
data from the Deployment Server database and a new file containing that information is
created. The end result is that the new file created would now have an entry such as –
ComputerName=Bryce in one file while another file might have an entry such as –
ComputerName=Jackson .
Template File Rules
The following template file rules are as follows:
z
The template file can have as many Altiris tokens as needed.
z
The template file needs to be saved in the Deployment Server directory or in one of
its subdirectories. Example: the template file may be saved in the \Deployment
Server\temp directory.
By default, the Deployment Directory is located at C:\Program
Files\Altiris\eXpress\Deployment Server and is the directory where Deployment
Server was installed. It is also referred as the Deployment Share.
The Token Replacement Process
The method of converting the template file to a unique file is accomplished as follows:
z
The template file (in this example - Sysprep.inf) is created with the necessary
tokens and is placed in the
Deployment Server\temp subdirectory.
z
A Job is created containing a Run Script task.
The Run Script task contains the command(s) needed to invoke the token
replacement process and the specific paths for all files needed in this process. (See
“The Run Script Task” on page 1-32 for the Run Script task syntax.)
z
This Job is then run on selected target computers.