rene02

And sorry for my basic graphic knowledge ;-)

Hello,

I think that's a very interesting idea, especially when you have a lot of servers you want to connect to this way. I've opened a ticket so we can add this in the future.

Thanks for the idea!

Regards,

Perfect :-) Looking forward for that feature. It would help me and other a lot I guess.

Hi Devolutions team

I'm working on a daily basis for years now with RDM. While working; I often have to restart multiple servers and use the "Check is online" feature to reconnect, as soon as the servers are back online.

I don't like to have several "Check is online" dialogs at the same time on my screens, therefore I have done a little Paint work :-) to show you my idea on the redesign of this dialog.

It would be great to have all servers being reboot on the same dialog and automatically resizing itself.

Just an idea.

Amazing...

I don't see information on how to upgrade DPS and RDM. Is it possible to upgrade DPS first to 2021 and 2020 RDM clients can still connect?

Or do we have to upgrade DPS and RDM all at the same time?

Nice to see version 2021 is released. When will the corresponding DPS version being released?

Thanks a lot for this fast reply. Seems that I did not search enough for that feature... Amazing.

One of the reasons, why I love RDM so much.

Hello everyone

Maybe someone of you can help me. Is there a way to apply some default settings to the Quick Connect feature?

I often use quick connect to connect to computers, but I would like to make sure, that my local drives are never mapped into the remote session.

I did search around the settings, but did not find a way to apply such defaults.

Also it would be amazing, if this defaults to not map local drives could be applied globally within RDM on a per-user base.

I just deleted my "config" folder and re-created a complete new configuration from scratch.

Starting with the new config, double click seems to work. But as soon as I do make some UI changes in the options, regarding the tree view, it sometimes stops working again. I'm not completely sure, but it may have something to do with showing the data source in navigation pane.

@Rene Zimmermann

There was a new permission implimented in 13.9, the permission "Execute", and it prevents you to open session.

Can you confirm that in the root this permission "Execute" is allowed for the user that is currently experiencing the issue?

If your root permissions are set to never, the double click might not be working because of this new permission.

Best regards,

The execute permission is on "Default". However, I can open sessions, but only by pressing "Enter" instead of double clicking it.

On strage thing I've just seen. I have multiple data sources. Some local databases and a DPS account.

If I startup RDM with a local database, double clicking works, as soon as I switch over to the DPS datasource, it's no longer working. Switching back to the local datasource, double click is also no longer working on the local data source.

As I told, if you wanna see the problem or do some trouble shooting on my device, please just let me know.

@Rene Zimmermannm

Hello,

For the double click issue!

We have not been able to reproduce this issue once or even had someone experience it internally. In the past it has been mentionned that restarting RDM fix the issue up until it shows up again. Are you saying that even after restarting the application, you're getting the issue right away ?

Regards,

That‘s correct. I have closed and re-opened RDM several times and it does not work ar all.

If you need any additional logs or anything, just let me know. Maybe I can help you in analysis.

Unfortunately I no longer remember, with which version it happened first time. With the latest version 13.6.7.0 I no longer had this issue.

Also the extremely annoying double click bug is back in 13.9.2.0. Double clicking an entry, does not open it. Even with multiple times closing and reopening RDM, it's not working.

Btw. I'm using the "portable" installation.

Perfect, thank you very much. I can confirm, 13.9.2.0 is working with DPS.

One bug report I have, which is present since many versions. Maybe this could be fixed in RDM 14.

If I have already one RDP session openend withing RDM and do a quick connect with password prompt, the new session does not get the focus, instead it's switching back the focus to the already openend RDP session instead.

It's not a huge thing, but it's annoying.

Is it possible, that 13.9.1.0 beta cannot be used with Devolutions password server?

It's always complaining that my password is wrong, but it's definitely entered correct.

Still having the same issues with 13.0.19.0 Beta.

The latest beta 13.0.8.0 still has this issue. I'm facing it right now.

Maybe interesting for you, I'm using a portable Version of RDM, but I cannot say, if it only happens there.

Just now having the Problem with double-click not functioning. It's not working in Public Vault AND private Vault.

But in Data Sources grid, double-click works fine. The Problem can be resolved by closing and starting RDM mostly.

By selecting the entry and pressing "Enter", the sessions opens.

I'm facing the same Problems. Sometimes it can be solved by closing and restarting RDM.

The newest beta 13.0.6.0 has the Problem too, 13.0.5.0 was way better.

Thanks for the information. It's working with your solution.

Hello Érica

I've just sent you the web.config file.

Best regards

René

Hello

We are testing the Devolutions server for our company. The installation of the Devolutions server went smooth, no problems so far. We can login to the web console of the DVLS, but as soon as we click on "Connections", I receive the following error message:

at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)

