RDP 6.8 Deployment Issue

[B-Mac]

Server = DL360G5, 6 physical 146GB drives
Drives 1+2 RAID 1:
- Logical Drives C: 36GB, D: 36GB, V: 72GB
Drives 3+4 RAID 1:
- Logical Drive E: 146GB
Drives 5+6 RAID 1:
- Logical Drives F: 36GB, G: 108GB

I'm using RDP 6.8 (Build 282) SP1.

I run the default task "Read ProLiant ML/DL/BL Array Configuration {WinPE}" from the manually built server (using SmartStart) and it writes my array config to an ini file. I run the default task "Erase ProLiant ML/DL/BL Array Configuration {WinPE}" and it erases the array and reboots.
I copy/modify/run the "Write ProLiant ML/DL/BL Array Configuration {WinPE}" with the "Deploy Array Configuration" task using the newly created ini as the input file, and it creates the array correctly.

I then try to Distribute Disk Image (C: drive only in the image), which downloads the image, but hangs immediately at the cursor when booting to C: drive. The image does not boot, whether using Advanced properties of a fixed size or 100% and only a single partition is showing in the Advanced properties. What am I doing wrong?

If I use the manual build method, push the Altiris client, capture the image, then deploy the image to the same server, it works perfectly. I need to be able to deploy the image to a fresh DL360G5, so HOW do I do it?

Please help.

- Brian

[B-Mac]

Anyone?

[Neal Bowman]

Hi Brian,

One step that we found needed to be done after creating the arrays is to perform a reboot before we distribute any image to the server.

Here is a summary of the steps we have defined in our environment:
1- Deploy hardware config (%server%.xml)
2- Reboot
3- Erase Array config
4- deploy array config (%server%.ini)
5- Reboot
6- deploy image (NTFS.IMG)
7- reboot
8- push server image down using ImageX (Standard.wim)
9- modify sysprep.inf
10- Push HP PSP files, other updates
11- Reboot
12- Install PSP
13- Reboot

Hope this helps,
Neal

[B-Mac]

Thanks for replying! Can you explain what you are deploying in step 6 in NTFS.IMG and why you deploy another image in step 8?

In my scenario, I'm using one step (with a reboot as a final step) to deploy my image file (IMG format, captured using RDP)

Thanks!
-Brian

[Neal Bowman]

Brian,

What the NTFS.IMG file does is create a blank 4G partition on the c: (first logical drive) and marks the partition as active. Rebooting in step 7 then allows the drive to be seen as a boot device, even though there are no files or OS installed yet. Step 8 actually lays down the sysprepped image file. We are using the WAIK (Windows Automated Installation kit) to create a WIM image of our server 2003 load. You use the Altiris tools to create your image file, or use other tools such as Ghost or PowerQuest to create and deploy these images. Or you opt to do a scripted unattended installation after the reboot in step 7.

Hope this helps,
Neal

[B-Mac]

Good info! So what steps did you take to create your blank 4GB partition? Did you just boot to a shell and use diskpart to create/active the C: drive, then capture that using the RDP quick disk image?

-Brian

[Neal Bowman]

Brian,

The NTFS.IMG file is included with RDP. You should be able to find it in the express share under Deployment server\lib\images folder.

If you look in the pre-built jobs from the RDP console, there should be a task under Server Deployment Toolbox/2B- OS Installation (Scripted)/ Deploy Windows Server 2003 STandard (ProLiant ML/DL/BL){WinPE}.

From there, you can follow the files and folders to deploy your job.

Neal

[B-Mac]

How do I capture multiple logical windows drives in one capture process?

For example:

I have carved partitions for drives C:, D: and V:, all running on a RAID 1 of 2x146GB physical drives.

How do I capture and restore all logical drives?

I currently only see the C: drive, and can see the other partitions, but no logical drives.

Please help!

P.S. I have two other mirrored pairs that I will also need to capture that each have logical drives E:, F:, and G:.

Cheers!
- Brian

[Neal Bowman]

Brian,

in order to capture images for C, D, and V, you will need to create two additional tasks, added to the initial task of capturing the image from C.

Create a new job and copy over the task you currently use to capture C. Now copy this task twice within the job. Modify each of the last two tasks to point to the logical drives for D and V. Make sure you save the image name so you don't overwrite the C image.

Neal

[Adrian Clint]

Brian,

Something you need to clarify is how you have partitioned your drive.

If you have partitioned your disks within the Array Config Utility (ACU) then RDP/Altiris sees these as separate "Disks".

If you have used windows to partition your single ACU partition then RDP/Altiris sees these as "Partitions"

So say you used the ACU to split a 146GB RAID 1 set into 4 "Disk" partitions of 100MB, 10GB, 20GB and 16GB. Then you used windows to split the first 1 "disk" partition into 2 windows partitions of 40/60GB each then you would have

Disk 1 - Partition 1 = 60GB
Disk 1 - Partition 2 = 40GB
Disk 2 - Partition 1 = 10GB
Disk 3 - Partition 1 = 20GB
Disk 4 - Partition 1 = 16GB

So if you tried to capture what you may think is disk 2 - you are trying to capture disk 1 partition 2 or vice versa.

From what I got told last week on an altiris course a Capture Disk Image task will capture All partitions on a disk. So a capture disk image of "Disk" 1 will capture 3 partitions. (Not sure of this myself but pleaze verify)

You can reference disks and partitions on
as -p1 (partion 1) or -d2 (disk 2) on the advanced buttons command line on the image task. Increment no for additional partitions

so

-d1 -p1 would capture the 60GB &
-d2 would capture the 10GB
-d1 -p1 -p2 would capture only the 40 & 60GB (so should -d1 as long as there are only two windows partitions on disk1)

Download
http://www.altiris.com/upload/deployment_adv_002.pdf and lookup the command line options for rdeploy


I agree with Neil that you should reboot after a deploy array config job.