Pauline's community posts

Hello,

Thank you for your message.

Could you please try using the Send key command instead and see if this helps to resolve the issue? For example, please right-click on the connection tab when stuck on the "world map" screen, then select Send key and choose the PrintScreen command as shown on the screenshot below:


In addition, please try enabling the Use legacy capture mode feature in the Host Settings -> Other tab and see if this helps to resolve the issue. Please make sure to restart Host after enabling the feature in order for the changes to be applied. You can also edit the Host Settings remotely via the Remote Settings feature.

Hope that helps.

Hello Igor,

Thank you for the provided details.

In addition, could you please let us know if the issue persists when you try running the programs with the Use system account checkbox enabled, or when you try using the Run as... feature?

In case if the issue persists even, then please feel free to send us the Host log files for examination. The Host logs can be located in the following folder: C:\Program Files (x86)\Remote Utilities - Host\Logs\. Please do not post the logs on the forum, you can send them to support@remoteutilities.com.

Looking forward to your reply.

Hello Steven,

Thank you for the clarification.

Could you please also let me know if you try logging in (i.e. within your Full Control window), when switching to the needed terminal session and getting the Windows login screen - does this action logs out the other user who was previously connected to the remote Host machine in an RDP session?

Looking forward to your reply.

Hello Steven,

Thank you for the clarification.

Could you please clarify if you're connecting to a Server OS or a Client OS and if the terminal session you select is active? Please note that when you want to switch between terminal sessions using the Toolbar menu, the sessions must be active, i.e. running. You cannot create terminal sessions with Remote Utilities, only switch to existing ones.
In addition, please note that in case if your Host is running on a Client OS, such as Windows 7 or Windows 10, unfortunately, it won't be possible to connect to an existing session this way.

In case if your Host is installed on a Server OS and the terminal session that you want to connect to is active, then please double-check if the RDP client is configured properly, as such issues might be caused by the RDP client on a server machine being configured for Client OS.

Hope that helps.

Hello Steven,

Thank you for your message.

Please note that Remote Utilities works in a console session and displays exactly what is shown on a remote display which is the reason why you see the Windows logon screen when connecting to a remote machine. Please try using the Terminal user switch icon on the Full Control mode's Toolbar to switch to a specific session and see if this helps.

Please let me know if you have more questions.

Hello Dan,

Thank you for your message.

Yes, Agents count against your license as well, as in terms of licensing Agents are no different from Hosts. However, since Agents are mostly meant for spontaneous attended remote sessions, you can simply remove Agent from your address book if you do not plan connecting to the same Agent again.

Please let me know if you have more questions.

Hello Chris,

Thank you for you message.

In case if you want all of your Hosts to have different Internet-ID codes upon installation, then the best option is to use a custom MSI installation package.
This way, you can use your custom MSI installer to push-install Host across your network, including silent installation via the Remote Install Tool or via GPO. For this purpose, we recommend creating a standard MSI package as described in this guide.
In this case, you can push-install Host on each VM and each Host should have its own Internet-ID code, so there's no need to update their settings manually or involve the students.

Please let me know if you have more questions.

Hello,

Thank you for your patience.

We've upgraded your support level, so now it's properly displayed as Starter. Sorry for the inconvenience.

Please let us know if you have more questions.

Hello Christian,

I'm glad to hear we were able to help!

Does Remote Utility have any way to detect if the connection drops, and perhaps toss up a warning box? I would rather have the window pop up with a disconnection notice than to think that I am still properly connected.

Unfortunately, for now a feature that would notify a tech when disconnect occurs is yet to be implemented. However, if disconnection occurs when using Viewer for Windows, then Viewer tries reconnecting to the remote Host and then does notify the tech about connection being interrupted. Therefore, since such feature is already available in Viewer for Windows, we definitely plan to implement it in future updates of Viewer for both Mac and Linux. Thank you for your feedback.

Please let us know if you have other questions.

Hello Christian,

Thank you for your message.

Would it be possible to shrink the text down, so that I may reclaim more screen space?

Actually, this feature is already available in Viewer for Mac/Linux. In order to shrink the connection window, please do the following:
1. When connected to remote Host in Full Control mode hover the mouse cursor over the the top edge of the connection window to reveal the Toolbar.
2. On the Toolbar click the last icon with three dots to invoke a drop-down menu and select Stretch view.
3. Alternatively, in the Viewer main window right-click on the remote connection and select Properties, then navigate to the Remote Screen mode tab and set the view mode to Stretch.

Hope that helps.