Just want to give you a heads up on a hotfix that is going out today. We've made it possible to schedule the deployment of Live Connect agent-side code so that it can be kept up-to-date without having to actually start Live Connect. The benefit of this is that if you schedule the Live Connect Deployment procedure then you won't be forced to wait for agent-side code to download and update while you're trying to connect to the machine.
You'll see the new procedure once the re-apply schema has been run. This is done automatically every couple of days, or you can force the re-apply schema from the system tab.
I've included a quick video to show where the procedure is located and how you can use it to make Live Connect even faster by not having to wait for agent-side code to update after Live Connection changes.
You have to check the "Reload sample scripts with every update and database maintenance cycle" -option in System > Configure, before you perform the re-apply schema, to get the procedure to appear...
Still looks like it deploys the specific KLC -files when initiating KLC on an agent that have run the new deployment procedure.
This is from the agent procedure log:
22:11:38 27-Apr-11 Start KLC on [MACHINE-ID].[GROUP-ID] - [HIDDEN] [HIDDEN]
Script Summary: Success THEN
22:11:37 27-Apr-11 Start KLC on [MACHINE-ID].[GROUP-ID] - [HIDDEN] [HIDDEN]
22:11:36 27-Apr-11 Start KLC on [MACHINE-ID].[GROUP-ID] - [HIDDEN] [HIDDEN]
Delete 'C:\Program Files\Kaseya\[HIDDEN]\DesktopAccess\server_settings.ini'.
Delete 'C:\Program Files\Kaseya\[HIDDEN]\DesktopAccess\tvnserver.exe'.
22:08:32 27-Apr-11 Deploying Live Connect files on [MACHINE-ID].[GROUP-ID] *System*
22:08:31 27-Apr-11 Deploying Live Connect files on [MACHINE-ID].[GROUP-ID] *System*
22:08:30 27-Apr-11 Deploying Live Connect files on [MACHINE-ID].[GROUP-ID] *System*
22:08:29 27-Apr-11 Deploying Live Connect files on [MACHINE-ID].[GROUP-ID] *System*
22:08:28 27-Apr-11 Deploying Live Connect files on [MACHINE-ID].[GROUP-ID] *System*
22:08:27 27-Apr-11 Deploying Live Connect files on [MACHINE-ID].[GROUP-ID] *System*
22:08:26 27-Apr-11 Deploying Live Connect files on [MACHINE-ID].[GROUP-ID] *System*
22:08:25 27-Apr-11 Deploying Live Connect files on [MACHINE-ID].[GROUP-ID] *System*
22:08:23 27-Apr-11 Deploying Live Connect files on [MACHINE-ID].[GROUP-ID] *System*
22:08:19 27-Apr-11 Deploy Live Connect [HIDDEN]
22:08:14 27-Apr-11 Run Now - Deploy Live Connect [HIDDEN]
Admin [HIDDEN] scheduled procedure Run Now - Deploy Live Connect to run at Apr 27 2011 10:08PM
Live Connect will always check to see if it needs to be updated when it's run. If you take a look at the time-stamp you'll see that it took over 15 seconds to deploy the Live Connect updates after the procedure was run, because updates were needed. When you launched Live Connect, the same process completed in about 2 seconds, because everything is up to date.
Thanks! Seems to be working well so far.
Do I just need to schedule this on all the exiting agents and my templates the once? Or is there various LC updates so it would be better to schedule this to reoccur and if so how frequient?
Set a recurring schedule (I recommend daily) — If you have a schedule to automatically apply hotfixes, then I suggest coordinating the Live Connect Deploy procedure to kick off after hotfixes are applied.
Great, i can see that the improvement is more then noticable.
Still wonder, why these files are not part of the agent install? Or is this because KLC updates are more often than agent updates?
@Patrick: I guess the recurring interval should depend on how many agents one have. Considering the entries from this procedure in the agent procedure log, this update takes about 16 MB. Since we have more than 8000 agents, this would mean we have to deploy 130+ GB over night when updated files are released - which might cause problems.
Indeed, in our case 5200 agents through a not to fast vpn connection can cause some problems if this update script is running.
I'd like to have a more de-central solution. Our 5200 agents are spread around 400 lan networks, so i'd like to run this script to those 400 agents (servers) where then another script is running in the local lan to update the rest of the machines.
Only it seems that this procedure is somehow hidden, i'd like to adapt it to antoher one wich can run local on the lan.
Is there any way to get my hands on this procedure?
Re-apply Schema...will this bog down the network in anyway if I was to run mid-day? Or is this better to run after work hours.
Would be nice to have this updated as part of patch management, then it could use patch source location.
Eddy: That would be a *great* idea. Right now it is too bandwidth intensive to deploy it out to all of our agents so we just do it it on a case by case basis.
We are investigating ways to distribute the load of updating the agent-side code, but right now it can only be updated from the KServer. One Note: If the Live Connect agent-side code is generally up-to-date, then we will only download and install what is necessary. While the cumulative package is approximately 15 MB, we rarely update everything at once. If you run the agent procedure on all machines and get the Live Connect agent-side code up-to-date, maintaining them becomes MUCH easier.
Copyright © 2012 Kaseya International Limited. All rights reserved. Kaseya and the Kaseya k-bug logo are among the trademarks or registered trademarks owned by or licensed to Kaseya International Limited. All other brand and product names are or may be trademarks of, and are used to identify products or services of, their respective owners.