Limiting options with ClientMenuConfiguration

Forums / NoMachine Terminal Server Products / Limiting options with ClientMenuConfiguration

This topic contains 4 replies, has 3 voices, and was last updated by Avatar itguy92075 6 months, 1 week ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #21873
    Avatar
    itguy92075
    Participant

    Hello,

    I’m trying to set up a limited ClientMenuConfiguration, but it doesn’t work quite right.  I want clipboard, keyboard, and display.

    # /etc/NX/nxserver –version

    NoMachine Terminal Server Node Evaluation – Version 6.5.6

    # grep ClientMenuConfiguration /usr/NX/etc/server.cfg

    ClientMenuConfiguration clipboard,display,display-mode,display-settings,keyboard

     

    The Display icon is active, but all its options are greyed out.  Which additional setting do I need?

    Thanks.

    #21901
    Avatar
    Shoti
    Contributor

    Hi itguy92075,

    we can’t reproduce any problem with the “ClientMenuConfiguration” key in our labs. To investigate this issue further, we would need the logs from the client, as you mentioned “clipboard” and “keyboard” we are assuming that you are using the web session.

    Please find the instructions here how to gather web session logs: https://www.nomachine.com/DT10O00163#2.6 You can send them to forum[at]nomachine[dot]com.

    #21928
    Avatar
    itguy92075
    Participant

    Hello,

    I followed the link to the instructions and saw this:

    Step 1 – Point your browser to the webplayer application and run it in debug mode:
    https://server:port/nxwebplayer?logging=start

    This might be the disconnect. I’m not using nxwebplayer — I’m using Firefox. I’ll try nxwebplayer.

    Thanks!

    #21942
    Avatar
    mlyn
    Contributor

    Hello,
    as I see you use TSN, so you have also ETS as main server for this remote node,

    The key ClientMenuConfiguration should be set on main server, not on remote node.

     

    #21962
    Avatar
    itguy92075
    Participant

    That was the trouble.  I changed the configs on the nodes, not the main server.  Thanks!

Viewing 5 posts - 1 through 5 (of 5 total)

This topic was marked as solved, you can't post.