Hot answers tagged virtual-machines
Run Disk2Vhd inside the VM. It uses the volume snapshot capabilities of Windows to make a copy of the hard drive and write it to a VHD. From there, you are free to use that VHD on your new VM, or convert as needed. https://technet.microsoft.com/en-us/sysinternals/ee656415.aspx When you first boot up the VM, do not allow it to access the network. Change the ...
It's not a flashy, but you could always run a shared session over VNC - that does allow multiple connections to share the same session and display. x11vnc is a common example which works well in this situation. Keep in mind that VNC doesn't handle encryption so running through a encrypted SSH/VPN tunnel is highly recommended.
VMware allows to create VM images from physical machines - you could try to create an image from a the VM and then move it to another physical server. I've never tried to use it with with virtual machines, so I'm not sure if it will work, but it's worth a try. It works with VMware ESx hyper-visor, but usually it's easy to convert a VM image to another type (...
Here's how I do this: I create VMs with a PowerShell script as part of the script I copy an existing VHDX with a sysprep'ed OS. I then mount the VHDX and create a unattend.xml as well as a \Windows\Setup\Scripts\SetupComplete.cmd file, both are specific to the new VM. After dismounting the VHDX I can start the VM and everything else is automatic.
Your code seems OK (except for sometimes writing port 9901 and sometimes 9001). Your problem is that your VMWare host is NATting all the outbound packets. You need NAT to rewrite the source IP of your VM to correspond to the 192.168.2.* network. To do this for many source IPs (here you have two, your VM and your physical machine), NAT also needs to be able ...
Only top voted, non community-wiki answers of a minimum length are eligible