Forum Discussion
MichaelP
15 years agoContributor
Hi Alex
Actually, it does work!
I confused 'remote' to mean the .vmx could not reside on a remote computer but this is wrong. It means that the VMWorkstation cannot be on a remote computer and must be on the local computer with the vestris dll.
My Virtual Machines are on a remote diskstation that does not have VMWare Workstation or the ESX server. The vestris dll and VMWare Workstation are on my local computer. I can now open a remote vm from my local computer using the following code. I had to refer to the remote vmx using drive mapping otherwise it wouldn't work.
VirtualHost ()
vmHost, vmMachine;
Actually, it does work!
I confused 'remote' to mean the .vmx could not reside on a remote computer but this is wrong. It means that the VMWorkstation cannot be on a remote computer and must be on the local computer with the vestris dll.
My Virtual Machines are on a remote diskstation that does not have VMWare Workstation or the ESX server. The vestris dll and VMWare Workstation are on my local computer. I can now open a remote vm from my local computer using the following code. I had to refer to the remote vmx using drive mapping otherwise it wouldn't work.
function VirtualHost ()
VirtualHost ()
{
var vmHost, vmMachine;
vmHost, vmMachine;
vmHost = dotNET.Vestris_VMWareLib.VMWareVirtualHost.zctor()
vmHost.ConnectToVMWareWorkstation()
vmMachine = vmHost.Open("U:\\Testing\\Windows 7 Ultimate x64 Office 2010 Pro Plus x64\\Clone of Win7Ultx64Office2010ProPlusx64 (2).vmx")
vmMachine.PowerOn(5000)
vmMachine.LoginInGuest("wombat", "neuxpower")
vmMachine.PowerOff
Regards,
Michael