Since we've seen rapid updates with Live Connect throughout the past few months, we can imagine how managing these Live Connect deployments can be a headache after running a patch update. We figured it would make sense to develop a simple agent procedure that would quickly deploy Live Connect updates across machines. Your technical staff would focus on solving issues the moment they walk in the office rather than dealing with downloading and installing new Live Connect updates often.
You can download the Live Connect deployment agent procedure here created by our own Douglas Sanchez: https://automationexchange.kaseya.com/products/331.
The agent procedure consists of grabbing the available installer from the VSA, checking if Live Connect is actively running on the machine, stopping it, and then proceeding with the install / update. We're looking for feedback on whether this would be useful for your team and how we can improve this further.
Sweet, so this would take care of my question about pushing *that* out... Now how about one for the RC agent :)... If I could do both, then that would be great!
Can you elaborate on the remote control agent? Live Connect also has remote control built in. Let me know if I misunderstood.
Ok... so basically you are saying that if I install Live Connect that I shouldn't need the separate KRC app installed then? I"m talking about the app that gets used when you don't do live connect but instead just do Remote control or private remote control from Quickview.
That's correct. If you only need remote control, it will launch the remote control sub-app by itself. However, if you go to Default Settings under System in the VSA, you will see an option to switch to the previous version of remote control and that itself will require a separate installation. This agent procedure targets the new version. Hope that helps.
Is it supposed to be KaseyaLiveConnect.exe? We have KaseyaLiveConnect.msi
GDRBrian In 9.4, all of our Live Connect installers are in .exe format whereas in 9.3, they were provided in .msi format. It shouldn't make a difference in installing and running.