What is the difference between named users and concurrent users?

[#1]

Our licensing indicates we have total licensing for 64 named users and 36 concurrent users.

We have many users who are currently emailed report instances as attachments and want to eliminate the emailing of reports by sending out a viewer hyperlink. We have many more than 100 users who will be sent a link and want to be sure that users who recieve a link will be able to use it to view reports.

I'm trying to understand how the named & concurrent user licensing limits the number of user who can use viewer hyperlinks and / or login to the system.

[Former Member · Accepted solution]

Thanks Richard and Thanks Tim,

Is there anyway to force sessions to close or timeout if a user has been logged in and "forgot" for some period of time?

My understanding is that cpu licensing will be standard in the future and we are discussing with our rep.

Thanks again...

[BasicTek · Accepted solution]

there are session timeout settings in the web.xml (search for timeout or search the forums for more specific instructions).

I''ve heard that they don't work as well in 3.x and thus the reason for going to CPU license in the future.

Regards,

Tim

[Former Member]

Q: Would the licensing scenario I describe above allow us to include as many active directoy accounts (users) as we want to the active directory group (seagate) and have 64 (#concurrent licenses) of them logged in at any one time?

A: Yes. This is correct. e.g: You can have hundereds of users in your active directory group but only 64 of them can login at one time. Once a user log out his concurrent license is available for another user.

Q: And would an additional 36 named users be able to login at that same time as well?

A: Yes. This is correct. 36 named users and 64 concurrent users can login at the same time.

[BasicTek]

>

> A: Yes. This is correct. e.g: You can have hundereds of users in your active directory group but only 64 of them can login at one time. Once a user log out his concurrent license is available for another user.

Just to point out a few things to watch out for...

When mapping in the AD group(s) make sure that you select concurrent users

If you exceed a named license count, mapping in of the groups will usually fail (group will map in but users will not).

Also if users do not close their browser properly you may have sessions on your CMS that wait(hang around) until they are timed out. This may make it appear that you are not getting 64 users connected at the same time. I've heard rumors that concurrent user license may be phased out for CPU and named user licenses in the future. Talk to your account rep about this.

Regards,

Tim

[Former Member]

Thanks Deepti,

We're moving from seagate 7.5 to boe xi r2.....

Our License totals show 36 named and 64 concurrent....

We're using Active Directory authentication for Single-Sign-On and have an active directory group (seagate) that we add all users we want to allow access to boe....

Looks like we were emailing reports as attachments because we had more users than licenses in 7.5....

In BOE we want to stop emailing attachments and just email hyperlinks to users and I'm unsure how our licensing will limit our ability to do so.

Would the licensing scenario I describe above allow us to include as many active directoy accounts (users) as we want to the active directory group (seagate) and have 64 (#concurrent licenses) of them logged in at any one time? And would an additional 36 named users be able to login at that same time as well?

[Former Member]

Hi Bart,

Difference between named users and concurrent users:

Named user means when you buy BOXI you buy a certain amount of named user licenses and then you give each of these named users a login. It`s a cheaper type of license but you have to know exactly who your users are, and so is pretty useless if your userbase is constantly changing or your exposing Infoview over the web.

Concurrent user licenses are now only available in BOXI Edge - the equiv in BOXI Pro\Premium is a CPU license, which means you can let as many people login as your hardware will support. Concurrent user licenses are useful when you don`t know who your userbase is - you can just give a generic login for people to use. Or give people specific logins and not worry that they might not be using the system and using up a valuable named user license.

-

---

for more information follow the below links:

http://www.forumtopics.com/busobj/viewtopic.php?p=476977

http://www.forumtopics.com/busobj/printview.php?t=125096&start=0&sid=095882f7c0d636e7bca723e5930c21d...

Hope this helps.

Regards,

Deepti Bajpai