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

5
b. Deploying the ProLiant HW Add Migrated Windows Server or ProLiant HW Add Migrated Linux
Server OSBPs on each migrated target server. The OSBP will boot the target server into a service OS,
register the iLO, and then boot the target server back to the production OS.
Note: It is assumed that /sbin/hpbootcfg exists on RDP managed Linux-based target servers.
This utility is installed during an RDP operating system installation and sets the one-time boot to
PXE which is used by the ProLiant HW Add Migrated Linux Server OSBP.
Automated Procedure
The RDP Migration Utility provides the ability to either
import the RDP migration jobs and migrate all ProLiant G6, G7, and Gen8 servers running a Windows, Red Hat
Linux, or SUSE Linux x64 IC server provisoning-supported version in one execution, or
import the RDP migration jobs that will allow the user to manually migrate RDP managed servers individually
with the drag-n-drop feature.
ProLiant G5 or earlier servers or Integrity servers are not automatically migrated since not supported by IC server
provisioning. Virtual machines are also not automatically migrated even though support by IC server provisioning via
the Insight Control server provisioning How to Deploy to a Virtual Machine technical white paper. Finally, ProLiant
servers running operating systems, other than mentioned above, are not automatically migrated or may not complete
the RDP migration jobs successfully.
IMPORTANT: Running the RDP Migration Utility will overwrite any existing migration jobs with the same name and
remove the history of the previously run instances. If changes were made to the migration jobs, they should be renamed
to not lose those changes.
NOTE: With the RDP Migration Utility 7.2, the target server will still be on-line in RDP after the reboot. The Run Script
task used to uninstall the Altiris agent for Linux run as unknown user and services are back up once rebooted. With the
RDP Migration Utility 7.2.1 or later, this is no longer an issue.
To migrate all servers in one execution to IC server provisioning
1. From the RDP server and rdpmigration folder, run rmu.exe /targetservers ICSP_DEPLOYMENT_IP
/reboot ICSP_APPLIANCE_IP where ICSP_DEPLOYMENT_IP is the IP address of the Deployment
Interface and ICSP_APPLIANCE_IP is the IP address of the Appliance interface of the IC server provisioning
appliance. The /reboot parameter will reboot the target servers using IC server provisioning OSBPs to
register the iLO. To manually register the iLO without rebooting the target servers, remove /reboot
parameter and refer to Step 7.
NOTE: The /reboot parameter is available with RDP Migration Utility 7.2.1 or later and requires the
Appliance interface IP address.
2. Enter the IC server provisioning appliance administrator user name and password. The entries for these values
are masked by asterisks. After three failed attempts the utility will exit.
3. Confirm to migrate and reboot all applicable target servers.
4. In the Deployment Server Console Computers pane, verify that a computer folder, Migrated_Targets, was
created and the migrated target servers were moved there.
5. In the Deployment Server Console Jobs pane, verify that two job folders, one for Windows and one for Linux,
were created and a job in each folder were imported.
6. In IC server provisioning, verify the targets are listed in the Servers view with their Windows computer name or
Linux hostname.
7. If the /reboot parameter to rmu utility was not used and before an OSBP can be run on a migrated target
server, the server’s iLO must be registered with the IC server provisioning. This can be done by either
a. Adding each migrated target server’s iLO information manually. From IC server provisioning Servers
page, choose Actions > Add Server, enter the iLO IP address and credentials of a target server and
select Do not boot to maintenance. Choose Add to initiate the iLO registeration or Add+ to enter
more IP addresses.
b. Deploying the ProLiant HW Add Migrated Windows Server or ProLiant HW Add Migrated Linux
Server OSBPs on each migrated target server. The OSBP will boot the target server into a service OS,
register the iLO, and then boot the target server back to the production OS.