P2V Migration Checklist

Some showstoppers which might prevent candidate selection:

Applications with low latency
Very large workloads and large data sets
Non Standard hardware requirements, modems, fax cards, dongles etc
Pre Migration Checks:
Use Capacity tools to qualify a physical server as a P2V candidate, preferably Capacity Planner
Hostname
OS Type
Server Model
# of CPU sockets and Cores
Physical memory installed
Disk Capacity requirements, any LUNS from FC or SCSI or NFS mount points (CIFS)
CPU, Memory and Disk usage (Capacity tools can give an insight)
Decide on vCPUs, Virtual Memory and Disk space to be allocated
Its always good to have a local Administrator account on the physical box prior to P2V, else login atleast
once using your domain credentials so that its stored in the local SAM
Record the IP configuration, possibly a screen dump of ipconfig
iLO information
Check for disk defragmentation
Check whether the applications are hardcoded to any IP/Mac addresses
RDP access
Information about all the applications and check which services are required to be stopped during migration
Possibly a runbook, which provides an update on the milestone, P2V started, in progress, successful or
failed etc
On board resources from OS and Application teams, their contact information
Ensure there are no Hardware dongles, take note of compatibility, else the effort is wasted
Ensure the firewall rules are opened for the destination network, if applicable
Ensure your ESX/ESXi hosts management port group is connected to atleast 1GB port

Post Migration Checklist:
Ensure to power off the physical server before powering on the VM, else ensure the Network Adapter is
disabled on the VM
Install VMware tools and ensure the Hardware Version is compliant with the ESX/ESXi version
Removed unwanted serial ports and uninstall all the Hardware Services, HP Insight Manager etc
Ensure there are no yellow exclamation marks in the Device Manager
Check and Adjust the Hardware Abstraction Layer, if required
Once the server is powered on, enable the NIC and assign the IP address
Start up all the disabled Application services if any, also check all the Automatic Services are started
Ensure the Physical Server is no longer pingable in the network, else you may run into Duplicate entries in
AD
Get your OS teams (Check Windows Events log) and Application team for stress testing
Test Network and Disk latency
Most importantly User Experience
Converter - Ports Used
Overview of ports:
139, 443, 445, 902

Details of ports and direction:
Converter --> Physical 445 + 139
Converter --> VirtualCenter 443 (If Converter on same server as VirtualCenter N/A)
Converter --> ESX 443
Physical --> VirtualCenter 443
Physical --> ESX 443 (902 for converter 3.0.1)