- This topic has 5 replies, 2 voices, and was last updated 5 years, 6 months ago by
.
-
Posts
-
Hi,
Trying to start a session using a script, using NoMachine Enterprise Client latest version.
I’ve created a connection file, saved the password, and check marked “remember this setting in the connection file” when asked to select a desktop session type – in my case kde.
This works while the session is alive, I just use the connection file and I skips all screens and just logins.
But if the session is terminated, I’m presented with a screen to start a new desktop session. After clicking “new desktop” it doesn’t ask me the select to KDE, which is good but still it stops to ask to open a new session, which ruins the automation.
Is there a setting in the connection file to start a new kde session if not available, and use an existing one if available?
When the virtual desktop is not automatically created, do you see other running sessions on the server? They’re listed in the same panel where you can find the “New desktop” button.
No, no other sessions. You get a big new desktop button. When you press it, you do get a KDE session, but I want to also skip that screen.
If you have access to the NoMachine server verify that the ConnectPolicy key enables the ‘autocreate’ mode, in the file server.cfg. You can also check the ‘autocreate’ value in client logs, by looking for the file ‘connection’ in your $HOME/.nx directory.
Thanks, I checked. The server indeed has AutoCreate as 0.
Does this mean there is no way to do this without changing server settings?
Why is this even a server controlled policy… theoretically any NX client could ignore it… Even a ugly click button automation script can bypass this so called “policy”.
It just makes everything more complicated than it has to be. I would move this policy to the client side.
This topic was marked as solved, you can't post.