I didn't see a thread on this yet.
We got our approval and deployed on Monday night. First impressions:
For us, so far, the only issues are AuthAnvil integration and the sporadic remote control issues. This release appears to have been vetted pretty well.
Just an update on this. KRC/Live Connect has some annoying bugs:
I don't know if it's just us or the larger userbase, but I would recommend holding off on the upgrade until these bugs are fixed.
"When you change focus from a KRC window and then switch back with the mouse, it clicks the window behind the active window in the KRC session."
EXTREMELY annoying! Don't know why Kaseya's re-inventing the wheel here. TeamViewer, VNC, GoToMeeting/Assist do remote control SO much better. No fuzzy displays, ability to zoom, so many other things.
Items I've noticed-
Based on the issues outlined above, I'd recommend that others might want to hold off on this upgrade until the issues with Live Connect are resolved.
One issue I had was with updating my SSL Cert as the process has changed in 9.4. If you use the old Java process then it will prevent the Edge Service from starting.
New process listed here:
The issues with KRC continue to mount:
That's all for now. We've updated our KRC ticket (169615) with Kaseya but haven't heard back from support yet.
As I said before, it's probably worth holding off on the update until KRC is at least as good as it was in 9.3.
I reported most of the above new 9.4 type KRC bugs in beta. No responses from Kaseya. We"ve revered to 9.3 style KRC in the meantime, at least this works reasonably reliably.
How do you revert to the 9.3 style KRC?
It's an option somewhere under system.. Sorry, not infront of a pc to look it up exactly.
Thanks for the heads-up. Here it is:
"System>Server Management>Replace KRC with RC in KLC to allow you to enforce all screen sessions getting recorded"
After my first couple experiences with the RC locking up when I try to log out of a system, I went ahead and followed the above instruction (System / Server Management / Default Settings / highligh "Replace KRC with RC" and click the Edit button). That's an improvement.
Now, how do I convince Chrome that the new LiveConnect extension should be permitted to run...? Or is this a 32-bit/64-bit problem? Firefox had no problems whatsoever. IE, of all things, had no problems at all.
And while I'm griping... how does 9.4 NOT have 2016 support? I'm still seeing that annoying "> 2012" in my agent list. Getting 2016 support was a big reason I wanted to upgrade!
(We skipped 9.3, so I imagine that some of my stumbling around the next few days will be on account of missing some of the paradigm shifts most of you enjoyed last year...)
Thanks guys the reverting KRC setting is going to help so much until the new version gets the kinks worked out. Just reverted it and ones I was having trouble with now seem to work fine.
@greyduck - FWIW, our 2016 servers are correctly identified, but they were also correctly identified in 9.3 when they released the patch that fixed that issue. I can confirm both new and existing clients are being correctly identified.
For those concerned about the KRC functionality with the mouse cursor, I've reported this to engineering and it is identified as a bug. Thanks for the reports, guys!