Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 394
  • Last Modified:

Workstation to ESX

I want to move a machine from Vmware Workstation to ESX. Should I just drag and drop?
0
Starquest321
Asked:
Starquest321
  • 4
3 Solutions
 
VishalnarseSystem Wintel Administrator L2Commented:
Hi,

Steps to Move VMware Workstation Virtual Machine to ESXi Server

1) Uninstall VMware tools from guest OS. ( I’m not sure whether workstation and server VMware tools are same, but I think its better to remove now and install later in vSphere Client)

2) Shutdown the virtual machine and remove floppy drives, USB and sound devices. If not removed now, converter will remove them with warning message later.

3) Make sure network connectivity is OK and firewalls are opened between VMware workstation host and ESXi server.  In workstation go to File on menu and select Import or Export.

Convert Physical Computer to Virtual by VMware Stand alone converter

4) Select Virtual Appliance in source type.

5) Browse the virtual machine’s configuration file VMX in next screen as shown below. Since VMX file has the details of Snapshots VMDK files, it will take care of them while converting.

6) It should detect the configurations of virtual machine properly. In next screen you can select and resize the disks which should be exported.

7) Now time to select destination. Select ‘VMware Infrastructure Virtual Machine’ and click next.

8.) Provide the IP address of VMware ESX or ESXi server with root user name and password. The same details provided to connect through vSphere client.

9) It should login without any issues and ask for VM name. Give a name and go to next step.

10) Select the resource pool to export if more than one available. Otherwise select local host and press Next.

11) Choose datastore to move virtual disk. My ESXi server have single datastorage.

12) Next is to select network cards. Network cards can be added during export by selecting number of NICs.

13) Its highly recommended to select both options on next screen. Customize the identity of the virtual machine is very important in production environment due to unique machine ID, host name, licensing and domain networking.

System restore checkpoints are useless after converting since any time we can’t restore to earlier checkpoints, because of the different environment later.

14) After completing the customize steps, check the summary before start. Select the Power on the new VM after creation (Optional) option and click ‘Finish’ to start the procedure.

15) Conversion and export should run smoothly and complete successfully. Warning messages can be seen on progress dialog box.

It failed initially because of space issue on VMware ESXi Server. There was no space on host computer to allow growing ESXi’s VMDK file.

Export succeeded after fixing the space issue. Because of I selected power on option, exported virtual machine is up and running on server after conversion completed.

It is very simple and useful if all are correct. This will be helpful to configure and test Operating Systems on local computer before exporting to live servers.

I have attach the attachment with screenshot.

Workstation-to-ESX.docx
0
 
Starquest321Author Commented:
Let me be clear: This is a VIRTUAL machine running on workstation 10 to ESX. . . No need to do a physical machine converstion.
0
 
VishalnarseSystem Wintel Administrator L2Commented:
Yes, I understood that and I believe that I have provided the Steps to Move VMware Workstation Virtual Machine to ESXi Server.

Please clearly go through the steps and I have additional details provided.
0
2017 Webroot Threat Report

MSPs: Get the facts you need to protect your clients.
The 2017 Webroot Threat Report provides a uniquely insightful global view into the analysis and discoveries made by the Webroot® Threat Intelligence Platform to provide insights on key trends and risks as seen by our users.

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
The recommended method of transferring a Virutal Machine from VMware Workstation to ESXi, us to use "VMware Converter".

Please see my EE Articles

HOW TO: FAQ VMware P2V Troubleshooting

HOW TO:  P2V, V2V for FREE - VMware vCenter Converter Standalone 5.5

You could also attempt, uploading the files, see an example in this article for an ISO file


Part 4: HOW TO: Upload an ISO CD-ROM/DVD-ROM image to a VMware datastore for use with VMware vSphere Hypervisor 5.1 (ESXi 5.1) using the vSphere Client, and checking its MD5 checksum signature is correct.
0
 
VishalnarseSystem Wintel Administrator L2Commented:
You can copy past the file VMware Workstation Virtual Machine to ESX vsphere in inventory the step are below.

Open the vSphere/VMware Infrastructure (VI) Client and log in with appropriate credentials.
If connecting to vCenter Server, click on the desired host.
Click the Configuration tab.
Click Storage.
Right-click on the appropriate datastore and click Browse Datastore.
Navigate to the folder named after the virtual machine, and locate the <virtual machine>.vmx file.
Right-click the .vmx file and click Add to inventory. The Add to Inventory wizard opens.
Continue to follow the wizard to add the virtual machine.

To register a virtual machine from a command line on an ESX host:
Log in as root to the ESX host with an SSH client.
Run the command:

# vmware-cmd -s register <full path to virtual machine>\<virtual machine name>.vmx
To register a virtual machine from a command line on an ESXi host:
Log in as root to the ESXi host with an SSH client. For information on using Tech Support mode, see Using Tech Support Mode in ESXi 4.1 and ESXi 5.x (1017910).
Run the command:

# vim-cmd solo/registervm /vmfs/volumes/datastore_name/VM_directory/VM_name.vmx

Thank you
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now