Document Outline

• HP Insight Control Server Migration 6.2
• Table of Contents
• Part I Overview and concepts
  • 1 Server migration introduction
    • Overview
    • Installing and configuring server migration software
      • Installing or upgrading server migration software
      • Licensing server migration
    • Related products
  • 2 Server migration concepts
    • Server migration components
    • Overview of migrating a server
      • Migration checklist
    • HP Insight Control server migration software tabs
• Part II Pre-migration tasks
  • 3 Preparing hardware for migration
    • Verifying hardware and operating system support
    • Verifying application station system requirements
  • 4 Planning the migration
    • Planning a migration strategy
    • Preparing a schedule
    • Considerations for dual or multi-boot systems
    • Migrating Large NTFS Partitions
    • Resizing file systems for migration
      • Resizing Windows file systems
      • Resizing Linux file systems
    • Manually disabling critical or hardware-dependent applications
  • 5 Preparing software for migration
    • Verifying licenses for software to be migrated
    • Migration Security
      • Disabling firewalls
      • Changing the default Insight Control server migration application station service port number
      • Disabling antivirus software
      • Generating static or dynamic certificates
    • Installing ProLiant Support Packs
• Part III Migration
  • 6 Preparing the source server and deploying the Source Agent
    • Verifying Windows source server requirements
      • Preparing a Microsoft Hyper-V source server
    • Verifying Linux source server requirements
    • Uninstalling guest tools
    • Choosing server migration agents
    • Deploying server migration Source Agents
      • Deploying Source Agents
    • Manually running server migration Source Agents on source servers
      • Deploying a Windows server migration Source Agent locally on the source server
        • Deploying a server migration Source Agent on domain controllers
        • Deploying a server migration Source Agent on a Microsoft Small Business Server
      • Deploying the Linux server migration Source Agent locally on the source server
    • Detecting, stopping, or restarting a remotely deployed server migration Source Agent
  • 7 Preparing the destination server and deploying the destination agent
    • Prerequisites
      • Physical destination servers
      • Virtual server hosts
    • Linux destination size requirement
    • Booting the destination server
      • Booting a physical destination server using the server migration Boot CD ISO for X2P migrations
      • Booting a physical destination server automatically using the migration wizard
        • iLO boot prerequisites
      • Manually creating and booting a virtual destination server
        • Prerequisites for manually creating and booting a destination virtual server
          • Prerequisites for booting a virtual server in Microsoft Hyper-V
          • Prerequisites for VMware ESX migration
          • Prerequisites Citrix XenServer migration
        • Manually creating and booting a virtual server destination server for P2V and V2V
      • Automatically creating and booting a virtual destination server
  • 8 Migrating the servers
    • Prerequisites
      • Minimum source server prerequisites for all migrations
        • Uploading drivers
      • Preparing for a Windows server migration
        • Windows source server prerequisites
        • Source physical server prerequisites
        • Source virtual server prerequisites
        • Destination physical server prerequisites
        • Destination virtual server host or virtual server prerequisites
      • Preparing for a Linux server migration
        • Source physical server prerequisites
        • Source virtual server prerequisites
        • Destination physical server prerequisites
        • Destination virtual server host or virtual server prerequisites
      • SAN migrations in Windows
    • Starting the migration wizard
      • Launching server migrations through Systems Insight Manager
      • Launching server migrations through Quick Launch
      • Launching server migrations outside of Systems Insight Manager
  • 9 Post-migration tasks
    • Installing ProLiant Support Packs after migration
    • X2P post-migration tasks (Windows)
    • X2V post-migration tasks (Windows)
    • Editing the Windows Boot.ini file after migration
    • X2P post-migration tasks (Linux)
    • X2V post-migration tasks (Linux)
    • Viewing migration logs
    • Validating the migration
      • Validating Linux migrations
      • Validating Windows migrations
