As with the VWP and the Citrix Workspace app, you can also access the vLWP session using a dedicated client. In this case, it is the NoMachine client. The client can be downloaded from the official website.
The LWP wiki provides a detailed manual on how to install and configure NoMachine to access the vLWP, please consult this manual to setup NoMachine on your local device.
Note: The LWP wiki does not specify the name/address of the hostname to configure in NoMachine. This depends on to which LWP you want to connect, so to the general vLWP or to a remote, but locally installed LWP. In this example, we assume that you want to connect to the vLWP. In this case the name of the remote host has to be specified as vlwp.rug.nl.
After you added a new host, you can connect to it by clicking on the respective button. After you specified your UG credentials, the remote session should start in the NoMachine app.
The virtual setting in the NoMachine app is very similar to the vLWP session in the browser, but it comes with some additional functions. One important additional feature is the ability to access data on your local system directly.
to access your data locally, first open the NoMachine settings (accessibly via hovering on the top-right of your virtual session). Here, you will find now a new “Devices” option that is not present when connecting via a web browser.
If you select it, it will present you with the option to add different devices to your virtual environment. To make local data accessible, use the “Connect a disk” option.
This will present you with available disks that you can make available in your virtual environment. What you see here depends on the available drives in your disk. In the provided example, only one drive (C:) is available and will be selected.
The selected drive will be made available by default in your user's Desktop which is located at /home/<p_or_s_number>/Desktop
. You can specify a name and also adjust settings on who should be able to see your drive. After making these selection, confirm via “Connect”.
Your data is now available under the assigned name at its default location in the virtual environment. You can now transfer data between your local and virtual environment, but also open local data with the tools available in the virtual LWP directly.