Io rX wrote: Installation of the RU-host. I first logon to the machines with an RDP-session when the client is connected with a VPN (user initiated). I installthe RU-host with elevated privileges and then get an ID from the RU. Restart the machine. The I try to connect with the RU-Viewer to the ID acquired I can't connect.
If you have a VPN tunnel why would you want to use the ID connection? This unnecessarily complicates the issue by routing the remote access via our servers. Instead, just use the VPN IP address (or dns name if any) of the remote PC for direct point-to-point connection.
I mean you can try to adjust printing options after you received the printing request from the remote PC but before you actually send it to the printer.
In the Remote Printing window, when you click "Print all pages" or "Print selected page" you are shown a dialog window that prompts you to select the printer. Beside the dropdown printer selection menu there is a "Properties" button. Depending on your printer model the properties can provide a whole variety of options for the printing outcome.
Well, that's not exactly the reason, although we you are probably right - a more general assumption is that we try to keep our default hosted service as simple as possible. You know, the more moving parts a system has, the more it is prone to errors and malfunction.
Whereas with RU Server we can experiment and add more advanced features. By the way, using e-mail for what you described is probably overkill. If both Host and View keep connection with the RU Server alive a notification (or a desktop alert) could appear right in the Viewer. So we'll give it a thought and adjust our plans regarding the RU Server roadmap accordingly.
Remote Utilities only transfers the print file from the remote PC to the local PC in a special printer interchange format, understood by all printers. When printing the file to your physical printer on the Viewer side did you play with printer options in the standard Windows Print dialog?
Both these options can only be possible with RU Server rather than with our default (corporate) server, for obvious reasons. We'll take a look at your suggestions and see if we can implement them in subsequent releases.