Altiris Deployment Solution™ from Symantec User’s Guide 158
RDeploy Options
RDeployT is the default imaging executable. This facilitates the imaging of thin client
computers. The following are the RapiDeploy options for imaging:
Graphical Mode (RDeploy). Select this option to run the RDeploy in a GUI mode.
Text Mode (RDeployT). Select this option to run the RDeploy in a text mode.
Linux (RDeploy). Select this option to run the RDeploy in Linux mode.
You can select the ImageX or Mac Image option for imaging. If you select ImageX,
the image is created as a .WIM file. If you select Mac Image, the image is created as
a .DMG file. For information on creating a Mac Image, see Creating a Mac image on
page 159.
You can also select the Ghost option for imaging. If you select Ghost, the image is
created as a .GHO file. For information on creating a Ghost Image, see Creating a
Ghost image on page 160.
Important
Linux (RDeploy) and Ghost options are available only when the ImageTools.ini file is
stored in the eXpress folder.
4. Enter additional parameters in the Additional Parameters field.
You can add command-line options specifically for the RapiDeploy program to run
imaging tasks. See Command-line Switches in the Deployment and Migration Guide.
5. Enter a path and file name to store the disk image file. You can store image files to
access later when a managed computer is assigned a job that includes the image
file.
The default file name extension is .IMG. Saving image files with an .EXE extension
converts them into self-extracting executable files (the run-time version of
RapiDeploy is added in the file). You can also save ImageX files with a .WIM
extension, a Mac image with a .DMG extension, and a Ghost image with a .GHO
extension.
If WinPE is used, Deployment Solution supports UNC and DFS paths in the Name
field. For example, you can type \\My_Server\My_Volume\myimagefile.img in the
Name field.
6. Select Disable image path validation if you want to store the image file outside of
the Deployment Share file structure. If you do not select this option and do not
specify a Deployment Share path, a warning message appears, reminding you to
configure your automation process to use the path indicated in the Name field. You
can still save your image to a location outside of the Deployment Share file structure
even when you do not select this option. This option only eliminates the warning
message. You can use this option to store images locally on the managed
computer's hard drive or to an additional server used to store images.
If you typed a UNC path in the Name field and the server does not have access to
the path, check to disable image path validation. Otherwise, the process fails.
When storing images locally on the managed computer's hard drive, ensure that you
enter the path relative to the managed computer (Example: C:\myimage.img).
When you store an image locally on a managed computer instead of a file server,
you save server disk space and reduce network traffic.
To Next Page
Loading...
