6 Preparing the source server and deploying the Source
Agent
Verifying Windows source server requirements
The physical or virtual Windows source server requires the following:
• Local system administrative credentials.
• A supported Windows operating system. For a list of operating systems, see HP Insight
Management Support Matrix at http://www.hp.com/go/insightmanagement/docs.
• Available disk space of at least 180 MB.
• The availability of ports 51125 and 51126.
• Screen resolution of at least 800 x 600.
• All detachable media removed.
• If the source server is an application station, disable the HP Insight Control server migration
Application Service and the HP Insight Control server migration Web Service.
Preparing a Microsoft Hyper-V source server
If you are planning to migrate a source server that has the Microsoft Hyper-V role enabled, perform
one of the following on the source server:
• Turn off the hypervisor by using bcdedit /set hypervisorlaunchtype off at a
command line.
After the migration, you can re-enable the hypervisor at a command line by using bcdedit
/set hypervisorlaunchtype auto.
• Remove the Microsoft Hyper-V role from the source server by using the server configuration
tools.
Verifying Linux source server requirements
The physical Linux source server requires the following:
• User account credentials with administrative rights.
• SELinux running in passive mode.
• A supported Linux operating system. For a list of operating systems, see HP Insight Management
Support Matrix at http://www.hp.com/go/insightmanagement/docs.
• Available disk space of at least 10 MB on /boot and 150 MB under the directory where the
Linux server migration Source Agent must be installed.
NOTE: When Linux Source Agent is launched remotely from the CMS, the default location
on the source server for agent installation is /root.
`
• The availability of ports 51125 and 51126.
• Verify that you have removed all unused boot entries from /boot/grub/menu.lst and the
corresponding initrd from /boot.
• Disable any scripts that might clean up the migration agent files on reboot or shutdown. For
instance, if the agent has been deployed manually to /root, make sure that no scripts will
clean up /root on restart or shutdown.
24 Preparing the source server and deploying the Source Agent