One of the processes will be copying the files. Importing the jobs will be a second part, third will be changing the global options, forth will be changing the PXE settings and last step is to copy the os distributions to the osdist folder. So, in the end starting a new server with HP RDP would be a better idea.

nelo

a new RDP server is not an option as i stated in the original post due to network constraints (ie lots of small sites with servers and desktops sharing a subnet)

There are not that many global settings and the same PE boot image will work for both as i have found in my testing.

I second sforsythe's motion to figure this out. We have an infrastructure that is working very well right now and we would not like to disturb that. I have loaded the RDP in my test environment and it seems to have "re-branded" everything "RapidDeploy". I get to talk with some HP people in training week after next. I'll post the results if I figure anything out.

The HP RDP PIM is not a free add-on and any extraction from an existing installation of RDP into a seperate Altiris DS server would be a violation of the HP's EULA. The only authorized installation method for the HP RDP PIM is to install RDP. My suggestion is to install RDP first on a server and then add DS licenses as needed for other clients and servers. I know this may not be an option for you.

This may seem combersome but other methods of obtaining or installing the HP RDP PIM will violate the HP RDP EULA.

Joel

Bummer. Do you know how this affects applying future DS patches and hotfixes? Can you apply the DS ones to an RDP install?