Question

Active Directory Group and Device Licenses

Administration Licensing Directory Server

Updated April 14, 2016

asked on April 14, 2016

Hello All,

I have a client reaching out to me to attempt the following and my team is not sure if we are understanding fully.

This is what the client would like to do:

In Active Directory
Create a group in AD like Device-Users
Assign AD users to the Device-Users group
I DO NOT assign these same users to the LF FULL group (user logs into device using generic AD login)

In LFDS
Add new device to LFDS using hardware footprint
How am I pulling in the new users so that LFDS knows who they are and that they have rights to LF?

I am trying to replicate the setup where they login generically to workstation (which has the device license) then individually to Laserfiche without having to assign them to a group that gives them a full license.

Thank you for the help!

0 0

Answer

APPROVED ANSWER

replied on April 14, 2016

Unless I am misunderstanding that is how a device license works. I don't believe that you could have them login via the Windows Authentication checkbox with the client though.

Basically you would add that Device User group to the specific repository you want them to access. Trust the group and give the appropriate folder security/rights. Then make sure the device is licensed in the LFDS. Since they want to log into the workstation generically they are going to have to uncheck the Windows Authentication Box at the client page and probably put in the domain\username and password to login. This would get them into Laserfiche with their own Windows account while being logged into the workstation as something else. Probably need to test it quick but it should work if I am reading your explaination right.

1 0

Replies

replied on April 14, 2016

As of now, My client believes this to be the answer. Thanks!

0 0

You are not allowed to follow up in this post.

Question

Question

Active Directory Group and Device Licenses

Answer

Replies

Sign in to reply to this post.