at Devolutions.Server.ServerCacheManager.GetConnections(SessionContext context, Byte[] clientVersion) in c:\Dev\devolutions\Websites\Server\Common\Managers\ServerCacheManager.cs:line 207

at Devolutions.Server.ConnectionManager.GetConnectionsWithRoles(SessionContext context, Byte[] clientVersion) in c:\Dev\devolutions\Websites\Server\Common\Managers\ConnectionManager.cs:line 166

at Devolutions.Server.ConnectionNavigationManager.GetConnections(SessionContext context, String currentFolder) in c:\Dev\devolutions\Websites\Server\Common\Managers\ConnectionNavigationManager.cs:line 26

at Devolutions.Server.Controllers.APIControllers.v2.BackendApiController.GetPartialConnections(String currentFolder) in c:\Dev\devolutions\Websites\Server\Website\Controllers\APIControllers\BackendApiController.PartialConnection.cs:line 35

at lambda_method(Closure , Object , Object[] )

at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass10.b__9(Object instance, Object[] methodParameters)

at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken)

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at System.Web.Http.Controllers.ApiControllerActionInvoker.d__0.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at System.Web.Http.Filters.ActionFilterAttribute.d__0.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at System.Web.Http.Controllers.ActionFilterResult.d__2.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at System.Web.Http.Filters.AuthorizationFilterAttribute.d__2.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at System.Web.Http.Controllers.ExceptionFilterResult.d__0.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Web.Http.Controllers.ExceptionFilterResult.d__0.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at System.Web.Http.Dispatcher.HttpControllerDispatcher.d__1.MoveNext()

If we try to connect to DVLS using RDM, we receive the following error message, as soon as we try to connect to the database:

System.Net.WebException: The remote server returned an error: (500) Internal Server Error.

at System.Net.HttpWebRequest.GetResponse()

at Devolutions.Server.ApiWrapper.RestClient.GetInfoDataFromBodyRequest[T,K](String apiUrl, T postObject)

at Devolutions.Server.ApiWrapper.RDMSWebClient.GetData(DataOptionsEntity options)

at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSWebApiClient.ca672ee2e2ecd95333b49c186092d0277.c20e7a175c4cf686430ff4e87fb942e7b()

at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSWebApiClient.c4cfebae48c715cba5241d6a671d47c8d[cb75a0a5d15a1ad8b8a8a5e57cca214a3](c31561c0d54939abd223ac7c0cf30e7e6`1 c6cc9ab02b2ea9ccd42c7c0497677bcc2, String ce54111a2f696be07240ffb02871e6867)

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

at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSWebApiClient.GetData(String proxyConnectionCacheID, Byte[] version)

at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSConnectionDataSource.GetDataSourceSettings()

at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.c29fbd34504079a3525ca4c390d5d4074(BaseConnectionDataSource cf40b69955d088020784eb92737f0a505)

Any idea, what the problem could be? DVLS is running on a Windows Server 2016 and the SQL database on SQL 2014.

All the IIS requirements are installed.

Best regards

René

Same problem here.

Hello

It does not work with Google Chrome externally, therefore it's no solution to Change the embedded browser to Google Chrome. Also Firefox is not working, only IE when starting externally.

If I may help you to test in any way, please just let me know.

Regards

René

Hello

Since any RDM 11.x version, I can no longer start iLO Remote Console from a HP iLO Website within RDM. This started with any update of RDM, unfortunately I cannot tell you, what version exactly.

I receive this error message, If I try to start the .NET Integrated Remote Console:

Details:

---------------------------------------------------------------------------

INFO ZUR PLATTFORMVERSION

Windows : 10.0.14393.0 (Win32NT)

Common Language Runtime : 4.0.30319.42000

System.Deployment.dll : 4.6.1586.0 built by: NETFXREL2

clr.dll : 4.6.1586.0 built by: NETFXREL2

dfdll.dll : 4.6.1586.0 built by: NETFXREL2

dfshim.dll : 10.0.14393.0 (rs1_release.160715-1616)

QUELLEN

Bereitstellungs-URL : file:///C:/Users/username/AppData/Local/Microsoft/Windows/INetCache/IE/JX1YT8CU/IRC%5B1%5D.application

IDENTITÄTEN

Bereitstellungsidentität : IRC.application, Version=1.3.2.1858, Culture=neutral, PublicKeyToken=b0178837005b9730, processorArchitecture=msil

ZUSAMMENFASSUNG FÜR ANWENDUNG

* Reine Onlineanwendung.

* Parameter für Vertrauensstellungs-URL ist festgelegt.

FEHLERZUSAMMENFASSUNG

Es folgt eine Zusammenfassung der Fehler. Details zu diesen Fehlern werden später im Protokoll aufgelistet.

* Die Aktivierung von C:\Users\username\AppData\Local\Microsoft\Windows\INetCache\IE\JX1YT8CU\IRC[1].application führte zu einer Ausnahme. Folgende Fehlermeldungen wurden entdeckt:

+ 'file:///C:/Users/username/AppData/Local/Microsoft/Windows/INetCache/IE/JX1YT8CU/IRC.exe.manifest' konnte nicht gedownloadet werden.

+ Die Datei "C:\Users\username\AppData\Local\Microsoft\Windows\INetCache\IE\JX1YT8CU\IRC.exe.manifest" konnte nicht gefunden werden.

+ Die Datei "C:\Users\username\AppData\Local\Microsoft\Windows\INetCache\IE\JX1YT8CU\IRC.exe.manifest" konnte nicht gefunden werden.

+ Die Datei "C:\Users\username\AppData\Local\Microsoft\Windows\INetCache\IE\JX1YT8CU\IRC.exe.manifest" konnte nicht gefunden werden.

FEHLERZUSAMMENFASSUNG FÜR DIE SPEICHERTRANSAKTION DER KOMPONENTE

Es wurde kein Transaktionsfehler festgestellt.

WARNUNGEN

Während dieses Vorgangs gab es keine Warnungen.

FORTSCHRITTSSTATUS DES VORGANGS

* [15.11.2016 07:08:29] : Die Aktivierung von C:\Users\username\AppData\Local\Microsoft\Windows\INetCache\IE\JX1YT8CU\IRC[1].application wurde gestartet.

* [15.11.2016 07:08:29] : Das Verarbeiten des Bereitstellungsmanifestes wurde erfolgreich abgeschlossen.

* [15.11.2016 07:08:29] : Die Installation der Anwendung wurde gestartet.

FEHLERDETAILS

Folgende Fehler wurden bei diesem Vorgang entdeckt.

* [15.11.2016 07:08:29] System.Deployment.Application.DeploymentDownloadException (unbekannter Untertyp)

- 'file:///C:/Users/username/AppData/Local/Microsoft/Windows/INetCache/IE/JX1YT8CU/IRC.exe.manifest' konnte nicht gedownloadet werden.

- Quelle: System.Deployment

- Stapelüberwachung:

bei System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

bei System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()

bei System.Deployment.Application.FileDownloader.Download(SubscriptionState subState, X509Certificate2 clientCertificate)

bei System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)

bei System.Deployment.Application.DownloadManager.DownloadApplicationManifest(AssemblyManifest deploymentManifest, String targetDir, Uri deploymentUri, IDownloadNotification notification, DownloadOptions options, Uri& appSourceUri, String& appManifestPath)

bei System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)

bei System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)

bei System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)

bei System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

--- Interne Ausnahme ---

System.Net.WebException

- Die Datei "C:\Users\username\AppData\Local\Microsoft\Windows\INetCache\IE\JX1YT8CU\IRC.exe.manifest" konnte nicht gefunden werden.

- Quelle: System

- Stapelüberwachung:

bei System.Net.FileWebRequest.EndGetResponse(IAsyncResult asyncResult)

bei System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

--- Interne Ausnahme ---

System.Net.WebException

- Die Datei "C:\Users\username\AppData\Local\Microsoft\Windows\INetCache\IE\JX1YT8CU\IRC.exe.manifest" konnte nicht gefunden werden.

- Quelle: System

- Stapelüberwachung:

bei System.Net.FileWebResponse..ctor(FileWebRequest request, Uri uri, FileAccess access, Boolean asyncHint)

bei System.Net.FileWebRequest.GetResponseCallback(Object state)

--- Interne Ausnahme ---

System.IO.FileNotFoundException

- Die Datei "C:\Users\username\AppData\Local\Microsoft\Windows\INetCache\IE\JX1YT8CU\IRC.exe.manifest" konnte nicht gefunden werden.

- Quelle: mscorlib

- Stapelüberwachung:

bei System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

bei System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)

bei System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)

bei System.Net.FileWebStream..ctor(FileWebRequest request, String path, FileMode mode, FileAccess access, FileShare sharing, Int32 length, Boolean async)

bei System.Net.FileWebResponse..ctor(FileWebRequest request, Uri uri, FileAccess access, Boolean asyncHint)

DETAILS ZUR SPEICHERTRANSAKTION DER KOMPONENTE

Es sind keine Transaktionsinformationen verfügbar.

---------------------------------------------------------------------------

Unfortunately the text is in german. The iLO Website is shown with Internet Explorer Engine within RDM. If I start the .NET Remote Console only using IE, not within RDM, everything works fine.

René

I have found the setting and it definitely looking better, but still not OK.

RDM 12 beta seems to have a problem with DPI scaling. On my Surface Pro 3 with Windows 10 everything is extremly small and looking weird.