Thank you John for taking the time writing this instruction. I hope it will help everyone to resolve the issue while our request to Google is being reviewed. We sent it couple of hours ago and normally such requests are reviewed for 24 hours or so.
What's up with that? I mean, if they know exactly what program it is, why are they blocking it?
This is a good question and we constantly ask ourselves the same. Our website is clean and is being daily monitored by Symantec Norton Secured malware check. The program is signed with a valid VeriSign code signing certificate issued to our company name "Remote Utilities LLC". And we routinely send false positive reports to AV software vendors.
There is only one explanation to this - many antivirus programs are simply poorly made and the business processes behind signature updates aren't thought out well. It's far easier to mark a file as "malicious" than it is to develop a thorough and foolproof review procedures to avoid false detection.
We are aware of this issue with Chrome and do our best to contact Google and resolve the issue. For some reason they keep detecting Agent as malicious even though we already sent them a review request and explained that the program is perfectly legitimate, signed and is being put on our website which itself is monitored for malware by a third-party (Symantec in this case).
We'll keep working on this though. Hopefully it will be fixed soon.
I would be inclined to believe that if this issue occurred with any other remote software. [censored] was used some time ago & Bomgar never exhibits this issue. Even when the keyboard is misbehaving in a RU session. I can disconnect & startup a Bomgar session & the keyboard works as it should.
One doesn't necessarily mean the other :) For example, AV software may treat some programs well and some not so well. Also , different remote control programs may use different libraries, methods, algorithms etc. that again are affected very differently by security policies on a specific PC.
P.S. Sorry, I accidentally edited your own message instead of quoting :)
Dask DT wrote: I am on beta 6.0 and I am attempting to chat with a user who has logged into the Windows 2012 Server using RDP. As of 2008 terminal services was renamed to Remote Desktop Services/Protocol so yes they are a terminal session user.
Dask, the chat only works for console session by design. It's not available for terminal sessions, sorry.
Jeff, we cannot reproduce the issue. Since it's the Server OS on the remote end, it looks very much like something with security policies or even antivirus software activity. In other words, something that gets in the way of Host operation (a policy, a program, a service running).