Any CPU or memory intensive operations should be run on the CLASSE ComputeFarm or on individual workstations - not on lnx201.

LNX201 is available through NoMachine as a general-use remote login node. Please submit a ServiceRequest for help selecting or setting up NoMachine for your workstation or desktop. Pausing Remote Access, switching between interactive and view-only, and Disconnecting Remote UsersĪvailable NoMachine servers and options for new installations.ĬLASSE supports four versions of NoMachine.Change connection settings (display, keyboard, etc.).Available NoMachine servers and options for new installations.Such a gimmick wouldn't create any problems for my workflow, but I don't know of a way to accomplish it.

I'm thinking the a good approach would be something running under OS X that watches for the key being depressed for several seconds, and forcibly 'unsticks' it. Is there a way I can avoid this situation without relying on changing my habits, which hasn't yet worked out for me after a year of occasionally getting burned by this? :) Therefore, when I return to the TightVNC session a minute, hour, or month later and begin typing, the results are often surprising and sometimes bad, because OS X still thinks the key is depressed. The combination works great for my purposes, with one exception: when TightVNC has focus and I hit on the Windows box to switch focus to another application, the OS X understandably sees the key go down, but never come back up.īecause the Windows key maps to the OS X key, the OS X box is left thinking I never released the key. I'm using TightVNC on a Windows 8 圆4 box to access a Mac OS X El Capitan box through standard built-in OS X Screen Sharing.

Tl dr: I'd like to avoid OS X thinking the key is being held down when I away from a Windows TightVNC session, or at least get the key to auto-release after a period of time.

Nomachine mac command key