I've been following another good thread on the Kronos-Fans Yahoogroup about Java and thought I'd point it out to any of you that don't spend enough time there. This particular message is written by Chris Flanders and is a worthwhile read. He starts,
"Having been through this same dilemma in a couple of different large, distributed healthcare systems, I can assure you that there is no magic bullet or easy solution to managing Java on the clients for your Kronos users. In fact, even when you have the correct versions installed & working, I would still say that roughly 95%+ of the non-process related problems that individual users experienced were Java-related and resolved by either clearing their Java cache or reinstalling Java. But, despite all that, you can make it a little easier on yourself. Here are some suggestions or thoughts that you mind find helpful (in no particular order)"
Go check it out if you still have Java issues!