New session for any user

[helfgott]

Hi everyone.

We are setting different scenarios with NX and we need to setup the product in a way that allows for each connecting user to create a new session.

It doesn’t matter if the same user is connected to the same node and has already a session. We need that if the same user connects it creates a new session (without killing the existing ones).

Is something like this possible? That would mean if user XXX connects to node ABC four times, then four sessions would exist.

 

[Tor]

Hi.
Could you describe those scenarios with more details please? By having more information we could better understand your needs and evaluate if available NoMachine server configurations could help, or plan features offering new possibilities.

[helfgott]

Hi @Tor, thanks for answering.

We have a TS with 9 nodes, let’s say:

• TS_NM_SERVER
• Node_1
• Node_2
• ………_9

And we have some generic users:

• GenericUser1, GenericUser2, GenericUser3

With the free !M version we established our sessions through python and a .nxs template dynamically in 500 servers (each server was a node), at the end of the script we call:

• /usr/NX/bin/nxplayer –session custom_template.nx

Because we had 500 nodes each generic user would connect to each node, there was no chance to have two “GenericUser1” connected in the same node. So we had 500 GenericUser1 sessions at the same time, one in each node.

With the new paid infrastructure (TS) we only have available 9 nodes, so GenericUser1 (i.e) will be connecting to one of our 9 nodes, the issue is we need 500 sessions with the same generic user. That means GenericUser1 is going to be connected several times against each node, and each time it must have a new session, also the session must be dynamically created, we can’t allow users to click on “new_session” through the NX GUI.

I’ve looked for a flag kind of:

• /usr/NX/bin/nxplayer –session custom_template.nx –new_session

but that doesn’t seem to exist.

Please let me know if I’m clear with the example.

Regards

H.

[Tor]

Please let me know if I’m clear with the example.

Yes, thanks. Just two more questions:

1. Did you evaluate using guest users? They would allow to automatically create a new user for each client connections, environment would not be shared among them (different home directories) and your script would be easier.

2. Do users need to suspend and restore sessions, or when a user disconnects the session should rather be terminated?

[sil04]

Did you have the opportunity to evaluate guest sessions (automatic generation of guest sessions) as suggested by Tor?

We would like to know if using guests is suitable for your requirements and if not, why.

Another possibility would be to configure the server for always creating a new session. This applies only if the session must be terminated and there’s no need to reconnect it. Please confirm if the session should be terminated when it’s closed or suspend/reconnect abilities are necessary.

We are also evaluating pro and cons of adding a further option to the ‘nxplayer –session’ command to allow to specify to run ‘this’ session on ‘this’ node. This option should be used in conjunction with a further option which forces the creation of a new session. In most cases however, it should be possible to reach the same result by means of tuning the configuration.

Please let us know if any of the suggestions above fit your scenario.

[helfgott]

1. Did you evaluate using guest users? They would allow to automatically create a new user for each client connections, environment would not be shared among them (different home directories) and your script would be easier.

Yes, guest sessions aren’t an option. Here’s the detail:

In our current scenario with free !m we have this:

• Workplace 1 – ScannerUser1,ScannerUser2,ScannerUser3,ScannerUser4,ScannerUser5
• Workplace 2 – ScannerUser1,ScannerUser2,ScannerUser3,ScannerUser4,ScannerUser5
• Workplace 3 – ScannerUser1,ScannerUser2,ScannerUser3,ScannerUser4,ScannerUser5
• … and so on…
• Workplace 599 – ScannerUser1,ScannerUser2,ScannerUser3,ScannerUser4,ScannerUser5

Because each Workplace it’s a !m node there’s no problem. We can’t change those users, several scripting processes run on them and we must identify them in that way. Our current problem with the paid version is only having 9 nodes where a huge amount of ScannerUser1 (it would be 599 ScannerUser1 in 9 nodes, i.e) will collide in the same node, that’s why we need to setup !m to create always a new session (in an interactive way).

2. Do users need to suspend and restore sessions, or when a user disconnects the session should rather be terminated?

No, when a user is disconnected the session can be terminated.

@Sil04 Another possibility would be to configure the server for always creating a new session. This applies only if the session must be terminated and there’s no need to reconnect it.

Yeah, that’s not a problem, the thing is it must be interactive, we already setup the server to create always a new session but you must click on “create new session” and we can’t afford that.

Further detail

As I’ve mentioned before we have a python script to do the login process (which do many things) imagine this scenario:

1. The user turn on the machine
2. A python window (PyQt4) appears and ask for User//Password
3. The user provide user//password
4. The script does its magic (which involves creating the nxs template)
5. The script launch the nxplayer + custom template
6. The user only sees a new window (full-screen) with it’s session

We have setup the server to always create new sessions, but we have a problem:

1. The user turn on the machine
2. A python window (PyQt4) appears and ask for User//Password
3. The user provide user//password
4. The script does its magic (which involves creating the nxs template)
5. The script launch the nxplayer + custom template
6. The user sees a !m window and must click in “create new session” <– this must be interactive
7. The user only sees a new window (full-screen) with it’s session

We can’t allow it. That’s why I’m looking for a way to create the session directly without asking to the user or presenting any dialog from !m.

Sorry for not answering quickly I was sick last week.

Regards,

Helfgott.

[sil04]

Thanks for the detailed description.

We opened a new Feature Request which should address your needs:

https://www.nomachine.com/FR10P03730
Extending the ‘nxplayer –session’ command to always create a new session

We are also planning to allow administrators to configure the server for always starting a new session at every connection of a given user.

[helfgott]

Wow, that’s amazing, I’ll be looking forward to this!!!

Thank you!!

Helfgott.

[Author]

Posts