We’re running IFS 23R2 SU6 on-prem, with Time Clock on managed android tablets around our different sites.When we do CRIM deliveries, or have to take IFS down for other reasons, some Time Clock units bounce back fine. But a bunch of them will fail to authenticate and go back to the authentication screen. Our MDM tool doesn’t allow us to remote on directly to re-authenticate, which leaves us two options:Either get a bunch of people from service desk to do site walks and authenticate the terminals again. Leave them broken overnight and fix them when we get there in the morning (this means that the afternoon and night shift don’t have time clocking, and the morning shift are also frustrated as they get on site long before we do).Are there any solutions out there to this problem? Is this something IFS are aware of as a bug? Or have other users found different ways of addressing this issue?

Time Clocks auth fails after outages

We’re running IFS 23R2 SU6 on-prem, with Time Clock on managed android tablets around our different sites.

When we do CRIM deliveries, or have to take IFS down for other reasons, some Time Clock units bounce back fine. But a bunch of them will fail to authenticate and go back to the authentication screen.

Our MDM tool doesn’t allow us to remote on directly to re-authenticate, which leaves us two options:

Either get a bunch of people from service desk to do site walks and authenticate the terminals again.
Leave them broken overnight and fix them when we get there in the morning (this means that the afternoon and night shift don’t have time clocking, and the morning shift are also frustrated as they get on site long before we do).

Are there any solutions out there to this problem? Is this something IFS are aware of as a bug? Or have other users found different ways of addressing this issue?

Page 1 / 1

Hi Emma! I was curious if you found any solutions to this?

We are not running on-prem but have encountered this issue for both SU, RU and the latest occurrence was during the IFS Planned Maintenance.

I was interested if you found any solution, reported it to IFS or found a decent workaround?

About our set up
We are running Time Clock in kiosk mode in Chrome(on PC) and have solved the auto-login with a .bat-file which handles reboots of the computers, but when the connection is broken for a period of time, the time clock´s gets logged out with the need of us to manually log them all in (17 of them) individually.

We are also interested in a solution to this problem.

@maxels would you like to share the solution with the bat-file since that would also be helpful for us as well?

Following as also interested in time clock config and trouble shooting

@ovjose We have autorun on a .bat-file to start the browser and a direction to the time clock address.

The File starts the browser in Kiosk mode and is run on a touch display without any HID devices connected.

Start "" "C:\Program Files\Google\Chrome\Application\chrome.exe" --kiosk https://yourdomain.ifs.cloud/timclo/main --chrome-kiosk-type=fullscreen

Regarding the issue we have during IFS service window´s and when we are applying release/service-updates, we posted a ticket to IFS Support without high expectation since we found it hard to describe (CS0434410). But the IFS Support team was helpful and have found an issue. The ticket and a potential fix is now planned (not yet confirmed) for release in 25R2

Did you find what you're looking for? If not:

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded