Technical white paper Data Migration from Insight Control server deployment to Insight Control server provisioning Table of contents Summary 2 RDP Migration Utility 2 Preparing for Migration 3 Matrix Operating Environment Migration Considerations 3 Target Servers Manual Procedure Automated Procedure 3 3 5 Jobs 6 Images from Image Captures Images Created with Symantec rdeploy Utility Images Created with Symantec Ghost Images Created with ImageX 7 7 7 7 Hardware Configuration and Operating Syst
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.
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.
1. Determine the SA agent filename from http://xxx.xxx.xxx.xxx:8081 where xxx.xxx.xxx.xxx is the Deployment IP address or DNS name of the IC server provisioning virtual appliance. Look for the files with .current extension. There are different agent files depending on the operating system version and architecture type. Table 1: SA Agent Files Operating System SA Agent to download Windows 2008 x64 opsware-agent-NT-6.0-X64.current Windows 2008 R2 x64 opsware-agent-NT-6.1-X64.
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.
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. The RDP Migration Utility verifies that each target server is in an active state before it attempts to migrate the server.
server and then executes a script Windows or Linux Run Script that Windows or Linux Run Script copies a single file to the target server * Note: Packages cannot be added, deleted, or modified. Configuration File Images from Image Captures Images Created with Symantec rdeploy Utility IC server provisioning does not have the capability of using images created by Symantec’s rdeploy utility. To use the image data with IC server provisioning 1. The image will need to be deployed to a target server using RDP.
Windows product keys Windows System Disk volume label Windows System Disk integer number Windows computer name Windows administrator password Network configuration during OSBP deployment Linux and ESXi hostname Linux and ESXi install kernel arguments Linux and ESXi root password ESXi network command and settings Special custom attributes for defining path to Media Server productkey Various with pattern ProductKey_Winxxxx-yyyx64 where xxxx is Windows version name and yyy is edition. Refer to Table 4.
SelectBootEnable-HBA1=1 HostAdapterBiosEnable-HBA1=1 NOTE: The HBA0 configuration must be specified. Additional HBA’s are optional. Up to 4 HBAs may be configured. The tags for each HBA should end with HBA0, HBA1, HBA2, and HBA3. 2. Refer to the IC server provisioning online help for additional information about using this custom attribute. Copy and paste the appropriate data from the RDP Fibre Channel HBA configuration file for the values to the right of the equal sign within the custom attribute.
5. 6. 7. 8. In two places, change the Administrator password to an IC server provisioning custom attribute: From RDP unattend file line: zzzz To IC server provisioning line: @AdminPassword:zzzz@ where zzzz is the encrypted Administrator Password. It is assumed that you changed the RDP password from its default value and kept the encryption. Remove or comment out the first logon commands section that installs the RDP aclient agent.
3. 4. 5. Remove or comment out all lines in the %post section that reference Copying files from the oem dir, Installing Adlagent, Install OS updates, Install driver, etc. Change or comment out any customized drive path locations or references to RDP utilities. Refer to Table 6: OS Distribution Folder Mapping for references to the media server OS distribution locations. If a customized binary is referenced that IC server provisioning doesn’t already have, for IC server provisioning 7.2 and 7.2.
The Fibre Channel HBA Configuration files are the exception in that they are not a Configuration File in IC server provisioning. Refer to the above Fibre Channel HBA configuration files section. To locate, copy and convert the hardware configuration or the operating system answer files to the rdpmigration temporary location, from the RDP server and rdpmigration folder run rmu.exe /jobfiles. Scripts With IC server provisioning, the “Run Script” tasks and shell scripts should be stored as a Script.
5. If a customized binary that IC server provisioning doesn’t already have is referenced, for IC server provisioning 7.2 that customized binary will need to be stored on the media server. Within the script file, the path to that customized binary will need to reflect the location on the media server. The OSBP that will contain the modified script will need to include the Set Media Source script that makes the connection to the media server.
VMware vSphere/ESXi 5.1 u1 hpfeatures\esxi51u1\dist media\esxi51u1 VMware vSphere/ESXi 5.1 hpfeatures\esxi51\dist media\esxi51 VMware vSphere/ESXi 5.0 U1 hpfeatures\esxi50u1\dist media\esxi50u1 VMware vSphere/ESXi 5.0 U2 hpfeatures\esxi50u2\dist media\esxi50u2 Red Hat Enterprise Linux 6.3 x64 hpfeatures\rhel63-x64\dist media\rhel63-x64 Red Hat Enterprise Linux 6.4 x64 hpfeatures\rhel64-x64\dist media\rhel54-x64 Red Hat Enterprise Linux 5.
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.
For more information To read more about Insight Control server provisioning, go to www.hp.com/go/insightcontrol/docs HP Insight Management Support Matrix HP Insight Control Server Provisioning Installation Guide HP Insight Control Server Provisioning Administrator Guide HP Insight Control Server Provisioning Build Plans Reference Guide HP Insight Control Server Provisioning online help HP Insight Control Release Notes To read more about Matrix Operating Environment, go to www.hp.
