But what's the easiest way to get the new ID? I know I can hover over the icon and take a screenshot, but it seems a bit cumbersome.
If you disabled settings in the tray you can still call the settings window from Windows start menu or search. Just start typing "Settings for host" in the windows search bar. Then click on the item and Host configuration window will open where you can copy the ID.
Please, note that the previous issue that we "fixed" in version 220.127.116.11 wasn't actually a Remote Utilities own bug. It was a bug in Microsoft update which we "fixed" on our side (in fact adapted some code to avoid the bug).
Yet, we will see if there are reports and if we can reproduce the problem. Meanwhile, I would ask if you can send us your system event logs to firstname.lastname@example.org . This may help us figure out if there is a problem and where it lies.
Host works as a system service, i.e. globally on the operating system level. This means that you cannot create separate host installations for each and every terminal user running on the server.
Unlike Host the Agent works as a user-specific application and therefore multiple Agents can run each one in its own terminal session.
Please, note that when you use Host and want to switch between terminal sessions using the toolbar, the sessions must be active, i.e. running. You cannot create terminal sessions with Remote Utilities, only switch to existing ones.
I need to correct my own answer. We are not planning to implement bulk Host settings update via GPO. Rather, we are planning to implement our own centralized policies (using self-hosted server) feature.
However, you can already mass-update Host settings using GPO. Just export the Host's settings registry key and they propagate it across your remote machines using GPO. The key is
This is to inform you that we managed to find a workaround to this problem and implement a hotfix. A new Remote Utilities version is available on the site for download. You can also use Viewer's "Check for updates" command to update Viewer in automatic mode and Simple update command to update remote Hosts.
Please, refer to this article for more information on updating the software. We recommend that you update Remote Utilities first before installing KB4503293 and KB4501375 updates.
I understand your frustration. Remote Utilities didn't "brick" previous Windows installations until these updates came out. Isn't this a clear indication of a bug with updates then? As I said, we reported this bug to Microsoft but so far this is all we can do.
We investigated this issue and it looks like we got to the root of the problem. When a certain function is called in one of the core RU code components/libraries it causes the whole system to crash. This bug is triggered when rebooting after installing updates KB4503293 and KB4501375 and not on each and every system, at least not in our testing.
We have reported this problem to Microsoft and hopefully they will fix. Meanwhile, here is what can be done to reduce the impact of this issue:
- Before applying these updates set the Remote Utilities Host service startup to "Manual" and then after successful updates return it back to Auto.
or, if the update has already started and there is a spinning wheel use Ctrl + Alt + Del to restart the system (or use the Reset button) - the updates should still install after the system restarts.
Hope that helps. As I said, unfortunately this is a problem beyond our control but we will do our best to reach to Microsoft and see if they can fix the problem. Sorry for any inconvenience.
Soon after Microsoft pushed KB4503293, Windows 10 users started to complain about booting issues on Microsoft’s forums. At the time of writing this article, there is no official workaround for this bug.
Therefore, if you have not installed the update yet, it is better to pause the updates for a few days. Otherwise, you may experience some serious issues after installing KB4503293.
We will still see if we can somehow rectify this problem on our end though.