thm

Still having freezing issues even after removing the local appdata information. Is this ever going to be fixed?? On version 2024.3.27.0

Devolutions seem clueless as how to, sadly.

If you want us to delete cache files, can't you specify what folders we need to delete instead of the entire RDM appdata folder?

In light of these findings, are you getting any closer to making a proper bugfix? In our case, we use RDM via a Remoteapp so we cant interact with the taskbar in the same manner. Sometimes we have freezes that can be unfreezed by killing all msedgeview2.exe processes but sometimes it does not help.

In our case it seems like the freeze happens related to various reasons. Personally I've also experienced a freeze when using the clipboard and then I've got colleagues who freeze when RDM is left idle for a very short while. All seems random and hard to reprocedure, sadly.

Haven't noticed that one.

But we sometimes experience that it unfreeze when closing edge webview processes running on the user.

But not always. Depends on whether the freeze is caused by the Edge web entries a user might be running, I guess.

When your RDM is frozen, does it also enter a 'not responding' state (according to task manager) without actually fading out like programs typically do on Windows?

Could you reach out to their support and schedule a remote sesssion? It sounds like you can perhaps more easily replicate the issue while someone from Devolutions is looking at it with you.

We are running RDM on Server 2022 session hosts.

I've been running a ticket with you (00071968) regarding the issue.

No one else experiencing freezes related to Edge WebView proccesses?

We are experiencing freezes seemingly related to website entries (although we're not completely sure) but without being able to properly reproduce it.

When a colleagues RDM was frozen I could enter the task manager of the RDS server he was using RDM thru, and see a bunch of Edge WebView procceses and the RDM task itself being "not responding" - when I forcefully closed all the webview proccesses (related to his user), RDM unfroze and started functioning again. Has anyone else experienced this?

Version 2024.3.12.0.

Yes, I included them all. What remains in the database seem to be alot logs related to non-existing entries.

We see a lot of entries in our db.ConnectionLog table. Many of them seem to refer to deleted entries to my theory is that they cannot be cleaned up with the "Clean up activity logs"

Do you have any script available that can handle this?

Thanks. There is something I don't quite understand though. If potential unwelcome guests get as far as to start RDM, as one of our users, but are refused to log in because they do not have the OTP key; what's keeping them from creating a new datasource and copying the host and authentication method (in our case active directory, i.e.the user the intruder would be logged in as) and then just configuring a new OTP on this newly created datasource?

Hello,

While it's still not possible to force the configuration of a 2fa at the user level without the Devolutions Server, a few options have been added that could suit your needs. Please note that these are only available to Advanced Data Sources.

1- Under Administration -> System Settings -> Applications -> Force application security with Windows Credentials

2- Under Administration -> System Settings -> Applications -> Force application security with TOTP (Authenticator)

3- Under Administration -> System Settings -> Security Settings -> Force data source 2-factor configuration

We also have GPOs that could help you achieve your goal https://kb.devolutions.net/rdm_group_policies.html

An example of such GPO is the "Force multiple-factor authentication on the application login"

%Root%\SOFTWARE\Policies\Devolutions\RemoteDesktopManager\ForceApplicationMFA

Let us know if that helps!

Best regards,

Thanks for getting back so quickly. Seemingly, the option under System Settings -> Security Settings should be sufficient. But when we enabled it, what do the users of RDM (those who not yet have enabled MFA) experience, exactly?

Is there still no way to enforce 2FA without the Password Server?

We only have (or well, I only have) "include folder" checked.

Searching without it yields no difference.

Again, I'm wondering - is it supposed to be instant? If not, how come searching with "all vaults" enabled is pretty much instant?

We've updated to 2020.3.19.0 and seemingly it hasn't made a difference in searching.

Again, it's instant when using "search in all vaults" - how come? What's the difference?

One obvious difference I can think of is the info about who is active on the servers in question, but I've tried disabling this as well without any difference.

Any idea :-/?

Hello,

Thank you for your swift reply!

In order for us to diagnose this slowness, would it be possible for you to go under Help -> Profiler and set the Profiler level to 1?

Once this is done, move the Profiler window aside and try to use the search field at the bottom of your Navigation Pane once more.

In doing so, a log should be created. You can provide it to me via private message or attach it to your next post.

Best regards,

Here you go!

Main thread (UI)
----------------------------------------
TreeView.LoadConnectionList...
    GetGroupInfos : 1 ms
    BeginUpdate...
        LoadConnectionInTreeNode : 2387 ms
        PreCreateGroups : 0 ms
    BeginUpdate : 2402 ms
TreeView.LoadConnectionList : 2406 ms
SelectionChanged : 126 ms
TreeView.LoadConnectionList...
    GetGroupInfos : 0 ms
    BeginUpdate...
        LoadConnectionInTreeNode : 2352 ms
        PreCreateGroups : 0 ms
    BeginUpdate : 2366 ms
TreeView.LoadConnectionList : 2366 ms
SelectionChanged...
    LoadConnectionList : 3 ms
SelectionChanged : 114 ms
TreeView.LoadConnectionList...
    GetGroupInfos : 0 ms
    BeginUpdate...
        LoadConnectionInTreeNode : 2046 ms
        PreCreateGroups : 0 ms
    BeginUpdate : 2050 ms
TreeView.LoadConnectionList : 2050 ms
SelectionChanged...
    LoadConnectionList : 1 ms
SelectionChanged : 59 ms

Searching isn't particularly slow today, it varies a lot. Sometimes it can take 7 to 11 seconds. I get it could be anything; slow SQL server, slow terminalserver that runs the actual rdm process but what I wonder is how searching can be so instant when used advanced or "all vaults"-search functions.

Hello,

Please go in Help -> Support. From there, you will find Diagnostic.

Best regards,

Alright

Repositories:         3
Entries/Items:     8891/8891
  Sessions:        2776
  Data entries:      25
  Credentials:     4779
  Sub connections:  187
  Documents:         72
  Contacts:           0
  -->Sub total:    7839

I dont see it

Regardless - any suggestions as to why "all vaults"- and advanced search is faster than regular searching in the nav pane?

thanks,

Hi Gabriel,

• We're running 2020.1.20.0. Bit more outdated than I initial figured, if I'm being honest, but we do usually not upgrade unless there's quite good reason. Have searching been adressed in recent versions?

• Database is v1.592

• How do I tell?

• We do have multiple but 99% of the items are located in one vault.

For most of the time where we've used RDM (which is a great product, that we love) searching has been a very slow process. It's bearable but generally slow. We've for a long time blamed the RDS servers from where we run RDM as a RemoteApp or the SQL server behind the database. But now a colleague of mine show me how to search across all vaults. If I enable this and search, the results are pretty much instant. Doing an advanced search is also very fast, but searching thru the navigation pane can take between 5-10 seconds before it shows the results. Sometimes even longer.

Some of use use "press enter to search" which can help avoid RDM beginning to search when we're halfway typing in the search critiria but it's also slow.

Nothing is checked under the "include X information".

Anything we can try?

Hi

I don't know if this is just the RDP client being terribly buggy like it has been for the last 3-4 Windows 10 releases, but running RDM 2019.1.41.0 as RemoteApp on Server 2019 we're seeing weird issues where the window will quickly flash, especially when switching tabs in RDM, and sometimes the window disappears completely showing everything that was opened behind the remoteapp, but when clicking anywhere it brings the remoteapp back to focus.

Another example is when clicking the dropdown list under folder or credentials, it will typically show up fine first but afterwards the dropdown list will appear behind the window:

I wanna blame Microsoft because their RDP client have sucked ass for years now but does anyone have any experience with these issues and possible workarounds?

We're running 1809 and 1903 and there's seemingly no difference in regards to these bugs. I've tried using GPOs to disable RemoteFX but that just introduces other bugs in RDM where there's large black borders around all windows and such visual oddities.

Must say I'm impressed with how fast this issue was handled, considering it's obviously not exactly critical. Thanks.

While we're talking cosmetics, I also noticed the look of tabs changed drastically. But is it really by design that theres no visual seperation of tabs?

Old version:

New version:

Couldn't some sort of borders on these tabs like the old version also be considered? It looks kinda.. buggy, the way it is now. Maybe it's just me.

I also think it looks odd how the navigation pane header changes color depending on an entry in the navigation pane is selected or not.

Selected:

Unselected:

Again - nothing critical. Maybe just user feedback :)

Thanks,

Hm, alright.

Top is how it looks on RDP session, bottom is with local: https://i.imgur.com/5VrgCcw.png - both with clean profiles.

I might just be nitpicking too much, but the borders look cut off. Obviously not a critical bug, just visually annoying, imo.

V13 seemed to have window shadows more similar to other programs, and the "hide windows shadows" option in Windows was respected then while V14 works differently, perhaps in a way that isn't supported by RDP.