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

RDP coexists with IC server provisioning on same broadcast domain

This configuration is not recommended for the Matrix Operating Environment.

As with the case of removing the RDP Deployment Server, existing services which utilized RDP will fail lifecycle

operations including, but not limited to, flexing up of new servers and erase disk. This is true even if target servers are

migrated. New services created from service templates using RDP would fail initial provisioning. To overcome these

limitations it is necessary to delete existing services utilizing RDP services and recreate them from templates utilizing

Insight Control server provisioning. Use this option only if the loss of lifecycle operations for pre-existing Matrix services

is acceptable.

IC server provisioning replaces RDP with existing Matrix Operating Environment services

This configuration is not recommended for Matrix Operating Environment.

If the RDP Deployment Server is removed or target servers are migrated to IC server provisioning, some service lifecycle

operations will fail. These operations include, but are not limited to, flex-up of new servers and erase disk. To

overcome these limitations, it is necessary to delete existing services utilizing RDP services and recreate them from

templates utilizing Insight Control server provisioning. Use this option only if the loss of pre-existing lifecycle

operations Matrix OE is acceptable.

Removing RDP-dependent resources from Matrix OE

When no Matrix services exist which are dependent on RDP and there are no templates which can be used which are

dependent on RDP, the RDP Deployment Server is no longer required. If the architect had chosen to keep RDP-based

service templates defined but not published, they should be aware that if they are published, the service creations will

fail. Thus, they may choose to delete those templates.

If RDP had been on a separate network from IC server provisioning, the removal of RDP means that deployment network

is no longer required and the network can be un-configured from Matrix infrastructure orchestration, and removed from

all service templates.

Limitations

The following limitations should be considered when planning to use IC server provisioning and Matrix:

 The IC server provisioning Add Server to Domain script cannot be used to join a Windows target server to a

domain. Servers provisioned by Matrix can join a domain via an Operations Orchestration workflow.

 For the release prior to IC server provisioning 7.3.1, the default RHEL 6.4 KVM OS Build Plan will fail during the

post-installation customization for target servers provisioned with Matrix. Prior to the OS installation,

changes are required to the kickstart file referenced by the OS Build Plan. With IC server provisioning 7.3.1 this

is no longer a limitation.

For details of the required changes, see the HP Matrix Operating Environment Release Notes. Future IC server

provisioning releases will resolve these limitations.