Kaseya Community

Kaseya Administrators within Terminal Services

  • We're in the process of migrating some of our help desk staff from their desktop environment to a Terminal Services environment for a cleaner rotating helpdesk, however have found a minor/major glitch.

    Basicaly, as our staff (logged in as Kaseya Administrators) attempt to connect to a KVNC client, it initiates the KVNC Daemon on the machine, and via that creates the connection to the remote desktop. This works, except the KVNC Daemon remains open within that users profile, and as soon as a 2nd Terminal Server staff member attempts to connect to another KVNC session it'll open the initial screen as the KVNC Daemon remains open. If we close the Daemon manually on the 1st screen, upon next connecting from the 2nd screen it'll run the daemon under the 2nd profile and connect fine, however the same then applies for the 1st, 3rd etc etc.

    Has anyone worked out a way around this? or am I doing something wrong?

    - Glenn

    Legacy Forum Name: Kaseya Administrators within Terminal Services,
    Legacy Posted By Username: Connected
  • /Bump

    Anyone seen this or can think of any work arounds? The current setup severely limits Kaseya's capabilities within this environment moving forward.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: Connected
  • My guess would be that VNC is not terminal server 'aware' and will probably never work right in this type of environment.

    In fact having apps not be compatible with TS is one reason we have a client that we will be moving to a virtual desktop infrastructure with VMWare VDI.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: misolutions.com
  • We just use remote control to get to the console session of the terminal server. Then open Task Manager, go to the "Users" tab, right-click the user and "Remote Control". This is unquestionably less convenient from an admin's perspective, but so far I don't really have other options for a terminal environment.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: arobar
  • Our Kaseya administrators all use Kaseya in Terminal Server and we have had many problems such as you described.

    In short: Kaseya assumes that you run your browser on a PC where you have local administor priviledges. This is more or less the only setup they had in mind when they designed Kaseya.

    We had to move to another remote control solution because of this.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: Kalle