Pauline's community posts

Hello Basil,

Thank you for your feedback.

I'll forward your feature suggestion along with the feedback to our developers for a review to see if it's possible to add it in our future updates. Sorry for the inconvenience.

Please let me know if you have other questions.

Hello John,

Thank you for the feedback.

Is this like overkill ? I do thank you for the reply it is a solution I didn't know but think its very hard to roll out to other users.

Yes, unfortunately, this solution might be a little time/effort consuming and not very convenient for some users. We already have the feature that will allow mapping remote and local monitors in a convenient way in our wishlist as well as we plan to revamp the mechanism behind the multi-monitor configuration. I'll check on this with our development department to see if, perhaps, we can provide an ETA on this.

Please let me know if you have any questions.

Hello Fritz,

Thank you for the provided details.

I've forwarded the issue to our developers and asked for their input on this. Sorry for the inconvenience.

I'll get back to you with an update on this shortly.

Hello Peter and Michał,

Thank you for your patience.

I've checked on the issue with our development department - the "Fatal error" message was caused by a specific deinstallation issue that occurred in the 7.0.0.2 version. However, we've already implemented a quick fix for it in the subsequent version 7.0.0.3, so it shouldn't occur anymore.

Please let us know if you have any questions.

Hello John,

Thank you for your message.

Could you please clarify if you mean multi-monitor configuration on the remote Host side? Am I right in assuming that you want to match remote monitors to your local monitors as you've mentioned in this thread? If this is the case, then unfortunately, the feature that would allow automatically map remote screens to local monitors is yet to be implemented.

However, it's possible to do so manually:
1. In your Viewer create 2 different connections to the same remote Host, i.e. using the same IP address or Internet-ID code, but name them differently, e.g. Monitor 1, Monitor 2, etc.
2. Disable the Tabbed view mode: in the main Viewer window navigate to the Tools tab, select Options -> Remote screen tab and disable the Tabbed view checkbox.
3. Open both connections to the remote Host you've created on Step 1.
4. Select different monitors for each connection - this can be done by clicking the Remote monitors icon on the Toolbar in the Full Control and View window.
5. This will allow you placing the connection windows on your local monitors as desired.
If you mean something else, please elaborate a bit more on the issue.

Hope that helps.

Hello Fritz,

Thank you for the detailed clarification.

One more question - is there any antivirus/security software running on this specific laptop?

Looking forward to your reply.

Hello,

Thank you for letting us know.

We were able to reproduce the issue - I'll forward it further to our developers for a review, to see if we can implement a fix for it in our future updates. Sorry for the inconvenience.

In meantime, do we have the possibility to get a free (for 10 entries) key for version 6? Cannot find any way to order it.

Unfortunately, we no longer sell/distribute version 6.10 license after version 7 release. Sorry for that.
However, please note that it's still possible to connect from Viewer version 7 to both Host/Agent version 6 and 7. In fact, I've just tested the scenario with the "Restart Agent as..." feature when connecting from Viewer version 7.0.0.3 to Agent version 6.10.10.0 and the feature works as expected in this case, so it's possible to use this as a temporary workaround, i.e. no need to downgrade Viewer as well.

Hope that helps.

Hello,

Thank you for your suggestion.

We already have similar features in our wishlist that will allow generating new Internet-ID and password for Agents each time when a user runs Agent. However, I'll forward this feature request to our development department for a review to see if we can add it in our future updates.

Let us know if you have other questions.

Hello Marco,

Thank you for your patience.

I've checked with our developers on this question - the User field in the "Operating System" section displays the name of a user that is currently logged on. This property must have a value. In a terminal services session, UserName returns the name of the user that is logged on to the console not the user logged on during the terminal service session.

Hope that helps.

Hello Giorgio,

Thank you for your message.

This is a known issue - we're currently extensively testing it and will try to release an updated version of mobile Viewer (for both iOS and Android) with the implemented fixes as soon as we can. Sorry for the inconvenience.

Please let us know if you have other questions.