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

Question

Question

Users Scanning Attributes: Why do they get corrupted?

asked on April 22, 2015

I find that removing scanning attributes is one of the most common resolutions for scanner issues. I have had a few clients ask me what happened that caused the attributes to get corrupted and if they should avoid certain behavior. 

 

One example I had today was that a different AD user name was listed next to basic scanning as if she had logged into laserfiche while another user was logged into her computer. Now that she is logged into her computer again it wont start scanning. Clearing scanner attributes fixed it so it seems like using laserfiche under a different AD user name might have caused this? That one seems somewhat logical but it often appears completely random. 

 

Can anyone explain at least to some extent what goes on with scanner attributes? Thanks in advance

0 0

Answer

SELECTED ANSWER
replied on April 27, 2015

I've had this problem occur for me in the past.  In fact one user had this issue with importing to Laserfiche and the issue seem to spread from one user to another.  The common thing is they all share the same scan station.  Upon investigating I found that a user might leave from the station and still be logged into Windows. So, the next user that needed to use Laserfiche would just click on icon and proceed while still under the previous users Windows account. The attributes would then get out of whack. This would go on from one user to the next and the problem spread like a virus.  Well, I knew a virus certainly was not the cause.

 

So here is what I understands happens the user's attributes get stored both in Laserfiche under the user profile and store in the registry of the computer they are using.  When the user logs in Laserfiche compares the two and updates settings in both places.  So, when you have a user logging into Laserfiche on a system where another user is already logged into Windows, the attributes get messed up.

I solved this by activating AD on the Laserfiche user account for all users and training the users to check the Use Windows Authentication while logging into Laserfiche.  This way they had to be logged into Windows in order to log into Laserfiche under their account.

3 0

Replies

replied on April 28, 2015

Rodney is exactly right. The reason why this happens is because scanning attributes take into account not only the user who was logged into Laserfiche, but also the user currently logged into Windows.

 

Normally attributes are read first from the user, then from the Everyone group.  With scanning, however, they go one step further and read from the current AD user as well. They’re configured this way since it’s not uncommon to scan from the same station as the same user.

 

Having all users log into Laserfiche using Windows Authentication would indeed solve this issue.  Otherwise, clearing the scanning attributes is a very common solution in this type of situation. 

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

Sign in to reply to this post.