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

1. Execution log at %ALTIRIS_EXPRESS_SHARE%\rdpmigration\rmu.log.

2. Timestamp folder created at every execution under %ALTIRIS_EXPRESS_SHARE%\rdpmigration to

store all the data files captured.

Preparing for Migration

To migrate the target servers, RDP and IC server provisioning must be running and on the same subnet. Since RDP and

IC server provisioning are both DHCP and PXE based, they cannot both be actively responding to boot requests at the

same time. Additionally, IC server provisioning will not work with a separate PXE server, namely RDP’s PXE server.

When both products are on the same subnet, the RDP PXE server should be disabled so as not to conflict with IC server

provisioning PXE server and detecting bare-metal target servers.

A DHCP server is required and a separate DHCP server may be used with IC server provisioning. Refer to the DHCP Server

setup chapter in the HP Insight Control server provisioning Installation Guide. Insight Control server provisioning

documentation can be found at www.hp.com/go/insightcontrol/docs.

NOTE: If a hostname is used for the IC server provisioning address, that name must resolve to the correct address for all

the target servers.

Matrix Operating Environment Migration Considerations

In Matrix Operating Environment (Matrix OE) configurations using RDP, there are various considerations as IC server

provisioning is added to the environment. Existing Matrix service templates probably reference software images from

the RDP Deployment Server. Any Matrix services created from those templates will embed the RDP IP address and job

information. Removing RDP from Matrix OE should not be done until all dependencies have been handled. The

remainder of this section provides more details on the appropriate considerations including coexistence of RDP and IC

server provisioning.

IC server provisioning 7.2 and 7.2.1 only supports a single network where the deployment and management networks

are bridged or the target server iLOs are on the same deployment network. This should be considered when migrating

from RDP to IC server provisioning within the Matrix OE. For more information about using single and dual-network

environments for IC server provisioning, refer to the HP Insight Control server provisioning Installation Guide.

IMPORTANT: IC server provisioning 7.3.2 is a full appliance only; there is no update available from previous versions.

Since there is no update for 7.3.2, if you have an existing IC server provisioning 7.3.1 installation and do not want to lose

any of your data, you should remain on 7.3.1. If you want to start fresh and take advantage of the new features in 7.3.2,

you have the option of installing one of the full appliances. The next version of IC server provisioning will allow updates

from version 7.3.1 and version 7.3.2.

IMPORTANT: Since there is no update available from IC server provisioning 7.3.1, Matrix OE 7.3.2 supports IC server

provisioning 7.3.1 and 7.3.2.

Target Servers

Servers currently managed by RDP may be moved to IC server provisioning without redeploying the operating system.

This is accomplished by adding the HP Server Automation (SA) agent to the target server and then removing the Altiris

Deployment Agent from the target server which will remove the connection between RDP and the target server. To

migrate the target servers, RDP and IC server provisioning must be on the same subnet.

NOTE: Target server migration cannot be done with servers managed in the Matrix OE without imposing lifecycle

operating limitations as noted in the previous section.

Manual Procedure

To add the HP Server Automation agent to a managed server and remove the Altiris Deployment Agent