rich

Hi,

Sorry for the long and delayed response on this. Due to the long periods between our password change policy, we did not know immediately if this issue was resolved.

Unfortunately it has come to light recently that when going offline within RDM, this still only recognises the users previous password and not their new one, which they just changed to. I have experienced this myself now as well, when changing my domain password, RDM refuses to accept this is correct when taking RDM offline.

We are running RDM client version 2021.2.27.0

Thanks

Rich

Hi Hubert,

Thanks for the quick reply and look forward to seeing this VPN client support be added in the coming furture.

Thanks again

Rich

Can anyone confirm whether RDM has an add-on that works with the v2 client for Sophos Connect (SSL)? Can see there are two VPN clients shown within RDM that relate to Sophos, Sophos VPN and Sophos Connect but these do not appear to support the SSL connections used by the Sophos Connect application?

For reference, Sophos Connect 2.1 is now GA - Release Notes & News - Sophos Firewall - Sophos Community

Thanks

That's great, we have this all working now by allowing http:\\localhost:port in our Sophos AV web protection policy.

Thanks for your assistance with this.

Regards

Rich

Hi,

So we have managed to resolve this issue by allowing the localhost:19443 website via our Sophos AV web protection client. In fact, we added 127.0.0.1:19433 to be allowed (as that will resolve localhost).

With this done, the web extension looks to be working again.

It would still be interesting to know any details on how this works from a backend perspective, to ensure we are allowing the correct site etc...

Thanks again

Rich

Hi,

So managed to go through this, and have gotten further using a user account which doesn't have any policies applied for deploying the web extension.

The backgound.html page now lists under the Inspect Views for the extension, and can see the localhost entry is Red. It looks like this page is being blocked by our Sophos AV client due to this page being both uncategorised and also requiring Javascript,

Are you able to provide any background detail on how the web extension now works so I can further understand what we may need to tweak on the AV side of things to allow this work please?

Thanks

Rich

Hi,

Tried to go through this process however the Inspect Views section does not show a URL for us to select. This is the same on both Edge (Chromium) and Chrome,

Here is a screenshot from both Edge and Chrome, with Dev mode enabled,

Could this be the reason why the extension is not working, and if so why would this section of the extension properties not be shown on both browsers?

Thanks

Rich

Hi,

No, we all use Windows 10/Windows 11 machines with RDM installed locally. As mentioned before, we updated RDM to the latest version this week and it is since then that this is not working. I have repeated this on several machines here and all having the same problem. We use both Edge (Chromium) and Chrome, both of which are kept up-to-date via GPO policies so we always run latest versions.

Are there any log files, or extra details that we can review which might give us an indication of why this isnt working? The fact that the extension doesnt seem to 'read' or connect to our local RDM clients would seem to the the main problem here I suspect?

Thanks

Rich

Hi,

Could we please get some advise on how we can get the web plugin working again following the RDM update? A lot of our daily work flows and processes evolve around using this, so its vital we get this working again please.

Thanks in advance

Rich

Hi,

Tried changing the port to 19444 within both RDM and the web extension options but no joy.

Great, thanks!

Hi,

Yes tried that but same issue, screenshots to confirm that we have tried setting the same key value between RDM and the web extension options for Edge,

Have also tried this in Chrome, but same results.

Thanks

Rich

We recently updated our RDM server and clients yesterday to run the latest version (2021.2.27.0) and since then the web browser extension we use in both Chrome and Edge (latest versions of both) no longer work.

Reading the documentation on the change to the web extension I can see this now should create a API access key between the browse and RDM client however that does not seem to be working on our machines. When we remove (clear browser cache) and then re-install the extension in Chrome (for example), we can open the extension, select RDM but then the window just says that An Application Key is required. From the documentation it should ask for a key to be entered (name of the browser for example) but there is no option for this. Have tried manually entering an application key within the settings for the extension but nothing seems to change and this still doesn't work.

Any help on this would be greatly appreciated as we make use of the web extension alot!?

Thanks

Rich

HI James,

I think this is a start, and it will be interesting to see how this works in practice.

Additionally it would be interesting to understand how others handle the password update process for a team of users, as credentials may be updated by individuals working on systems (like a password expiring and needing to be changed), and so how do others handle having that credential also updated within RDM?

Thanks again

Rich

Is there a specific permission within RDM that would allow a user to amend just the password of a credential entry, but not have any other ability to rename, move or delete that entry in RDM.

I know the edit permission can be used to allow the password change part but this also allows that entry to be moved, deleted etc and instead we would like a sub-set of users to have the ability to update just the password field of an entry - if that is at all possible?

