Hi Chris,

Thanks for your reply. 

It's still a mystery that how many concurrent sessions can a named user create. I was once told by a LF engineer that it can create 8, then I have been told by another engineer that it can create 4 and now I have got 5 from you 

So in your second sentence, are you saying that, suppose if I have 5 un-named users/False type users, and if User1 creates a session to Laserfiche, then only one more connection could be made, using any other non-named user? Is that correct? So that means, it's not like all five un-named users can create up to two concurrent connections at the same time?

Thanks

Hi Uzair,

That is correct. All non named users share the same 2 concurrent connection pool. They don't get 2 user connections each (unfortunately  )

I was always under the impression it was 5. In my testing I certainly confirmed 5. Although it's important to know what counts as a "connection". You can monitor what actions actually use a connection by monitoring this in the 'sessions' node in the admin console.

Hope this helps!

Thanks Miruna,

Help file shows :-

"Each Named User license has up to four simultaneous connections per Laserfiche Server associated with it. This means that a user could have the Laserfiche Client, Administration Console, and Workflow Designer all open at the same time. This is true regardless of whether they are logging in using a Directory Named User license, a Repository Named User license, or a Named Device license."

Thanks Chris for your input.

Really appreciated .

Thanks for clearing the confusion Miruna 

I think this answers my question.

Miruna,

I was able to create up to 13 concurrent connections using a named user with our VAR kit.

For that, I had 13 LF client instances/windows opened, and I logged in to all of them successfully. I then stopped myself to go any further, through I might be able to go further. The device wasn't even a named device and only the user was a named user.

Any ideas why I was able to do that?

Those are all one application from one machine, so they're just cloning the existing connection, not opening a new one.

Got it. Thanks

To clarify a bit - obviously the main goal behind the session limit is to prevent license abuse. The reason it is 4 sessions and not 1 is to help ensure that legitimate use cases aren't impacted by this restriction simply because they are using a variety of Laserfiche products at once. As part of that goal, we've also ensured that products will recognize an existing session by that user on that machine and not force a new one where we are able to - as in the case you are seeing with the desktop Client.

This is also why the Named Device limit is 8 sessions, instead of 4.

Thanks for the details Justin.

To clear another confusion, we have a laserfiche not a named user called 'workflow1'. We have created a connection profile in designer using this user. This connnection profile is configured for 5+ workflows.

So my question is, the limit of 2 concurrent sessions for a not a named user doesn't apply in the above scenario? Is that right? So multiple workflows could run in parallel with the same profile configured?

THanks

Hi Uzair,

To my understanding, Workflow doesn't take up a connection in the same was as having the client open (for example). So the same rules don't apply when actually running workflows with a user configured like you mention.

Cheers!

Hi Chris,

That's what I believe but just want to make sure that what I am thinking is right 

Thanks!

That's what I found related to my last question: 

https://answers.laserfiche.com/questions/63834/Multiple-Workflow-Users-sessions

Seems to make sense?