1. In the Jobs pane in the Deployment Console, select a job. 2. In the Details pane, click Add and select Create Disk Image.
3. In the Create Disk Image dialog, select an imaging tool from the drop-down list. You can select RapiDeploy (Text mode), RapiDeploy (Graphics mode), RapiDeploy (Linux mode), ImageX, Mac Image or Ghost.
Advanced: Reset Connection Yes Yes Yes
Advanced: Install Automation Partition Yes
Advanced: Get Inventory Yes Yes Yes
Advanced: Reject Connection Yes Yes Yes
Advanced: Uninstall Windows Agent Yes Yes No
Advanced: Install BIS Certificate No No Yes
Advanced: Remove BIS Certificate No No Yes
Advanced: Apply Regular License Yes Yes Yes
New Job Wizard Yes Yes Yes
New Group Yes Yes Yes
New Computer Yes Yes Yes
Rename Yes Yes Yes
Delete Yes Yes Yes
Change Agent Setting Yes Yes Yes
Permissions Yes Yes Yes
Job Scheduling Wizard Yes Yes Yes
Create an image file by using the New Job Wizard or adding the task when building new jobs. You can distribute the disk image file using the
Distribute a Disk Image task. This task will run Altiris RDeploy.exe from the console to capture and migrate hard disk images. See New job wizard on page 146, Building new jobs on page 150, and Distributing a disk image on page 162.
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.
Prerequisite: To store images locally on the managed computer’s hard drive, you must have a hidden automation partition installed on the managed computer's hard disk with the required disk space to hold the images you want to store.
Caution
When imaging computers where images are stored on the managed computer’s hidden automation partition, use the option to remove the automation partition only when you want to clear all images from the computer.
7. Select Prepare using Sysprep to use Sysprep to prepare the system for imaging. 8. From the Operating System drop-down list, select the operating system or Add
new to open the OS Product Key dialog and select the OS Information.
9. Click Advanced Settings. This opens the Sysprep advanced settings dialog. See Advanced Sysprep settings for creating a disk image on page 161.
10. (Optional) Select the Do not boot to Production option to create an image of the hard disk while booted to Automation without first booting to Windows to save network settings (TCP/IP settings, SID, computer name, and so on). If you select this option, these network settings are not reapplied to the computer after the imaging task, resulting in network conflicts when the computer starts.
11. From the Automation pre-boot environment (DOS/WinPE/Linux) drop-down list, select the required pre-boot environment to perform the Create Disk Image task in the selected pre-boot environment. By default, the Default Automation (Auto-select) type is selected.
Note
ImageX requires a WinPE x86 pre-boot environment.
12. (Optional) To select Media Spanning and additional options, click Advanced. See Create disk image advanced on page 162.
13. Click OK (if you are using the New Job Wizard) or click Next.
14. (Optional) Set Return Codes. See Setting up return codes on page 193.
15. Click Finish. The task appears in the Task list for the job. The disk image is created when you run this task.
Tip
If an imaging job fails on a managed computer, the Deployment Agent
Configuration page appears on the client computer. This page displays a prompt to confirm whether the user wants to configure the client computer or restore the original settings. On the client computer’s screen, select Cancel > Restore Original Settings.
See also Deployment tasks on page 155.