jan-pieter

Hi,

When I start a putty session the putty window looses focus just after being displayed.

This behaviour seems to be related to the latest update (I'm on 5.0.4.0 64-bit at the moment) as I can't remember I happening before.

It is not a big issue but normally you would start typing username and/or password but now if I'm lucky I manage to get in one or two characters before the focus is lost for the putty session within RDM - RDM does not loose focus as I can use the Alt key to get the RDM menu after the Putty window has lost focus.

Regards,

Jan-Pieter

I'm connecting to the RDM database from another (non-trusted) domain using a script to call RDM via runas with the /netonly option.

Command line: runas /netonly /user:DOMAIN\USERID "C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager64.exe"

You could try to set up a cmd like this for when you are on the non-domain pc. And use the normal way of connecting when you are on domain pc's.

We have had a similar issue regarding the caching mode. Though the data source itself said it was set to intelligent , the data source information showed it to be cached locally. After changing the data source setting to disabled, saving (and thus reconnecting) and then to intelligent and saving the offline mode became available.

We just upgraded to 13.0.5 and the sessions and credentials were merged (even though a colleague and myself had disabled the option in our settings).

Turns out the global (admin) setting (I didn't even know this settings was available :-)) was set to enable overriding the personal setting (as you describe above).

Was this option on admin set to disabled before (and now it is set by default to enabled?)

Hi,

We are setting up a TeamViewer connection (through a Windows terminal server) using a jump host (rdm agent).

When the connection is made and (eventually) the TeamViewer session is started on the jump host the rdm agent takes a long time to start up. Obviously part of the time is caused by starting the jump host (it is not active so has to be started) but at some time we can manually start programs while the rdm agent isn't active yet. We have to set the time out to 120 secons. How can we speed this up?

Is it possible (we couldn't find it in RDM not in TeamViewer) to have TeamViewer connect to a specific screen directly without having to select this in TeamViewer after start ?

When TeamViewer starts it is not full screen. Can we influence the TeamViewer window to start full screen on the jump host?

Groet,

JP

Hi, here I am again. Sorry to bother you.

I'm still busy trying to figure out if this is possible and we would like to set up te following and maybe you know if this is possible.

On a VDI we will install RDM and the VDI will be accessed via a Thin Client with 9 monitors connected.

In RDM on the VDI we will set up several TeamViewer connections to remote workstations with 1 or 2 monitors connected.

These connections will be displayed on the 9 monitors on the thin client by having the RDM connections a preferred monitor/screen.

The remote workstations are behind a proxy/terminal services gateway so we plan on having the RDM agent and maybe RDM itself on a terminal server/... as a jump host behind the proxy/terminal services gateway for the TeamViewer connections and having the jump host connection (RDP right?!?) use the proxy/terminal services gateway connection.

I'm also not sure if TeamViewer should be on the VDI and/or on the terminal server/... set up as jump host.

Is this possible? Or are we not thinking straight?!? :-)

Hi,

I'm looking into using Wayk Now together with RDM.

The remote machines are workstations with one or two screens attached that will generate sound alerts when attention is required.

RDM will be installed on a VDI being connected to using a thin client with a video wall of 9 monitor attached.

Each of the remote workstation screens will have to be able to be displayed on one of the 9 video wall monitors either pre configured or dragged to (undock) so that is where RDM come into play.

We were planning on having Wayk Now connections (through one or more Terminal Services gateways) to the remote workstations to be able to display either workstation screens and as said when a alert plays a sound at the work stations showing on the video wall the sound should be played on the thin client.

What would be the best alternative for Wayk Now at this time in this setup?

Regards,

Jan-Pieter

David,

Thank you for the info.

Given the options for undocked (monitor #1 to #6) some of the connections could be placed directly on a specific monitor, right?

How would RDM handle two monitors/screens connected to the remote machine (endpoint of the connection). I don't see an option right away and again at this time I have no possibilty to test it.

Regards,

Jan-Pieter

Hi all,

I have a thin client connected to a monitor wall with 9 monitors.

The thin client will connect to a VDI with RDM installed.

RDM will connect through a Terminal Services gateway to workstations each having 1 or 2 monitors attached.

Can we display each workstation monitor on any monitor in the monitor wall?

I have no way of setting up a test environment for this so I'm hoping this description is enough to answer this.

Regards,

Jan-Pieter

RDM uses the ports set up in the SQL Server setup.

Check your SQL Server tcp/ip port setting and that is the port SQL Server is listening on (it may say TCP Dynamic Ports but that means dynamically choosen during installation). So this port should be open from the RDM location to the SQL Server using tcp/ip.

Furthermore if you are connecting to the SQL Server using the instance naming (i.e. HOST\INSTANCE) you should also open port 1434 using udp (again from the RDM location to the SQL Server). Via this port the SQL Server Browser is connected to and the SQL Browser returns the tcp/ip port mentioned above after which the SQL Server client (RDM) reconnects via that port.

At our side the new version fixed this.

Hi,

This sounds a lot like the issue we reported and is still being investigated.

Check https://forum.devolutions.net/topic28185-user-specific-settings-on-credential-entry-change-from-custom-to-embedded.aspx

Regards,

Jan-Pieter

To trouble shoot further if the action Jeff suggest doesn''t work:

From the computer you are running RDM perform a "telnet <databaseservername> 1433" (for example: telnet rdmhost 1433). This should clear the command line screen (success) or eventually return an error.

If you get the error something is blocking the port.

If you don't get the error you can reach the database server and sql server is listening on that port.

Now make sure (ask the dba) if the SQL Server Browser service is running. When you connect to SQL Server using the name only DATABASESERVER\INSTANCENAME for a named instance or DATABASESERVER for a non-named instance (you can actually have a named instance running on port 1433 so make sue you know if it is a named or a non-named instance - again your dba should know) you connect to port 1434 using udp. This connection returns the actual port SQL Server is running on and a new connection is setup using that port.

Let us know your findings if you are still unable to connect.

We will be closing the incident at our end. Hope you manage to find the issue and (should it be related to one of the upgrades) keep it in mind when testing new updates for simular issues.

As you are using MSSQL (like us) and if you are interested in querying directly on the database for this information, let me know so I can provide you with the query's we currently use for this.

Jeff,

That doesn't look like the same issue. They did not use batch edit and "the embedded" mentioned in this issue is different than the one for our issue - our embedded is the credentials being embedded while embedded in the other issue refers to a connection being opened external or embedded.

Furthermore I can confirm the issue is for more users. The whole team having access to the credentials and having set personal credentials (user specific settings) on them are seeing the credentials having been moved from custom to embedded.

Regards,

JP

Ah, the user is still on 12.5.4.0 and he suspects since the upgrade to this version the issue has arisen.

The exact version before that is unclear.

Yes, we use a SQL Server data source.

The user that detected the issues is on 12.6.2.0. He however already mentioned this issue briefly a couple a weeks ago so it can't be the last upgrade to 12.6.2.0.

I thought I had seen the client version in one of the tables with the connection log info but I can't find it (anymore?!? - I'm not sure) so I can't tell you the exact history of his upgrade.

I believe he upgraded once more recently but (again) I'm not sure if that was after or before he noticed the issues.

Regards,

Jan-Pieter

Hi,

Recently users have noticed user specific settings made as Custom entries were changed into Embedded credential entries causing the entry to stop working.

Is this something that has been changed in a recent version of maybe caused by an upgrade for a recent version?

Regards,

Jan-Pieter

Thanks for the update. Like Michel also pointed out your "What's changed" page contains beta release but once on this page it is unclear what the current non-beta version is.

Even more, if I goto the download page I see a version to be downloaded (12.5.4.0 at this time) and also a Change History "button" that leads met to https://remotedesktopmanager.com/Home/ChangeHistory. This page does not indicatie which version is still in beta and which not and this url does not include the Beta part Michel showed me.

Maybe you can add which version is beta and which is an official (non-beta) release on that page?

Ah, I didn't see the "Beta" part in the URL. Thanks for pointing that out.

Yeah, but we are on Default (should be equal to All (major and minor updates) according to documentation) and the changes page does not mention anything about the versions upto 12.5.12.0 to be beta ...

Hi,

Most of our users are on 12.5.4.0 and they haven't received any update pop-up/reminder and I see 12.5.12.0 is out according to the "what's changed" document/page.

I'm on 12.5.6.0 but I'm not sure if I auto-updated it or I donwloaded it for support on another issues.

I know you spread the updates but it now seems to be a "large spread".

Is something wrong or is it intended behaviour?

Regards,

Jan-Pieter

Ok, I will ask my colleague once he is back from his holiday to test but as far as I can tell it has been solved :-)

Looks like it is fixed in 12.5.6.0 ... can you confirm it should be fixed (as I find it hard to test ;-))?