Thanks

Rich

Hi Erica,

So we are using DVLS version 2020.2.9.0, and using Windows Domain Authentication yes.

I will need to do some testing with resetting account passwords and checking the reconnect to the data source as you suggest.

I will come back to you.

Thanks

Rich

Hi,

Recently we have found that each time our users change their domain account password (password has expired etc...), RDM does not appear to recognise the new password when users try and go offline.

We currently have RDM version 2020.2.19 with Devolutions server version .

When using RDM online, this accepts our users current domain credentials fine, even after a password reset and it is just the act of going Offline which we have issues with. We have found that when going offline after a password reset, our users need to use their previous password almost like RDM is not recognising the new password for just the act of going into offline mode!

At the moment we have a workaround of removing the RemoteDesktopManager folder location in our local appdata directory but this is not ideal, and so I wondered if this is a known issue, expected behaviour, fixed in a later release or maybe a configuration change we need to implement with RDM to prevent this issue?

Many Thanks

Hi

Erica, 

Thanks for getting back to me so quickly on this.

I am taken a look at the SQL table stats as requested, and we found the below,

I have also amended the SQL Connection timeout options as per that linked article, but that hasn't appeared to make a difference I am afraid. I would imagine that we need to cear down the ConnectionLog table, given its size?

Thanks

Rich

Afternoon,

We are trying to make use of the Activity Logs Report in RDM, but each time this fails to load with an Unexpected Exception. The progress bar will appear when trying to load this report, but after 20-30 seconds the Unexpected Exception error window appears and the details for this read,

Devolutions.RemoteDesktopManager.Business.TryGoOfflineException: Unexpected exception ---> System.Net.WebException: Unexpected exception

at Devolutions.Server.ApiWrapper.RestClient.GetResponse[T](HttpWebRequest request)

at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSWebApiClient.cea5ed782d590a019f81f2bdfbef26657()

at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSWebApiClient.c5f4f6c72c053c0cd60a62abeeaa43fdf[cb75a0a5d15a1ad8b8a8a5e57cca214a3](c31561c0d54939abd223ac7c0cf30e7e6`1 c6cc9ab02b2ea9ccd42c7c0497677bcc2, ExecuteActionLogMode c92f46156e371279a4f61cd5822be5fee)

--- End of inner exception stack trace ---

I have also attached the errors which RDM emails us when this happens (seems to be a different SQL Exception error each time).

We are running,

• RDM version: 2020.2.19

• DPS Version: 2020.2.9.0

• Data Source: DPS Server with SQL

I have tried running this from different clients, and from the server that runs DPS itself and also tried using the Activity Logs Report via the web portal version of RDM, but same issue.

Any help on this would be greatly appreciated.

Many Thanks

Rich

HI,

Thanks for the advice on this. We have amended the security on the directory to ensure the LOCAL SERVICE user (used by the DevolutionsSchedulerService service) has full access to the directory where these backup files are being stored.

It will take a few days to see if this has worked, and will report back if we are still having issues.

Thanks again

Rich

Hi,

If we run the backup manually via backup manager this does clear up the older backup files, so it appears to be something done when the backups run on its schedule?

Hi,

Sorry to re-animate such an old thread but we have now updated our DPS install to version 2020.2.8.0 but we are still seeing an issue where the built-in backup manager function does not clear down old backup files.

For example, we have configured backup manager via DPS to keep 14 backups, but this does not work and instead the directory which holds these backup files ever grows until the drive is full. Currently the backup directory has 34 backup files present where 14 should be instead.

I know it was said the later version of DPS would fix this issue, however this does not appear to be the case. Any other advice on ow we can resolve this please?

Thanks

Rich

Great thanks for confirming and look forward to testing this on the new release.

Also, do you know if the behaviour of referencing the configuration file might be changed/improved as well? Currently the configuration file referenced in the VPN entry needs to be a location that is local to RDM, ideally it would be better if RDM was able to store the configuration file as part of the entry, much like the OpenVPN client works?

Thanks again

Rich

Hi,

Just to follow on from this, we are trying to make use of this Sophos Connect Add-on now ourselves, however we cannot find a way of passing credentials to the connection from the credential repo in RDM. At the moment, the only way we can pass creds to the VPN connection when the entry is opened in RDM is to enter the creds 'free-hand' into the connection entry,

Instead we need to have the option of selecting from the credentials drop down which credential from the repository this connection should use. Is there a way this can be done please?

Thanks

Rich

HI,

Not a problem, will keep an eye out and if we still haven't seen the installer be created after that time I will let you know.

Regards

Rich