How To Perform A Windows Image Deployment On Servers With Two Or More Logical Drives On Separate Physical Drives
Article: 153
Applies to: Releases 2.xx or greater
The imaging jobs provided with the Rapid Deployment Pack will require modification to capture
and deploy two or more logical drives on separate physical drives.
This solution is required for target servers running Windows.
IMPORTANT:If one of the logical drives on the target server is designated the "F"
drive, the image capture will fail with the error, "System cannot find the file specified."
This error is explained in an Altiris Knowledgebase (Article ID: 33065), which can be found at
http://kb.altiris.com.
An alternate solution is to rename an existing "F" drive with another designation.
NOTE: Capturing the drives
on a target with Red Hat Linux and Logical Volume Manager (LVM), will
capture all drives appropriately since rdeploy treats the LVM volume as one drive.
For Red Hat Linux without LVM, refer to Knowledge Base article
Red Hat Linux Image Deployment On A Server With Multiple Drives Causes An
"Invalid Partition" Error (Article 128).
| 1. |
On the Deployment Server, copy and rename the appropriate imaging capture job depending on your RDP release.
For example, in Release 3.80, use the Capture Windows 2003 Sysprep Image job from the
Server Imaging folder.
|
| 2. |
Modify the Create Disk Image task in the new job to use a new disk image filename.
Optionally, add the rdeploy command line switch, -d1, in the Additional Parameters field.
This task will capture the first drive.
Refer to the Altiris Deployment Solution Reference Guide
for additional information on rdeploy command line switches.
|
| 3. |
For each additional drive, add a Create Disk Image task immediately
after the modified Create Disk Image from step 2.
| a. |
Use a unique disk image filename.
|
| b. |
Add the rdeploy command line switch, -dX, where X
is the drive number.
|
| c. |
Select Do not boot to Windows or Do not boot to Production
to prevent unnecessary reboots.
|
| d. |
Select WinPE Managed (32-bit) as the Automation pre-boot environment.
|
| e. |
Do not select Prepare using Sysprep for data drives.
|
|
| 4. |
Copy and rename the appropriate imaging deploy job depending on your RDP release.
For example, in Release 3.80, use the Deploy ProLiant ML/DL/BL + Windows 2003 Sysprep Image + PSP job from the
Server Imaging folder.
|
| 5. |
Modify the Distribute Disk Image task in the new job to deploy the first drive.
| a. |
Use the corresponding disk image filename from the image capture job in step 2.
|
| b. |
Optionally, add the rdeploy
command line switch, -d1, in the Additional Parameters field.
|
| c. |
Do not select Automatically perform configuration task after completing this imaging task.
|
|
| 6. |
For each additional drive, add a Distribute Disk Image task immediately
after the modified Distribute Disk Image from step 5.
| a. |
Use the corresponding disk image filename used in step 3.
|
| b. |
Add the rdeploy command line switch, -dX, where X
is the drive number.
|
| c. |
All Distribute Disk Image tasks, except for the last drive,
should have the Automatically perform configuration task after completing
this imaging task not selected. Only the Distribute Disk Image task
for the last drive should have this checkbox selected.
|
| d. |
Select WinPE Managed (32-bit) as the Automation pre-boot environment.
|
| e. |
Do not select Prepared using Sysprep for data drives.
|
|
|
Printable version
