Migrating from VMware Workstation to vsphere/esx5 drip recording

1, the best way to migrate from workstation to ESXi is to use vcenter converter.
Converter can convert a running virtual machine or a down-to-date virtual machine file into an object that can be used by ESXi.

2. If you do not use converter, you can upload the vmdk file of the virtual machine to the ESXi server, then create a new virtual machine, allocate hardware resources, and specify the existing hard disk file VMDK.
encountered the following error message:
An unexpected error was received from the ESX host when powering on the virtual machine vm-4448. Module Devicepoweron failed to turn on power.
Unable to create virtual SCSI device for scsi0:0 "/VMFS/VOLUMES/5024C83D-EF2EDA6D-9DA0-00000000145B/WEB/1.VMDK" Cannot open Disk scsi0:0: Disk type 7 Not supported or invalid. Make sure that the disk is imported.
Analysis Reason:
because 1.vmdk this file is copied directly from workstation, and the VMDK does not have the option to fully allocate space in its initial setup, that is, thin provisioning is selected. So upload it to ESX, and ESX has a recognition error. You need to turn a thinly provisioned hard disk into thick provisioning.
Workaround:
1), the simplest. Copy the uploaded vmdk file directly to another folder such as test, delete the uploaded vmdk file, and then copy the VMDK back in the Test folder.
2), vmkfstools.pl, need to install VCLI.
vmkfstools.pl--server vcenter.xxx.edu.cn--username xx--password xxxx--vihost esxi12.xxx.edu.cn-i/vmfs/volumes/ 5024c83d-ef2eda6d-9da0-00000000145b/doc/source.vmdk/vmfs/volumes/5024c83d-ef2eda6d-9da0-00000000145b/doc/ DEST.VMDK

3, using vmkfstools.pl encountered the following error message:
attempting to clone disk [DataStore] XXX/XXX.VMDK
Unable to clone virtual disk:
Analysis Reason:
I am on the native (VC clinet) connection to vcenter server via VCLI to manage/manipulate the VMDK files on the ESXi host. and VMware's CCLI documentation(VCLI and Lockdown Mode) Chaptermentioned in:

Lockdown mode disables all direct root access to ESXi machines. To make changes-to-ESXi systems Inlockdown mode you must go through a vCenter Server system, that manages the ESXi system. You can use the VSphere Client or VCLI commands this support The  --vihost   option. The following commands cannot run against VCenter Server systems and is therefore not available in lockdown mode:

vicfg-snmp

vifs

vicfg-user

vicfg-cfgbackup

vihostupdate

vmkfstools

vicfg-ipsec

If you have problems running a command in an ESXi host directly (without specifying a vCenter Server target), Check whether lockdown mode is enabled on the that host.
Workaround:

This article from the "Technology Collection" blog, reproduced please contact the author!

Migrating from VMware Workstation to vsphere/esx5 drip recording