PeterSAt the moment all connections to the remote machines go via your K Server, and associated network connection. So if your K Server is very busy or the network connection it is using has limited bandwidth available this will impact all remote control sessions.
4. Deploy agent (slower than video streaming because you need to wait for the scripts to run (audit etc)).
People (clients) with drama happening don't wait for a few minutes very well.
Thus, after all that , is my question: Is there a way to make the initial connection of Kaseya quicker?
Benjamin.Lavalley@kaseya.comYou can make a 'remote only' agent that is tied to a template that ONLY installs the remote control components and avoids the lengthy audit altogether.
Can you describe in more detail how to do this? I know I could have an agent template that has no audit or patch scans scheduled and use that to deploy a new agent. But it seems to me Kaseya always forces a baseline audit on a newly deployed agent that runs for minutes after the agent software is installed. And how do you create a template that preloads Remote Cntl components, like K-VNC? I thought the only way to do that was to go to Remote Cntl->Preinstall RC (after the agent has been installed)...