Forum Replies Created
Seems using RDP and Windows Server is actually possible to have multiple users with their own desktop.
I suppose the problem is the safety of using RDP, or I’m missing some other problem.
Being another Remote Desktop vendor affiliate I highly doubt will be interested 😉
Thanks, unfortunately I didn’t have the time nor the knowledge to modify the script myself.
Looking inside and understanding what is doing and replicating manually is also beyond my available time and knowledge.
Due the fact is working fine in my case with 50% of the GPU available to the VM, I think this way of working will be suited for many use cases and GPU-P seems to be a technology officially provided from MS, I suggest will be good create on your side a NoMachine version of the script or integrate the feature in NoMachine itself.
The article discusses only about VirtualGL.
Our solution will be based on Vulkan, will work the same way?
Also as written was interested to know about the possibility to share the GPU for CUDA compute.
Btw when will be I allowed to post without waiting moderator to approve?
Just wanted to add the system will be dual boot Windows 10 and Kubuntu 20.04 LTS
My interest lie on the Linux side, due I know virtual desktop it’s not supported on Windows.
Also want to better specify I’m not especially interested into hardware based video encoding (even if will be useful of course) but the possibility to access trough the virtual desktop directly to hardware rendering features trough Vulkan and compute trough CUDA. This not necessarily having a vGPU partitioning (reserved to Nvidia workstation GPUs ad far I know) but just sharing the whole hardware resource among the different virtual desktops.April 30, 2021 at 08:18 in reply to: NoMachine for Azure Windows workstation remote usage #33178
Looking to create my first VM using Windows 10 Pro (needing this due the interactive graphics application I will use) I was requested to flag the fact I hold “an eligible Windows 10 licence with multi-tenant hosting rights”.
Digging seems this is related to have a license including Windows Virtual Desktop service. I own a Microsoft 365 Business Plus license, that need to include WVD (reading in the docs).
If I’m going to use NoMachine as remote desktop application, all of this is still relevant?
Even if I tried to inform myself I still need to grasp most of the virtualization topics so it’s not very clear if in fact NoMachine isn’t using at all a specific remote desktop service.
Discovered about the grub-reboot command, so being Linux my default OS I can switch without problems from Linux to Win and back to Linux.
In the same way as a gaming specialized client such as [removed] but with the client machine connected to a VR headset.
I never tested [removed] since so far I’m satisfied with NoMachine, reading [removed] declare 7ms latency added that for VR needs is too much, since what [removed] is declaring seems to me is all also available in NoMachine (efficient hw video encoding and decoding, UDP slim protocol, etc), I want to understand more about NoMachine before searching for alternatives.
To be honest I’m not sure will be really feasible in term of latency (a VR headset does refresh every 11ms in the most slow case, a optic fiber connection we have in the office will add by himself a 4ms latency, before all the other latency sources), but the potential advantages worth a bit of analysis.
And what about changing PCIe Link State Power Management to Maximum Power Saving?
This is concerning me more than CPU since I have two GPU for a total of about 350W power consumption at load, so I suppose this can be a main source of power savings. Not sure how will behave at Max Power Saving if I try to connect when they are in idle.August 20, 2019 at 10:21 in reply to: Able to connect to Linux but not to Windows (dual boot PC) #23336
I have sent you the logs, btw I just tried disabling Win10 firewall, with the same outcome.
Want also to specify my PC is connected to the home router trough a Powerline, the laptop using a wifi range extender.
Need to be noted I tested shortly the same configuration in the office local LAN (PC connected using cabled LAN, laptop on WiFi) and got the same result.