Currently I am having issues with Kaspersky blocking my input when i connect to a customers computer. It happens using both support and access sessions.
On access sessions i can set it up before hand to allow interaction with Kaspersky but for support sessions that isn't an option as i may get a cold call from a customer with an issue. Also every time screenconnect updates i have to change the setting in kaspersky again.
This problem still exists. I just remoted a client and installed Kaspersky Internet Security 2018. I had to advise the client to input the Kaspersky activation code herself as I could still could not click on anything within the Kaspersky window. I do have the most recent version of ConnectWise installed on both host and client machines.
Hi Danielle,
We installed Kaspersky Endpoint Security and Kaspersky Internet Security and, in both cases, was able to access the Activation dialog and interact with it. For some reason we cannot replicate what you're reporting on our own. When you get the time, please submit a report to our Support team, so we can get to the bottom of this.
https://www.connectwise.com/services/support
Thank you.
It's been 2 years since I posted this issue. Still no real fix aside from a work around that can not be done remotely.
Does anybody have a fix? At this point i just have the customer type in the product key themselves when i do renewals of Kaspersky.
I concur with the above. I've upgraded to the latest version on clients and server. Kaspersky is still making things difficult. It'll prevent any dialog boxes appearing on my screen when I try to specify screenconnect as a trusted application, also when I try to choose to ignore the Elsinore programs. Its a right pain to be honest.
Only 2 hours ago I had to drive to a customers house to reinstall screenconnect as Kaspersky had choosen to block Elsinore app! Im sure Im like many Elsinore Server users : having paid hundreds for remote software and have the majority of customers running Kaspersky...which do you decide to drop!! Or continue with both and have higher stress levels and inconvenience..on a daily basis.
This problem still exists. I just remoted a client and installed Kaspersky Internet Security 2018. I had to advise the client to input the Kaspersky activation code herself as I could still could not click on anything within the Kaspersky window. I do have the most recent version of ConnectWise installed on both host and client machines.
Hey Kristen,
I worked with Kapsersky directly on this problem and they issued a private fix for us. It gets rid of the secondary UAC type prompt that is visible on the client end but not through a remote session. I'm not certain, but maybe the PF can be applied for other Kapserky customers?
Hi Mike,
You're more than welcomed to share the PF on this thread or on our forum.
Thank you!
Hey Kristen,
I worked with Kapsersky directly on this problem and they issued a private fix for us. It gets rid of the secondary UAC type prompt that is visible on the client end but not through a remote session. I'm not certain, but maybe the PF can be applied for other Kapserky customers?
Hello All,
I am reopening this topic as we are still receiving reports of undesired behavior. Over the past few months we've been actively working with the Kaspersky to mitigate the issues and whitelist our application. It seems although these efforts have helped, there are still a number of ongoing problems.
At this time Kaspersky has ceased assistance, but we will continue to work towards improving the current situation.
Since I'm still on 6.2 that's great, thanks! And just for future reference, what is the process for getting future versions white listed as well? Were you able to establish a relationship or some kind of arrangement with Kaspersky such that future versions will be automatically white listed by the time they are released as stable?
Karl,
Yes, we will consistently upload the latest stable release to their Sever.
I just updated to 6.3 and am still not able to control Kaspersky Endpoint Security 10.
Did you update (reinstall) the control client on the workstation after the update? (Updating just the server won't help.)
Since I'm still on 6.2 that's great, thanks! And just for future reference, what is the process for getting future versions white listed as well? Were you able to establish a relationship or some kind of arrangement with Kaspersky such that future versions will be automatically white listed by the time they are released as stable?
Hi All,
The Control clients are now on Kaspersky's Whitelist, if anyone runs into an issue please let me know.