![]() Now it does, so when the local X server cannot be found, NoMachine uses its own display service. In earlier versions NoMachine (for Linux) didn't have its own embedded X server. The solution you mention is actually for older versions of the free version on Linux OS. Maybe the NoMachine crew will read this and evaluate how to make it even clearer that the free version of NoMachine is not the same as the Workstation edition. The articles that you linked do point out that the virtual desktop functionality aka Terminal Server is available in specific products. ![]() That is probably what you were using, so not a bug at all. The legacy 3.5 version gave the virtual desktop functionality away for free. Virtual desktops on Linux are in the pay-for editions of the product, like other features. The free version of NoMachine is for access to the physical desktop of the host where you have installed it. It's not that it doesn't work, it's not supported which is something different. The native virtual desktop function in NoMachine linux does not work in the free version Remember that on the connecting device, clients are free, so choose from Enterprise Client for your OS, or if you are connecting from iOS or Android, proceed to their respective stores to. Instructions are here, change any ":0" to ":1" (so you don't screw up the existing physical display), and then in /usr/NX/etc/server.cfg uncomment "DisplayBase" and set to 1. The alternative to the free NoMachine software package in order to access the physical desktop of the remote machine is NoMachine Enterprise Desktop. The solution: NoMachine actually gives the solution, it's to create a second display using xvfb. The Rant: why the heck doesn't it say in the config files or any of those articles I linked to that virtual desktops are only supported in the workstation/enterprise version? I wasted hours trying to figure out what the heck my config issue was before finally stumbling on the info that said it wasn't going to work anyways. Somehow I've ended up in virtual sessions on my setup in the past, which was what gave me the whole idea, but I'm guessing that was a bug. It may actually work with the free version on a headless system, not sure. This is despite this guide, aka the guide I'd found and was following, not making that distinction. The PSA: the native virtual desktop function in NoMachine linux does not work in the free version, see here and here. ![]() I have an HTPC, and want the physical display to auto login to Kodi, with admin functions thru NoMachine on a virtual display. It functions as a single point of visibility, so that IT administrators can conveniently add, remove, monitor and configure user access to NoMachine nodes as well as visualize a Cloud Server's hierarchy.I wish I'd found this info sooner, and am writing this in the hope that someone searching for info down the road will find it and it will save them some time. Whichever product you choose from the Cloud Server portfolio, an intuitive navigation interface makes light work of remote configuration and management of your entire NoMachine infrastructure. Whether it's a small number of users connecting to a shared desktop, an entire university faculty providing a gateway to its myriad of hosted resources or a large organization offering unified high-available access to complex VDI and server infrastructures, your choice of Cloud Server is the single pane of glass for all your NoMachine environments. Access through the gateway is guaranteed even in the event of system failure or downtime, delivering applications and desktops seamlessly and with minimal disruption. Its integrated clustering capabilities allow administrators to create a powerful, resilient and highly-available gateway with built-in load-balancing. For load optimization and resilience, choose Enterprise Cloud Server Cluster. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |