Kaseya Community

KC sessions die if you lock your console

  • If your machine locks - e.g. press Windows+L, security timeout, etc. All open KRC sessions are closed.

    This is absolutely horrible and is killing us. Surely this cannot be by design?

  • Craig, I'm not able to reproduce this issue on my end. Would you be able to provide some details on your exact VSA patch level, configuration, and reproduction steps?

  • We've had a a ticket open about this 3 months ago and were given a workaround option....

    In folder "Program Files(x86)\Kaseya Remote Control" you have a 'Kaseya Remote Control.config' file. You can disable DirectX being used with KRC on the machine having the issue. I can copy the contents here, in between two lines of =======, so you can do a copy/paste:

    ========================================

    {

       "Kaseya":

       {

           "Application":

           {

            "EnableDirectX": false

           },

           "Library":

           {

               "Diagnostics":

               {

                   "EnabledNamespaces":

                   [

                       "Kaseya.Library.IO.Channels"

                   ]

               }

           }

       }

    }

    =======================================

    We were warned this might impact performance. At the time of replacing the config file to disable DirectX I didn't really see much difference. It could be the new 9.4 version is now default set up like this, explaining in part why KRC is slower.