![]() (usually: C:\Program Files (x86)\VMware\VMware Workstation on a Windows 64-bit host)Ģ - Then edit your vixwrapper-product-config.txt file in the same directory, to look (except comments) like the following (add the bold lines): In fact shared VMs cannot be managed from the command line/powershell with Vmware Workstation 15.0 if you do not want to write your own code or apply ugly workarounds.įor anybody, who needs this, I have disvovered, that the following ugly workaround is working on a Windows host:ġ - Copy the vmrun.exe from an WS 12.x installation (renamed to something like vmrunV12.exe) to the installation directory of Vmware Workstation ![]() I understand that VIX and vmrun are not further developed since the functionality of VIX for ESXi and Vcenter was transitioned to powershell (vshere PowerCLI).īut that existing funcionality is reduced and not replaced by something equivalent is frustrating - especially since there is no reason to do this - and PowerCLI does not work for Workstation or Player. The actual vmrun.exe does not honor the -H (host) parameter, therefore no remote connections possible. ![]() ![]() Now vmrun.exe only works on locally installed not shared VMs. Till WS 12.x the vmrun.exe could handle remote connections and shared VMs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |