does anyone have steps by steps guide written for p2v using vmware converter?

[vmwareluverz]

anyone has a guide that already written for p2v process you've done for production.

[azn2kew · Accepted solution]

I have a P2V guide that I've wrote for my client and handed over to them using same methods listed on site which is very precise. Basically follow the standards and you should be fine, just document and do screenshots of each step and put it in a technical form than you're solid with complete P2V guide.

You can follow steps below or read more details on VMware P2V Guide can be download on site.

Converter Best Practices

Found this in the recently posted "Server Migrations with VMware Converter" presentation from VMware TSX and modified it based on my experiences

1. Agent Installation Location

• Locally: Install Converter and agent directly on source machine if converting directly into ESX Server

• Remotely: Connect to source machine over network to install agent

2. Agent Installation

• Use local administrator account

• Avoid domain accounts that have restrictive policies

• Allow reboot for Windows NT 4.0 and 2000 sources

3. Machine Preparation

• Do not deactivate services or harden security

> Workstation service

> Server service

> TCP/IP NetBIOS Helper service

> Volume Shadow Copy service (Windows 2003 or XP)

• Ensure sufficient free disk space (at least 200MB)

• Mirrored or striped volumes across multiple disks should be broken

• Dynamic disks with utility partitions should use cold cloning

• Disable Windows Simple File Sharing (Windows XP only)

• Disable anti-virus software

• Defrag hard disks

• Shutdown any un-needed Windows Services

• Clean-up any temporary files and un-needed data

• Run chkdsk

• Keep users off if possible

• Power off VM if not using hot cloning

• VCB VM exports need editing prior to import

> Edit virtual disk filenames inside .vmx

> Rename filenames for .vmdk files to match those listed in .vmx

> Edit index .vmdk file to change references to span files

4. Network Preparation

• Open TCP/UDP ports 139, 445, and 902 (Converter 3.0.0) or 443 (Converter 3.0.1)

• Open network ports between source and destination

> Alternative is to create a VM visible to source, copy VM files to location visible to destination, and import VM

• Use FQDN to connect to both source and VI3

5. Converter Preparation

• Run on OS greater than or equal to source if source is

> VM and powered off, or

> Symantec Livestate System Image

6. Cloning

• Starter edition limitations and workarounds

> Cannot remote hot clone directly into VI3

- Workaround 1: install Converter on source machine

- Workaround 2: select standalone VM as destination, and then import VM to VI3 using two steps

> Cannot run multiple tasks concurrently

- Workaround: run multiple copies of Converter

> Cannot cold clone

- Workaround: create new VM, use third-party cloning application such as Ghost, and run Converter configure

• Do not resize volume for fastest clone speed (block-level copying)

• Resize volumes if source disks have inefficient utilization (resorts to file-level copying)

• Use cold-cloning disk-based cloning (not volume-based) for non-Windows systems

• Use hot cloning for Windows NT 4.0 systems to avoid NTFS upgrade

• Destination needs to be writeable

7. Configure

• Avoid cloning utility partitions

• Check partition numbers in boot.ini

• Automatic "Install VMware Tools" option is only available for ESX Server VMs

8. Clean-Up Prior to Power On

• Edit VM settings according to desired goal

> Number of vCPUs

> Add/Delete USB devices

> Add/Delete Serial and parallel devices

> Remove Floppy drive if not needed

> SCSI controller type (BusLogic vs. LSI Logic)

• OEM source may require license activation

> SMBIOS.reflectHost = "TRUE" in .vmx may avoid reactivation

> Requires destination host to have same hardware

9. Clean-Up After Power On

• Detect hardware

> VMware Tools installation may hang if hardware not detected

• Allow reboots to occur

> Detect hardware and VMware Tools installation

• Verify HAL and change if necessary

• Remove non-present old hardware

> CMD prompt type set DEVMGR_SHOW_NONPRESENT_DEVICES=1

> Next type DEVMGMT.MSC and select Show Hidden Devices

> Delete any old grayed out non-present hardware

10. Guest Troubleshooting

• Blue screen after powering on

> Start Windows in Safe Mode and uninstall hardware-specific applications or services

> Attach VM to "Helper VM" to remove hardware-specific drivers or to correct the boot.ini

• No keyboard/mouse

> Select Workstation/Server VM instead of ESX Server, then import VM to ESX Server

> Use PS/2 keyboard/mouse on source

• Display problems

> Uninstall PC Anywhere prior to installing VMware Tools

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

Regards,

Stefan Nguyen

iGeek Systems Inc.

VMware, Citrix, Microsoft Consultant

[Troy_Clavell]

.... to add to what Stefan said, this KB is also a good source of information

[continuum]

> Cannot cold clone

Sure starter edition can cold clone - see http://communities.vmware.com/thread/162037?tstart=0

___________________________________

description of vmx-parameters:

VMware-liveCD:

[vmwareluverz]

thanks stefan that is very long details there and vmware-land.com is great resource. can you send me a copy of your p2v guide too

[LuckyOne]

Hi Dear,

I have RedHat Linux 5.x VMWare workstation Image and I want to migrate it on ESXi 4.0 Server.

Is it possible?

When I tried it - getting Warning Can not configure the source image?

When bypassed the warning and covert it - could not power on the image - error - operating system not found?

What could be an issue? Please help

Thanks,