![]() If it works well on a 2 nd browser, then follow the above referenced steps and remove and re-install the plug-in on the first one. ![]() The simple troubleshooting step here is to switch browsers and see if it works. For Internet Explorer, refer to this KB Article. Kaseya has a guide on how to do this for the first two here. These two browsers make it fairly easy to un-install and re-install plug-ins. While Kaseya supports all the major browsers (latest versions preferred!), our recommendation is to use Chrome or Firefox. The problem could be on your side (Admin), or the remote side (Agent). It takes two to tango as they say, and it is very true when trying to connect remotely to a computer using KLC. This all works really well most of the time, but this blog is about what to do when things don’t seem to be quite working they way you want them to. This will ensure that all your systems are already up to date when you need to remote control them. If you are on one of Kaseya’s hosted servers, you should schedule this to run every Saturday afternoon (> 3pm). If you have your own on-premise KServer (or you are on our K2 server), you should schedule the “Execute Deploy Live Connect” script every Friday between 3am-8am. With the release of 6.2, this is still a best practice. In July I wrote a blog article about how to improve the performance of KLC by pre-installing the KLC modules on a scheduled basis.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |