The Windows system log capability is a great improvement of the software. Specially for complying with auditing and compliance requisites that such functionality (remote access) should have.
We´ve identified that when using the "Remote Utilities Security" vs the "Custom Server Security" the results have some small divergences: 1. The "Remote Utilities Security" shows the logged user on the "popup ballon" while the "Custom Server Security" does not. 2. The "Custom Server Security" explicitally register the logged user on the windows event log while the "Remote Utilities Security" does not.
Both theese situations are depicted on the attached images. The username should be shown/registered on both cases.
Suppose I have 200 computers, and 1 acquire endpoint license for each (i.e. 200 endpoint licenses). Can I use those same 200 licenses in multiple viewers (multiple techs/concurrent connections in different hardware) - working similar to the legacy Remote Utilities v5 licensing (which was licensed at the "host" side)?
Thanks for the answer. I'm looking forward for this feature.
Just to clarify: The "end user" does not access via the RDP connection mode in Remote Utilities. It access directly the native Microsoft Remote Desktop Connection client (via a Thinclient). Only the "support staff" uses Remote Utilities to access the hosts to support the "end users" (and to do so they need to mirror the "end users" screen" by selecting it under "Terminal sessions" menu of the Remote Utilities Viewer)
Is there any way to enable the "ask user permission" popup to show up on Remote Desktop connections?
My host stations are headless. The user access them via "Remote Desktop" and I'd like to use the "ask user permission" policy to require the users to explicity allow the remote access. On the other hand, the popup doesn't show on the "Remote Desktop Connection", only on the "local screen" (local vga/hdmi output), which makes access to the popup unviable.