Ryan Annear's community posts

VIPRE classifying rutview.exe as a threat and quarantining the viewer, ending in the program being removed. I have submitted the false positive, but please also submit one as well to help expedite the request. Thank you.

Threat:     Gen:Variant.Jacard.144055
Category:   Virus.Generic
Severity:   Severe Risk
Action:     Quarantined

Traces Found:
C:\Program Files (x86)\Remote Utilities - Viewer\rutview.exe|(Embedded EXE 4r)

VIPRES false positive URL.
https://www.vipre.com/support/submit-false-positive/

Check for recent KB update pushed via patch Tuesday (KB4284835). Microsoft specifically mentions a "Black screen" fix. I have applied it to several endpoints and have heard no one complaining so far. Not saying it will resolve the issue, but worth a shot as I have found 1803 to be cranky more so with the new Intel integrated GPU drivers, forcing me to fall back to older builds.

After upgrading all of our host computers to Version 6.3.0.6, we are experiencing a major bug with using the full control mode when remoting into the machines. Any PC that I remote into seems to lock the users ability to move their cursor out out of a certain real estate on their screen. My first thought was maybe I locked down their mouse use with the new MSI package, but double checked the options and it revealed that nothing changed from the last version (That worked). The end user can move their mouse in a small area, but then it is locked from moving it any further, and so far the only workaround that seems to work is deselecting the Full Control option. Any help would be much appreciated.

I actually found the problem. I was poking at it enough to where I found the solution. I kept hanging onto the DNS question you posed. I attempted to change the FQDN to the individuals IP address and it worked. So I went back and removed our Domains suffix from the "Direct Connection" and just left the computer name and it worked. I do not know if this is a bug or not, but upon the deployment process the MSI configuration tool, it sets the Direct Connection as the FQDN computer name (computer1.contoso.com). So I guess the few that did work for me, I must of setup manually prior to the mass deployment. It looks like all of the computers I mass deployed the software out too all have the FQDN and I have to manually change it on each one. Can you confirm if this was a option I missed in the configuration tool or if this really is a bug? Thanks.

That is correct, I attempt to double click the host within the viewer and it does nothing, and no options (After righting clicking the host) work as well. I do not think it is a firewall and or anti-virus problem because all computers have the same software and hardware setup. I deployed the same MSI to everyone as well, so there are no variants out there.

Ping returned no dropped packets and a reply immediately. I pinged both ways (Viewer to Host, Viewer to DNS server, and vice versa) without a single problem.

IP/DNS for the connection.

Just recently mass deployed remote utilities to our facility and it has been working great, but for some reason a few hosts will not let me connect. I have to constantly run a repair on them or I will find at random points of the day I can connect to them. Their PC's do not differ from others on site (Regards to Anti-Virus, Firewall Settings, etc). This has me absolutely puzzled. Double clicking the computers in the Viewer gets me nowhere, does not even attempt the remote connection. Anyone else experiencing similar symptoms??