You are viewing limited content. For full access, please sign in.

Question

Question

Device licenses for demos

asked on May 8, 2015

I read in one of the 2012 or 2013 articles about the canned demos that if you use a device license, you don't have to switch named users each time you run a different demo. How does that work exactly?

0 0

Answer

SELECTED ANSWER
replied on May 8, 2015

Please see this page regarding information about named device licensing. This other page has information about how to add a named device.

From the help page:

A Named Device license is tied to a particular computer; any user may log in from that computer, but the license will not be available when accessing the repository from any other computer. Like Directory Named User licenses, Named Devices are not specific to a single repository. For example, if you have a scan station that will be used by multiple scanner operators to scan into two different repositories, you can allocate one Named Device license to that scan station for access to both. Note that Named Device licenses cannot be used with Laserfiche Web Access, WebLink, or Web Administration Console.

1 0

Replies

replied on May 8, 2015 Show version history

Nareg, 

Be aware that in 2014 we greatly expanded the number the number of users in the VAR Kit to avoid VARs feeling they had to use named devices. You may want to confirm this is actually still an issue with these changes. 

1 0
replied on May 8, 2015

Great! Let us know if you find yourself having to do these sort of workarounds in the future - jumping through hoops and having to rely on setups outside of our best practices is exactly why we made these changes, so I want to ensure that's all covered now. 

1 0
replied on May 8, 2015

Thanks Alex and Justin. That clears things up. Justin, I forgot that you guys increased the named user license count for the Var Kit. I see 30 in Admin Console. That should be more than enough.

 

Thanks again!

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.