Data Migration from Insight Control server deployment to Insight Control server provisioning

2
Summary
Your Insight Control (IC) server deployment application, previously known as Rapid Deployment Pack (RDP), may contain
customized jobs and scripts you want to use with Insight Control server provisioning. You may also have target servers
that are currently being managed by IC server deployment. The sections in this document provide instructions for
transferring target servers and data from IC server deployment to IC server provisioning.
Within the Matrix Operating Environment (Matrix OE), special consideration should be given when migrating to IC server
provisioning. Refer to the Matrix Operating Environment Migration Considerations section of this document.
IC server provisioning provides equivalent functionality to upgrade firmware, deploy hardware configuration and deploy
operating systems, so not all data will need to be moved to IC server provisioning. Basic steps to follow in migrating the
data:
Copy the OS distribution files from the RDP eXpress share using the media server utility.
Review the IC server provisioning OS Build Plans (OSBPs) and steps to understand what functionality is already
available.
Run the RDP Migration Utility to convert the configuration files and scripts.
Decide which configuration files and scripts need to be moved to IC server provisioning.
Using copy and paste, create equivalent configuration files and scripts in IC server provisioning.
Edit the scripts and configuration files to make sure they do what you want.
Insert the configuration files and scripts into existing OSBPs where appropriate.
Test the new OSBPs.
Migrate one or two targets servers manually and verify work with IC server provisioning.
Migrate the remainder target servers in one execution using the RDP Migration Utility.
This document provides information on both manual and automated procedures for transferring the servers and data
from RDP to IC server provisioning. The RDP Migration Utility automates server and data conversion for many of the
components between RDP and IC server provisioning. The automated processes require RDP Release 7.0 or higher. For
RDP releases prior to Release 7.0, manual instructions for migrating data and target servers are provided, or you may
choose to upgrade to a newer RDP release.
This technical white paper presumes that the reader is familiar with editing, creating, and using RDP jobs and tasks via
the RDP Deployment Server Console. General instructions for using the data within IC server provisioning are provided.
For IC server provisioning installation information, refer to HP Insight Control Server Provisioning Installation Guide.
Insight Control server provisioning documentation can be found at www.hp.com/go/insightcontrol/docs.
RDP Migration Utility
The IC server provisioning virtual appliance package contains a small compressed file that is the RDP Migration Utility.
This command-line utility must be run from the RDP Deployment Server. JRE 1.6 or above is required on the RDP
Deployment Server with the PATH environment variable set properly to point to the java installation directory.
NOTE: Beginning with IC server deployment 7.2 Update 1, the RDP Migration Utility is included with that product as well.
The RDP Migration Utility also uses HTTP port connection 8081 between RDP and IC server provisioning to check the IP or
hostname provided in the command line, as well as between the target server and IC server provisioning in order to
download the SA agent during the target server migration. Verify this port is not blocked on RDP and target server.
To install the RDP Migration Utility on the RDP Deployment Server, extract the utility package contents to
%ALTIRIS_EXPRESS_SHARE%\rdpmigration where %ALTIRIS_EXPRESS_SHARE% is the RDP eXpress share
directory location. For RDP installations via the Insight Management DVD, the RDP eXpress share is C:\Program
Files\HP\RDP\Deployment Server.
To determine all available command-line arguments, run rmu.exe /h or rmu.exe /?
The RDP Migration utility generates two data items: