![]() ![]() Someone finally listened and we boxed them up and sent them all back. I was willing to lose my job fighting to keep from rolling them out across the board. The clocks kept falling off the network, the polling software would crash. Not sure if you can just get the Time and Labour module or not from them.Įdit: We tried the Handpunch clocks, again through ADP and it was an absolute terrible experience. Our clocks feed into the ADP time and labour side of things, which can then be fed into the payroll system. Not sure if it was static or what that caused it. We did have one clock that dumped it's entire config and fried the biometric pod recently. We've had them rolled out for about 6 months (15 clocks in total). My one complaint is they require a static IP address (well you can use DHCP but the lease must not expire). We're currently using them with a badge number and a biometric pod (fingerprint). They support multiple authentication methods. We have Kronos 4500s (well we pay ADP for the service, but they're Kronos made clocks) at our locations. The handpunch machines seem pretty good, but the software is all kinds of broken. We disabled the shared account and users connect using their domain credentials, we were told that was an unsupported configuration and again when we wanted to set up sensible table permissions we were told "just lock it down until it doesn't work, then relax it a bit". ![]() The SQL security is horrible, using the default configuration there is a single hard coded password used by all clients to access the SQL server and it has full access to the entire database (when I pointed out to our reseller that this was a bad practice and told them how I had found the password, they basically blamed MS saying it shouldn't be possible for users to obtain the password and said that is wasn't a problem because decent hard working people will just fill in their timesheets manually rather than trying to compromise the DB, conveniently ignoring the possibility that anyone might want access to the DB because it contains a bunch of confidential info). It's foxpro based (even the SQL edition), requires that users have write access to the server it runs from (the standard procedure is apparently to grant everyone full access to the entire program directory so that Fred the part time intern can overwrite an executable file regularly used by Jane the head of accounting, great idea guys!), when I asked our reseller for assistance setting up sensible permissions we were told "just restrict access to more and more stuff until it breaks, then undo the last bit". ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |