Mike Greene's community posts

Conrad Sallian wrote:

Hello Mike,

A few questions:

1. Could you please provide the exact  release numbers (you can open Help -> About in the Viewer).

2. You only update/change Viewer, not Hosts, correct?

Yes, on viewer I'm running 6.10.10.0  (July 2nd) build.

All hosts are running 6.10.10.0 as I wasn't provided a Dec 20 build for hosts, only viewer.

3. For simplicity of the experiment I recommend that you run portable Viewer from two different folders (i.e. each version resides in a different folder). You can populater both address books with same hosts. So in order to compare how it works in different versions first run rutview.exe from one folder, then run rutview.exe from the other folder.

Again, we cannot reproduce this in our environment (although we will try our best) , and your input will be helpful .

Thanks!

Do you have an updated build for the portable viewer?  The one on the download site is July 2.
Happy to continue testing, though it is quite odd that it started working after reverting back to July 2nd build.

I am contemplating spinning up a Win10 build 1909 VM to work with a clean OS, though I don't know if that will help resolve the issue I and others are having but it's pretty easy for me to do.

I wanted to provide an upd ate to this thread.  This morning I reverted back to the July 2, 2019 build on my viewer.  I se t the keyboard preferences on the two hosts (win2012r2) to UNICODE.

I'm now able to use CTRL and ENTER at the login prompt and also at the desktop.  No other changes to my viewer workstation at all, other than the "windows defender updates".

I haven't tested against any of the other hosts yet (win7, server 2016, etc).

If I use the Dec 20, 2019 build the problem returns.

Just sent you the event log file.  FYI, on my RU installation the program and event logs were at the following locations:

Event log files reside here: ..\AppData\Roaming\Remote Utilities Files\EventLog
Program installation here: C:\Program Files (x86)\Remote Utilities - Viewer

Slight improvement, at the CTL-ALT-DEL login screen the shift and enter work, once the desktop loads the CTRL and ENTER do not work, but the SHIFT key does.  (right and left shift)

Running as "administrator" didn't change anything.

Just the standard Windows Defender for anti-virus and the default windows firewall.

To be clear, I am able to connect to the remote host and all keys work  fine from my Win7pro laptop, attempt to do the same from the Win10Pro machine and the keys are non-op.

This doesn't appear to be a 'host' issue, more likely a recent security update on the Win10 'viewer' system.  

Though rolling back updates to October didn't resolve the problem and the one update installed on 11/12 will not uninstall and I've not looked into if that can be rolled back via some other means.

I just tested my Win7Pro workstation, latest RU (6.10) and connected to a host I had issues with before, this time it worked fine.  

Attempting a connection to the same host on my Win10Pro workstation I have the issue.  Appears to be Win10 specific.

Not specifically the same updates, my issue came up last month and it was very random which hosts were impacted.  Now pretty much all of my hosts are an issue.  

The viewer (my workstation) had updates done this month and a couple from last month.  I've uninstalled all of them (with exception to KB...338 and 204) they won't go away!

I don't always run the latest updates on remote hosts for a variety of reasons, however I do run the updates on my workstation on a fairly regular basis.

I'm also dealing with this issue.  Viewer machine Win 10Pro.  Host machines range from Win7, Server2012, 2016 and Win10Pro.  All running the latest RU.  (6.10).

Changing keyboard input didn't have any effect.  What I did notice though is if I open an RDP or Terminal session to the remote host the Enter/Shift/CTRL keys work fine.  If I use the RU Full control method I have the issue.

I've uninstalled and deleted the "AppData\Roaming\Remote Utilities Files" folder and re-installed RU on both the host and viewer machines.  No change.

Stopping the MS Click to run service had no effect.

May attempt to roll-back some updates but this is very annoying to say the least.

Update:  I guess I should have continued poking around on the host.  I was able to achieve exactly what I was after by going into the host security / authorizations area.

Is there a way to create an address book entry for a host that only allows the remote viewer the "view only" permission and not be able to switch to 'full' once connected?

I haven't dug too deep into this yet, so far I've created a new address book entry for the host and set the default to "view only" but once connected to the host I can switch to "full".  It doesn't appear to be controlled at the viewer end of the config.

Looking at the host config I see where you can enable or disable features, but it seems to be a global setting, not per session or login.

Is there a way to have various permission levels for remote viewers?