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

11
3. 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.
4. 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.
5. If a customized binary is referenced that IC server provisioning doesn’t already have, for IC server provisioning
7.2 and 7.2.1, that customized binary will need to be stored on the media server. Within the answer file, the
path to that customized binary will need to reflect the location on the media server. The OSBP containing the
modified answer file will need to include the Set Media Source script that makes the connection to the media
server.
VMware ESX 5.x kickstart files
To migrate a VMware ESXi kickstart file, edit the RDP VMware ESXi kickstart file for the following:
1. Change the network line.
From RDP kickstart file line: @@networkline@@
To IC server provisioning line: network –bootproto=dhcp
2. Change the root password to an IC server provisioning custom attribute.
From RDP kickstart file line: rootpw--iscrypted password
To IC server provisioning line:
rootpw --iscrypted <@root_password:zzzz@>”
where zzzz is the encrypted password. It is assumed that you changed the RDP password from
its default value, but it may not be encrypted. Remove --iscrypted as appropriate.
3. Comment or remove the lines containing @@.
4. Add the following lines of code:
%post –interpreter=python –ignorefailure=true
import time
stampFile=file(“/finished.stamp”,model=”w”)
stampFile.write(time.asctime())
5. 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.
6. If a customized binary is referenced that IC server provisioning doesn’t already have, for IC server provisioning
7.2 and 7.2.1, that customized binary will need to be stored on the media server. Within the answer file, the
path to that customized binary will need to reflect the location on the media server. The OSBP containing the
modified answer file will need to include the Set Media Source script that makes the connection to the media
server.
Automated Procedure
The RDP Migration Utility will search through the RDP database for jobs that reference toolkit utilities in
%ALTIRIS_EXPRESS_SHARE%\hpfeatures\hw-proliant\bin where %ALTIRIS_EXPRESS_SHARE% is the
RDP eXpress share directory location. If found, then will copy the files referenced by the inputfile= value in the job’s
Run Script. The utility will not search the Integrity hardware jobs.
The utility will also search through the RDP express share %ALTIRIS_EXPRESS_SHARE% for answer files:
 For Windows, files with .xml and unattend keyword in the content
 For Red Hat Linux, files with .cfg extension.
 For VMware ESX, files with .cfg extension and only in the
%ALTIRIS_EXPRESS_SHARE%/hpfeatures/esxi5.x directory.
 For SUSE Linux, files with .xml extension and <profile> keyword in the content.
If answer files are found, the utility will copy the files to the rdpmigration temporary location and modify, if appropriate,
each file with comments and IC server provisioning syntax. The new file will be labeled by its original name appended
with _rmu. As part of the conversion, every line within the post section of a Red Hat Linux kickstart file or script sections
of a SUSE Linux autoyast file will be commented out.
When the migration is completed, the file contents can be copied and pasted into a IC server provisioning Configuration
File, and then using a default hardware OSBP with the prefix name “ProLiant HW” or operating system OSBP with prefix
name “ProLiant OS” can replace the Configuration File step already in that OSBP.