Before 9.4 we were using 9.3 KRC. Now with 9.4 we are using KLC Remote Control. We had several servers with fast connections but the latency would be 100-360 ms. Sometimes even much higher.
Now with 9.4 we are seeing 10-25 ms on average while connected. This is a huge improvement.
The latency was much higher due to an issue with our netcode not disabling Nagle's algorithm properly. The algorithm would introduce 200 ms incremental latencies such as what you saw. Glad it worked for you!
Is anyone experiencing policies taking longer to deploy? We have the automatic policy deployment interval set to 5 minutes. However, we are seeing that for new machines the policies might take several hours to deploy.
We are just experiencing this issue since we upgraded to 9.4, we have open a ticket with support but I was curious to see if anyone else has experience this problem.
We are on 188.8.131.52 with agents at 184.108.40.206 and having nightmares with not being able to connect with KRC, just dropping out straight away. Some agents work but I wish we had not jumped to 9.4 so soon. Will wait for a longer time next release there are still too many bugs. Support told us to upgrade from 220.127.116.11 to 18.104.22.168 to fix the remote control issues but our service desk are limping at the moment due to this ongoing issue.
So I finally swapped over from KRC to RC after applying the latest patch and it's been good so far, before it was unusable for us. Our staff is very vocal when their tools aren't working so it would seem whatever the issues were before with RC are at least better.
We've been discovering some issues with the new (LCRC?) - Too many acronyms lol. I have a ticket open for one machine that just refuses to work on even after uninstall / reinstall and a force agent update. But since updating to .15 I have noticed more connections issues with the new LCRC. If I can pinpoint machines I will open a ticket for those as well. It will either sit at connecting or somtimes the RC will just crash all together.
emartens Sometimes we have found machines without the endpoint service running. Sometimes it will require manual re-provisioning. If you have a ticket number, we can take a look at it.
This is what I am seeing for my live connect issues www.screencast.com/.../WhKx5p8fw - I have not opened a ticket yet for that, but I do have a ticket number for a machine that we cannot remote into with the new remote control, but rdp and krc all work just fine. The ticket number is 175098