Pauline's community posts

Hello James,

Thank you for your message.

The First Connection Warning window is simply an informational message shown to the remote user upon the first remote connection being established to the Host machine. Please note that the first connection warning window can be closed by a remote user (that is, who is physically present at the remote machine).
In addition, please note that the notification is only shown if certain conditions are met when generating an installation package. However, we plan to slightly revamp the notification window, so it would be possible to move it to other parts of the screen.

Equally, on another laptop (an MS Surface) the dialog was positioned most of the way off-screen, and not draggable ... bug?

This might be caused by some screen capture issue. 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 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 James,

Thank you for your message.

I've forwarded your feature suggestion to our developers for a review to see if it can be added to our roadmap and implemented in future updates for Remote Utilities.

Please let us know if you have other questions.

Hello James,

Thank you for your message.

When using the Remote Printing feature you should be able to print a remote document on your local printer, i.e. some document that is stored on the Host machine can be printed on your local Viewer side. The Printer Driver is installed on the Host's side as well and can be installed directly from the Host Settings window - Printer tab.
If you need to print a document from your Viewer computer on a remote printer, then you can simply connect to the remote Host via the File Transfer mode or Full Control mode and then print the file directly from the Host machine via the remote printer.

Hope that helps.

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.