HP Insight Control 7.3 Update 1 Release Notes
Suggested action
Perform one of the following actions:
• Configure the controller in RAID mode and erase all logical volumes, then reconfigure the
controller into non-RAID mode and run the migration again.
• Configure the server to use the RAID mode of the controller and run migration.
Verification of Digitally Signed Application can possibly fail on some Microsoft Windows servers
If the Microsoft Windows server does not contain the VeriSign Class 3 Public Primary Certification
Authority - G5 root certificate, the digital signature verification for the application may fail. The
verification failure occurs on servers that do not have the latest ROOT certificate update from
Microsoft. The latest updates may not be available for reasons such as Windows update has been
disabled and server is not connected to the internet.
Suggested action
Perform the instructions from VeriSign available from the VeriSign website.
Improper behavior of Rediscovery in SIM
After selecting the Rediscovery in SIM option in the Step 6 of the wizard, the process results in
failed discovery logs and the IP address will not get discovered.
Suggested action
From the SMP installation directory, (C:\Program Files (x86)\HP\Insight Control
server migration\bin), edit the hpvmm.conf file by adding the following:
VMwareDisconnectTimeout = 90000.
Minor issues
B120i controller is displayed as Intel Lynx storage controller
When migrating to a Gen8 server with Intelligent Provisioning 1.45, the B120i controller is displayed
as Intel Lynx storage controller instead of HP Smart Array B120i.
Suggested action
Ignore the warning message and proceed with the migration.
A Red Hat Enterprise Linux 6.2 32–bit installation on CN1000Q takes approximately 20 minutes
to boot post migration.
Suggested action
This is a known issue and to be fixed in future release.
Windows migrations are not supported for more than 14 partitions on a single disk.
If you select 14 partitions or more on a Windows OS, then the following error is displayed in Step
4 of the V2V migration wizard:
The destination disk <target disk name> has reached its partition limits.
Try migrating one or more Volume Groups selected for this disk to another
disk or go to 'Step 2' of migration wizard to deselect few
partition/Volume Group.
Suggested action
The maximum number of partitions supported for Windows migration is 13 for a single disk. To
resolve this issue, perform one of the following:
• You can migrate one or more Volume Groups selected for this disk to another disk.
• Go to Step 2 of the migration wizard to deselect a few partitions/Volume Groups.
14 Insight Control release notes