FYI to all - Mike Sheffey asked me to run this a few weeks back. All went fine (it ran in a couple of mins). Since then we've been playing with it and have noticed better stability and speed. In my opinion, those of you who are actually using LC, this would be a good patch to run.
Please note, make sure to follow the update instructions posted above (push new agent out to handfuls at a time).
We've been running this patch for a few weeks now as well. I didn't run into any problems with the update. During our team meeting the next day my techs had already noticed this being quicker and much more stable.
I'd definitely recommend installing this patch.
I have been using this update for the past two weeks. IMHO it is a HUGE success that has been almost two years coming. KLC looked great in demo, but in practice it just did not work. It was waaaaaaay too slow to be usable, especially the remote control feature (which, as an MSP, is extremely important for it to work quickly.)
Mike asked us to give it a spin and immediately after installing the update on my VSA and pushing out a few of the new 188.8.131.52 - 184.108.40.206 agents, it worked like it was always intended to work.
Because of the problems, I always used the Remote Control (VNC) tab on the Quick Launch popout, but now I use Desktop Access (which is a link to the KLC feature.) Desktop Access allow fitting the remote screen to the size of the active window which is more important now with so many screen sizes available.
What really makes it great is that it works in Chrome without having that pesky noActiveX plug-in downloading every time I want to do a remote session. It is totally seamless.
Additionally, the thumbnails come up quickly, the File Manager works without hiccups and there is even a VPN tab that I haven't dived into yet, but it looks promising.
All in all, I have been very happy with this improvement.
Has anyone tested this updated agent on a mac os x yet? We have only updated the agent on one mac, but the klc procedure is failing on the system any time we run it right now?
We are also seeing a few agents not updating properly. Here are the logs for one of the failed updates to the agent (Note: we havent seen agent updates fail like this and even after restarting the agent service they are still failing, but we havent tried a complete reboot of the system yet)
11:21:11 29-Dec-11 K Agent Update Done Failed ELSE in step 3
11:21:11 29-Dec-11 K Agent Update Done FAILED in ELSE step 3, execute script K Agent Update Done Msg (ID = 134)
11:21:11 29-Dec-11 K Agent Update Done Msg Failed ELSE in step 1
11:21:11 29-Dec-11 K Agent Update Done Msg FAILED in ELSE step 1, execute script Deploy Live Connect (ID = 949)
11:21:11 29-Dec-11 Deploy Live Connect Failed THEN in step 25
11:21:11 29-Dec-11 Deploy Live Connect FAILED in processing THEN step 25, Get Variable, with error File Open Failed, Get content from file C:\Program Files\MSP Folder\Agent\AgentID\klcVersion.txt
11:20:03 29-Dec-11 K Agent Update Success THEN
11:20:03 29-Dec-11 K Agent Update Script K Agent Update Done was successfully scheduled to run in 1 minutes
11:20:03 29-Dec-11 K Agent Update Helper Success THEN
On that Mac agent, please log into it and remove the following folder: /Library/Kaseya/Proc
Once that is done, try to KLC to it again and let us know if it passes and/or you receive the same error at Step 10 that you are receiving now.
There are also npk*.bundle files within the Machintosh HD/Library/Internet Plugins/ directory you could remove as well.
When you have run the upgrade and someone tries to initiate a KLC session to an agent that hasn´t been upgraded will that single agent do an upgrade and later initiate the session that the user has started?
One more question.
"The very first KLC connection after you update the agent will be slightly longer, but those after will be much faster."
Will this be solved if I run the "Deploy Live Connect" procedure?
The new functionality from the Update Agent page does the same thing that the "Deploy Live Connect" procedure does. The nice thing about it now, is that there is visibility as to which agent machines have the latest KLC files on each of the Machines (with agents). So if you update the agent to the latest version (currently 220.127.116.11 - 18.104.22.168), there is no need to run the "Deploy Live Connect" procedure.
If you don't update your agent and attempt to Live Connect, the connection time will be delayed in order to update the agent. Once that is complete, your connection times will improve.
With that said, we recommend that you update your agents from the Update Agent page.
see response below....
YEA - i tested this fix and i see much better performance, in some cases we have the connection time dropping with 50% (customers with good DSL connenctions sometimes connect within 2 seconds. really slow DSL connections too about 10seconds and our now down to approx 7 seconds).
So with the agent version now showing as 22.214.171.124 - 126.96.36.199 on the Update Agent page, what's the best way to filter for agents needing an update?
I'm assuming that you would filter the Agent Ver by NOT 602 and "Contains LiveConnect.exe < 10200022", but I haven't been able to make it work yet...
I've been quite critical of Live Connect on this forum but this latest update after you have connected the first time is much quicker and a big improvement when connecting, however I still feel we are missing two really important key features of the old remote control before we fully switch over to using LC.
1. To be able to reduce colours, whilst I like to see the best possible screen, performance and speed is far more important and on slow connections our helpdesk team reduce the colours on the old VNC to make the screen respond faster so they can complete jobs much quicker.
2. To be able to copy and paste text into the LC remote session, having to type out IP addresses and text slows people down and it going backwards from the old remote control.
I'm sure these two key features are on the list to be added in but can Kaseya confirm if and when they will be released in LC please?