Christer Johansen's community posts

This was observed with the latest version of Remote Utilities Host, as well as all previous versions. This behavior was observed under Windows 10 as well as under Windows 11.

If explorer.exe crashes and is restarted, or if it's being killed and then re-started, the system tray icon is not re-created as it should have been. This is most likely because your programmers have "forgotten" to check for the message WM_TASKBARCREATED and then to re-create the system tray icon with something like "Shell_NotifyIcon(NIM_ADD, &m_tnd);".

The same is true for "Remote Utilities Server", it does not re-create the system tray icon as it should either.

Please fix this, it's a really easy fix!

Pauline wrote:

Let us know if you have more questions.

That would solve the issue for me, please implement such an option.-

I don't mind the banner, it's just that the current position actually blocks some information in my system tray, it's translucent yes but it still blocks some info in the system tray of my home server. So I have to switch to RDP every time I need to view that info, quite annoying and could be easily solved if you let us move the banner to a different position.

I would prefer it to be centered at the top of my screen. That way it's very visible, but it does not block anything on the status bar. And anything you have up there can be easily moved, that is not always the case for the status bar.

Thanks Pauline, that actually works now! The key to getting this to work seems to have been to delete all .rdp files from %appdata%\Remote Utilities Files\rdp_connections and *then* following your instructions. Thanks! :)

This was brought up more than 3 years ago here: https://www.remoteutilities.com/support/forums/forum1/1379-rdp-desktop-resolution

Since the native RU protocol is sometimes quite slow, I sometimes prefer to use RDP. But alas, this annoying issue hits me every time, resolution is fixed at 1024x768 unless I manually set it to something higher any time I connect over RDP.

Could this please get some attention, as was promised in the post above?

I have this issue as well, seems like it's still not fixed.

@asdffdsa, what was that workaround of yours? Why not post it here instead of saying you have one?

Thanks, Pauline, enabling the "Use legacy capture mode" indeed solved the issue with this specific computer. Seems like it's necessary for some but not all "headless" computers to enable this option then, good to know, thanks!

Christer

I am running a small home set up (less than 10 computers) with my own RU server for security, and this has been worked just fine. Until recently, when all of a sudden I cannot connect to and remote control one specific computer. I have tried just about "everything", including uninstalling the host and deleting all settings to start over a few times, but that makes no difference. I'm running the latest versions of all the RU software (host 7.0.2.0, viewer 7.0.2.0, and RU server 3.0.1.0), and I'm using "Custom Server Security" for all the computers. They are all configured exactly the same way and on the same physical LAN.

For the PC that Remote Utilities no longer can control the viewer will just show the usual message "Connecting to <computername>. Please, wait...

WHen I look at the log on the "host" computer, it looks like connections are established and ended normally, but the whole time the "viewer" window is just stuck with the "Connection to" message.

I can "Log on" to the computer in the "viewer" windows just fine so I see a miniature screen under "Logged on", I just cannot connect to it.

I didn't really think this could be a "missing display problem" as I havea few Intel NUC boxes with no display or display cable connected, and I can control them just fine. But not this relatively new AMD system with RTX 3070 graphics card, as soon as I unplug the HDMI cable I can no longer connect to it with Remote Utilities.

Now the whole purpose of using RU is to connect to such computers that are just left doing their things, with no need for an attached display.

Am I missing something here? RU is supposed to work even with no display connected to the "host", right?

How do I fix this issue so I can connect to the computer without having to have a display connected?

I did order a few of these "dummy HDMI plugs" that tricks the display card into believing that a display is attached, the kind that are usually used for "Mining rigs". But should that really be necessary?