Closed io-mneese closed 1 month ago
It should be, just skip the VM installation guide and set the config parameters like the IP, user and password to your actual login for the other machine.
That does not work because the installer requires that the variable WAFLAVOR is either docker, podman or libvirt.
Beginning with the following line:
The code already has libvirt
as a possible third option, seems the installer also needs a "manual" option to allow users to specify a remote ip in RDP_IP
Its been a while since I last ran this project on my system and must say that the progress looks really nice.
Its been a while since I last ran this project on my system and must say that the progress looks really nice.
Yeah, courtesy of @KernelGhost, he cleaned up the codebase a lot
This can certainly be achieved, however we would need to implement a new WAFLAVOR named 'remote' (or something to that effect) to allow WinApps to attempt a connection to a user-specified IP address without conducting additional dependency checks, user group membership checks or virtual machine status checks. The automatic pause feature should also be disabled when this 'remote' backend is selected. This isn't implemented yet, but could be with relatively little effort.
@KernelGhost See #204
closing in favour of #204
Oops I missed that. Awesome work!
At $company we can use a pre-existing virtual machine for different apps.
Is it possible to use the installer script without a local Windows installation and instead use the remote rdp server?