Jump to content

Id manager, bio metric reader, winx64


Recommended Posts

Posted

Like a few other schools we've moved cross to win10 but the x64 version.

 

We have biostore, id manager on site along with a biometric reader.

 

Weve had problems getting finance team fingerprint reader to work as it works perfectly fine with both domain admin and local admin. As soon as a user either domain or local use id manager or look at the properties in biostore id manager, it fails. In id manager it says no scanner found and in control panel, when we click on test scanner, we get an error - not ready (error 113).

 

It used to work perfectly on win 7 x32 so luckily we have a hand full of machines that are on win10 x32. After a quick install of biostore id manager manager and the UareU drivers, created a test local account with only users permissions, id manager says waiting for finger.

 

I was wondering if anyone on here would be kind enough to test biostore id manager and a fingerprint reader on either win7 x64 or win10 x64 versions and tell me what version of biostore id manager you are running.

 

Many Thanks

Posted
Have you tried speaking to Biostore? I have found them really helpful in the past and they helped me re-install their software on a PC for free when Softlink wanted £400 for about 30 minutes work!
Posted

If you have anything which has the name biostore they will help you regardless. To them their name is important and no i don't work for them.

 

They helped us loads of times with mls and cunninghams.

Posted
I see from your post that you are in a school. We have a very similar issue when using the readers with SoftLinks Oliver Library system. We use a monitoring software PCE and we found that if the reader software was initialised before the PCE AUP screen came up it would fail. In the end I had to set the reader drivers to load when oliver was launched, which would be after the PCE AUP came up. Neither Softlink or BioStore could work out why this was happening and said the issue lay with PCE.
Posted
Ive heard from BioStore who say that their software works on x64 machines which i know it does as both id manager and the fingerprint reader work on a x64 OS as either local admin / domain admin however as a local user the fingerprint reader doesn't work in id manager, so ive fired off a support request to the new owners of digitalpersona as they dont host the drivers for fingerprint readers publicly *rolls eyes*, as ive only got version 1.4.0.1 of the fingerprint reader software.
Posted (edited)

I may have a 64bit driver here if this is any good? its from our library heritage support but worked on our 64bit issue machine (Biostore and heritage (cant have both programs open at the same time..)

 

Scrap that... its the same number :(

Edited by newpersn
Posted

@timbo343

 

I've just checked the driver we're using and it's also 1.4.0.1. The 64bit version works on Windows 7 64bit and Windows 10 build 1607 for us without any issues.

 

This is with UareU 4000 series fingerprint readers.

Posted
@timbo343

 

I've just checked the driver we're using and it's also 1.4.0.1. The 64bit version works on Windows 7 64bit and Windows 10 build 1607 for us without any issues.

 

This is with UareU 4000 series fingerprint readers.

 

Thanks. Does it work for a local user of the machine running id manager?

Posted

^ A standard unprivileged domain user on Windows 7 and Windows 10 has no problems using ID manager.

 

(we don't have any unprivileged machine-local accounts, so I've never had reason to test it)

Posted
Ive found ID manager and the finger print reader ONLY work when id manager is run as administrator.

 

Same here. Unsure what its related to though, Both ID manager and Heritage only works by running it as administrator. Unsure why but it works...

Posted
Same here. Unsure what its related to though, Both ID manager and Heritage only works by running it as administrator. Unsure why but it works...

 

When UAC is disabled via GPO, the application doesnt elevate to administrator. Only if i take off the disable UAC policy does the user see secure desktop username and password box to enter administrator credentials. There is no other way round this other than to downgrade this particular PC to x86 of Windows 10 LTSB.

@pete. How on earth have you got it to work. I wonder if its a problem with LTSB2015. Which version of biostore id manager have you got?

 

Here is what i got from Cunninghams..

From past experience that old version of idmanger will not normally work properly with windows 10. Also we have always been under the impression that the biometrics scanners and idmanager will not work on windows 10 at all. There are currently no working drivers provided by the scanner makers for anything above w7.

 

In the past schools have only been able to get around this by downgrading that machine to w7 or the issue has then lead school to expedite the transition from the old biostore products to our iDStore cashless system as our iDStore suite of products is fully compatible with all versions of windows right up to w10.

 

As a warning if you speak to biostore and they offer the only solution as being to upgrade their software to V3 biostore then this will stop the cashless catering system from working completely due to the way the licencing works with the V3 biostore system

 

Im finding the drivers aren't a problem, its ID Manager which is at fault here but no one seems to understand.

Posted

@pete. How on earth have you got it to work. I wonder if its a problem with LTSB2015. Which version of biostore id manager have you got?

 

a) Dunno, just works *shrugs*. I mean, I was expecting it to be a complete trainwreck based on past faffing but it just worked.

b) ID Manager version 3.0.0.6

 

Bit more info:

 

We have:

 

Cashless server:

Biostore Primary Server (source of truth, ID manager talks to this and all secondary servers sync from it.)

Biostore Secondary Server (used by vericool cashless catering id station installs)

 

Library system:

Biostore secondary (used by MLS id station installs).

 

I've just checked file and reg permissions for Biostore on a finance workstation and I haven't done anything permissions-wise.

 

The one thing that you could check is: When the person first runs ID Manager, are they prompted to enter the server connection info or is it already populated? If it's already populated, it might be pulling it from somewhere they don't have permission to amend. On ours the first time a person runs it on any worksation they're asked to enter it (and thereafter it's saved for them).

Posted
a) Dunno, just works *shrugs*. I mean, I was expecting it to be a complete trainwreck based on past faffing but it just worked.

b) ID Manager version 3.0.0.6

 

Bit more info:

 

We have:

 

Cashless server:

Biostore Primary Server (source of truth, ID manager talks to this and all secondary servers sync from it.)

Biostore Secondary Server (used by vericool cashless catering id station installs)

 

Library system:

Biostore secondary (used by MLS id station installs).

 

I've just checked file and reg permissions for Biostore on a finance workstation and I haven't done anything permissions-wise.

 

The one thing that you could check is: When the person first runs ID Manager, are they prompted to enter the server connection info or is it already populated? If it's already populated, it might be pulling it from somewhere they don't have permission to amend. On ours the first time a person runs it on any worksation they're asked to enter it (and thereafter it's saved for them).

 

Ah, yours is the newer version of id manager, i wonder if that has owt to do with it.

 

As for running id manager for the first time, the connection details are blank and its related to the local profile of the user.

 

I think ill test it on 1607 just as a test to see if it works but i highly doubt it as i got the same problem on windows 7 x64. Failing that i think it might be the old version of id manger.

 

The only way we can get a new one is to contact biostore and their support is like talking to a brick wall at the moment.

Posted
Yeah, you need the new version. It's been out for a while, so why Cunninghams haven't offered to upgrade you as part of the yearly maintenance agreement I don't know. I assume the Biostore license is purchased through Cunninghams? I'd speak to them about getting a v3 compatible license from Biostore and then schedule a cut-over time when no-one needs to eat for a couple of hours.
Posted

Hi guys, i have a dp driver file left on the biostore server from one of the support guys for us to install on other machines. Works fine on id manager v2 and v3.

Will upload here tomorrow if i get a chance.

 

Can i attach files??

Posted
Hi guys, i have a dp driver file left on the biostore server from one of the support guys for us to install on other machines. Works fine on id manager v2 and v3.

Will upload here tomorrow if i get a chance.

 

Can i attach files??

 

Which driver version is it?

Posted (edited)
Which driver version is it?

 

Hi Mate,

 

According to my pc it is version 1.4.0.835.

 

Link attached to the driver:

http://lasainteunion.org.uk/docs/mukesh/DPDrivers.zip

 

Mukesh

Edited by mukz
  • Thanks 1
Posted
Hi Mate,

 

According to my pc it is version 1.4.0.835.

 

Link attached to the driver:

http://lasainteunion.org.uk/docs/mukesh/DPDrivers.zip

 

Mukesh

 

Thanks for the driver however its the same as what ive got. The OneTouch installer is 1.4.0.1 and the DPinst64 is 2.1.0.0.

Posted
Thanks for the driver however its the same as what ive got. The OneTouch installer is 1.4.0.1 and the DPinst64 is 2.1.0.0.

 

Ahh when i install it, version shows up as something different. We use it over here and its working correctly.

 

I have a biostore guy ringing me tomorrow morning, i will ask him if there is a newer one.

 

Mukesh

  • 2 weeks later...
Posted
Ahh when i install it, version shows up as something different. We use it over here and its working correctly.

 

I have a biostore guy ringing me tomorrow morning, i will ask him if there is a newer one.

 

Mukesh

 

Did you manage to find out if there was a newer driver?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...