• Part IV Troubleshooting and support
  • 10 Troubleshooting
    • Installation
      • Unable to communicate with the Insight Control server migration service
        • Suggested action
      • Insight Control server migration software for ProLiant cannot be installed on a machine with empty or invalid credentials
        • Suggested action
    • Configuration
      • Ports required for Insight Control are not available
        • Suggested action
    • User interface
      • Server migration wizard hangs
        • Cause
        • Suggested action
    • Source preparation
      • Corrective action is required before this server can be migrated
        • Cause
        • Suggested action
      • Source server identification fails
        • Suggested action
      • Migration agent deployment fails
        • Suggestion action
      • Server migration Source Agent deployment fails remotely from a Windows Server 2003 Application Station
        • Suggested action
      • Remote deployment of Linux Source Agent using non-root credentials fails
        • Suggested action
        • Manual installation of Linux Source Agent using sudo user privileges fails
          • Suggested action
        • Linux server migration Source Agent deployment from a Windows 2003 Application station to a SLES 10 SP2 source server fails
          • Suggested action
      • Incorrect LUN size detected in step 2 of the migration wizard
        • Cause
        • Suggested action
      • Migrating a source server fails with the Microsoft Hyper-V role enabled
        • Suggested action
    • Destination preparation
      • Destination server identification fails
        • Suggested action
      • Application station fails to connect to the destination server
        • Cause
        • Suggested action
      • IP address configuration fails on a manually booted virtual machine in Microsoft Hyper-V for a P2V or a V2V migration
        • Suggested action
      • Kernel panic occurs when booting a virtual machine to the Insight Control server migration Virtual Machine Boot CD ISO
        • Suggested action
      • Mouse does not work on a virtual machine booted with the Insight Control server migration Virtual Machine Boot CD ISO
        • Cause
        • Suggested action
      • Primary array controller does not have logical drives defined
        • Suggested action
      • Primary controller configured in the system does not have drives attached
        • Suggested action
      • Primary controller in system is not supported by this version of Insight Control
        • Suggested action
      • Insight Control server migration Boot CD ISO might stop responding when exiting the Array Configuration Utility
        • Suggested action
      • The destination server displays a blank screen when booting to server migration Boot CD ISO
        • Suggest action
      • Some storage volumes on the destination server are not available for selection
        • Suggested action
      • Static IP address cannot be assigned on the destination server while booting using the Boot CD ISO
        • Cause
        • Suggested action
      • Supported storage controllers display Unknown on the Boot CD ISO
        • Cause
        • Suggested action
      • Auto booting destination server using Insight Control remote management fails
        • Suggested action
      • Insight Control might not detect virtual machines on mapped network drives
        • Cause
        • Suggested action
      • Destination server does not boot when automatic boot option was chosen during X2P migrations
        • Suggested action
      • Destination server fails to boot while loading initrd.img
        • Suggested action
      • Insight Control server migration stops responding during auto-booting of Microsoft Hyper-V virtual machine
        • Suggested action
      • Application station fails to connect to the destination server when the server is auto-booted for a P2P or V2P migration
        • Cause
        • Suggested action
    • Migration process
      • Drivers cannot be installed or injected onto boot disk
        • Suggested action
      • Large volumes fail with server thread error
        • Suggested action
      • Migrating a Linux source server with very large storage fails when the migration is initiated
        • Suggested action
      • Partitions created with third-party partitioning tools do not show proper file system type in the server migration wizard
        • Suggest action
      • Migration fails to terminate if source server is shut down
        • Suggested action
      • NTFS resize error message
        • Cause
        • Suggested action
      • ReiserFS volumes are blocked for Linux migration
        • Cause
        • Suggested action
      • The File System on Source Disk \\.\PhysicalDrive0, Partition 0 Could Not Be Resized During the Migration
        • Cause
        • Suggested action
      • Migration fails during the disk cloning phase
        • Cause
        • Suggested action
      • Failed: Drivers Could Not Be Injected Into Boot Disk in the logs
        • Suggested action
      • Destination VM not powered off on HP integrated Citrix XenServers
        • Suggested action
      • Starting a new migration after a current migration is stopped
        • Suggested action
      • Unrecoverable sector-read errors on the source server hard drive are not supported and fail a Windows P2P or P2V migration
        • Cause
        • Suggested action
      • Source agent fails to launch when source server reboots in migration agent mode
        • Suggested action
      • Error during data copy of Linux migration
        • Cause
        • Suggested action
      • SAN-connected destination server displays blue screen
        • Suggested action
      • Out of memory error occurs on the application station during migration
        • Suggested action
      • Destination server boots with an invalid IP address
        • Cause
        • Suggested action
      • Windows server migration Source Agent or PINT remote deployment fails with Agent is already deployed or not required error
        • Suggested action
      • Windows server migration Source Agent or PINT remote deployment is intermittent and deployment fails with General failure occurred error
        • Suggested action
    • Post-migration
      • Destination server connected to SAN displays a blue screen after boot
        • Suggested action
      • Migration does not start after confirmation. The event log continuously displays Operation Migration waiting for connection to source
        • Suggested action
      • Destination server mouse and keyboard do not work after a Windows migration
        • Suggested action
      • Mouse does not work on the destination server's iLO after a Linux X2P migration
        • Suggested action
      • USB Mouse or Keyboard Drivers Not Loaded After a X2P Windows Migration
        • Cause
        • Suggested action
      • Mouse does not work on the destination ESX virtual machine after a V2V migration
        • Suggested action
      • Drive letters are not the same in the migrated virtual machine guest after migration
        • Suggested action
      • Drives do not appear on the migrated operating system
        • Suggested action
      • Mouse and keyboard do not work after migrating a Microsoft Hyper-V virtual machine to a ProLiant server
        • Suggested action
      • Static IP address cannot be assigned on the destination server after migration
        • Suggested action
      • Virtual machine hosts Integrated Components do not install on the destination virtual machine following migration
        • Suggested action
      • Yellow bang (!) appears on the NIC adapter in Device Manager on the migrated virtual machine
        • Suggested action
      • Network adapter in the destination ESX virtual machine is not initialized after a V2V migration
        • Suggested action
      • While editing the settings of guest VMs created by server migration, an invalid OS ID warning appears
        • Suggested Action
      • Server is unresponsive during PSP installation
        • Suggested action
    • Uninstallation
      • Unable to uninstall an older version of the Insight Server Migration software for ProLiant application
        • Suggested action
  • 11 Support and other resources
    • Contacting HP
      • Information to collect before contacting HP
      • How to contact HP technical support
      • Documentation feedback
    • New and changed information in this edition
    • Related information
      • Documents
      • Websites
      • Related documentation
    • Typographic conventions
• A Applying old SMP standalone licenses
  • Adding standalone Insight server migration licenses
• B Performing migrations in a Microsoft Cluster server environment
  • Premigration consideration steps for clusters
  • Performing the migration
  • Post migration considerations and steps
• Glossary
• Index